I am getting this error on just one particular device which is Moto E Android Version 5.1.1 which is a bit low spec then my production device Nexus 4 running same 5.1.1, most of the solutions provided here are not working, hope some one can give some pointers.
Fatal Exception: java.lang.NoSuchMethodError: No static method notEmpty(Ljava/lang/CharSequence;Ljava/lang/String;)Ljava/lang/CharSequence; in class Lorg/apache/http/util/Args; or its super classes (declaration of 'org.apache.http.util.Args' appears in /data/data/com.bowser.cloudthumper/files/instant-run/dex/slice-i2p_9eb30cacd8b3f7a68d7689d883ed4bf9afe9cdd9-classes.dex)
at org.apache.http.config.RegistryBuilder.register(RegistryBuilder.java:57)
at org.apache.http.impl.conn.BasicHttpClientConnectionManager.getDefaultRegistry(BasicHttpClientConnectionManager.java:114)
at org.apache.http.impl.conn.BasicHttpClientConnectionManager.<init>(BasicHttpClientConnectionManager.java:147)
at org.thoughtcrime.securesms.mms.LegacyMmsConnection.constructHttpClient(LegacyMmsConnection.java:181)
at org.thoughtcrime.securesms.mms.LegacyMmsConnection.execute(LegacyMmsConnection.java:194)
at org.thoughtcrime.securesms.mms.OutgoingLegacyMmsConnection.sendBytes(OutgoingLegacyMmsConnection.java:135)
at org.thoughtcrime.securesms.mms.OutgoingLegacyMmsConnection.send(OutgoingLegacyMmsConnection.java:118)
at org.thoughtcrime.securesms.mms.OutgoingLegacyMmsConnection.send(OutgoingLegacyMmsConnection.java:93)
at org.thoughtcrime.securesms.mms.CompatMmsConnection.send(CompatMmsConnection.java:37)
at org.thoughtcrime.securesms.jobs.MmsSendJob.onSend(MmsSendJob.java:82)
at org.thoughtcrime.securesms.jobs.SendJob.onRun(SendJob.java:43)
at org.thoughtcrime.securesms.jobs.MasterSecretJob.onRun(MasterSecretJob.java:18)
at org.whispersystems.jobqueue.JobConsumer.runJob(JobConsumer.java:76)
at org.whispersystems.jobqueue.JobConsumer.run(JobConsumer.java:46)
Related
Implementing "I18n.js" in our React Native project has worked flawlessly until a couple of days ago. Through the use of "Crashalytics" with Firebase we have noticed repeated but few crashes. These crashes seem to only mainly occur on Android 11 and Samsung + Xiomi devices (none on iPhones yet). The log output is as follows:
Fatal Exception: com.facebook.react.common.JavascriptException: TypeError: undefined is not an object (evaluating 's.languageTag'), stack:
at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:83)
at java.lang.reflect.Method.invoke(Method.java)
at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
at com.facebook.react.bridge.queue.NativeRunnable.run(NativeRunnable.java)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
at android.os.Looper.loop(Looper.java:246)
at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)
at java.lang.Thread.run(Thread.java:923)
I fail to reproduce the crash by changing language in the phone, downloading hardware profiles that match the ones mentioned in the crash logs (Samsung S10, etc), and using them as the emulator.
Any help and/or ideas are much appreciated.
Thank you in advance!
I got the same error. You can debug it by running production build on your phone and connect it with Android studio. You can see the logs by selecting your phone and app process screenshot. I my case the error was about destructuring a property that doesn't exist in object
I've noticed an increase in the number of StackOverflow crashes in my app which all seem to point back to Google Play Services Maps. I am currently using version 15.0.1 (com.google.android.gms:play-services-maps:15.0.1) - but this started about two weeks ago when I was still using 15.0.0. There are several crashes, but they all result in StackOverflows when dealing with Hashmaps or Arrays from the Maps code (which is obfuscated). Some examples of the crashes (I just copied the stack traces to the point where it goes to the obfuscated maps code):
Fatal Exception: java.lang.StackOverflowError: stack size 1038KB
at java.util.HashMap.remove(HashMap.java:617)
at com.google.maps.api.android.lib6.gmm6.util.e.d(:com.google.android.gms.dynamite_dynamitemodulesb#12685021#12.6.85 (040306-197041431):29)
Fatal Exception: java.lang.StackOverflowError
at java.util.ArrayList$ArrayListIterator.(ArrayList.java:551)
at java.util.ArrayList.iterator(ArrayList.java:548)
at java.util.Collections$UnmodifiableCollection$1.(Collections.java:953)
at java.util.Collections$UnmodifiableCollection.iterator(Collections.java:952)
at com.google.maps.api.android.lib6.common.i.iterator(:com.google.android.gms.dynamite_dynamitemodulesb#12685002#12.6.85 (000304-197041431):25)
Fatal Exception: java.lang.StackOverflowError: stack size 8MB
at java.util.HashMap.createEntry(HashMap.java:826)
at java.util.HashMap.addEntry(HashMap.java:813)
at java.util.HashMap.put(HashMap.java:436)
at com.google.maps.api.android.lib6.gmm6.util.e.b(:com.google.android.gms.dynamite_dynamitemodulesb#12685020#12.6.85 (040304-197041431):17)
Fatal Exception: java.lang.StackOverflowError: stack size 8MB
at java.util.HashMap.removeEntryForKey(HashMap.java:597)
at java.util.HashMap.remove(HashMap.java:584)
at com.google.maps.api.android.lib6.gmm6.util.e.d(:com.google.android.gms.dynamite_dynamitemodulesb#12685023#12.6.85 (040400-197041431):29)
Fatal Exception: java.lang.StackOverflowError: stack size 8MB
at java.util.ArrayList.(ArrayList.java:170)
at com.google.maps.api.android.lib6.common.i.(:com.google.android.gms.dynamite_dynamitemodulesb#12685020#12.6.85 (040304-197041431):9)
I also have a number of other crashes directly inside the obfuscated maps code.
Some other information: the maps are not inside the main flow of my app, so it is only used by about 8% of my users - around 200 or so calls a day. Today is by far the worst with 62 crashes affecting 13 users - two days ago it was 42 crashes and most other days I have zero crashes.
Operating system versions affected: 7.0, 6.0.1, 4.4.2, 7.1.1, 4.1.2, 5.1, 4.3
Devices: Samsung, Sony, Lenovo, Moto E3 (whatever that is) and a Huawei.
Any help or pointers would be useful!
The following crash increased from one release to the other, once we switched from generating a release build from a windows machine to a Mac OS X machine. It happens primarily with Android 4 (90% + )
Any help is appreciated.
Fatal Exception: java.lang.IllegalAccessError: tried to access method android.support.v4.app.FragmentActivity.onReallyStop:()V from class xx.com.app.view.orderflow.OrderActivity
at xx.com.app.view.orderflow.OrderActivity.onReallyStop(OrderActivity.java)
at android.support.v4.app.FragmentActivity.doReallyStop(FragmentActivity.java:668)
at android.support.v4.app.FragmentActivity$1.handleMessage(FragmentActivity.java:87)
I have an app which is using roboguice 3 and it crashes on start on devices with API 18.
Same app works perfect on android 23.
Stack trace:
java.lang.NoClassDefFoundError: roboguice.inject.ContextScopedRoboInjector
01-12 16:53:31.285 12710-12710/com.package.app E/AndroidRuntime: at roboguice.RoboGuice.getInjector(RoboGuice.java:197)
01-12 16:53:31.285 12710-12710/com.package.app E/AndroidRuntime: at roboguice.activity.RoboActionBarActivity.onCreate(RoboActionBarActivity.java:85)
any ideas?
As stated in their GitHub page
RoboGuice is no longer supported.
[..]
There are now many other excellent DI frameworks for Android, please consider migrating to one of them.
I have an Android app that is crashing with the following error.
Caused by: java.lang.NoSuchFieldError: com.google.gson.FieldNamingPolicy.IDENTITY
at ir.<init>(App:72)
ja.a(App:653)
at ja.doInBackground(App:1)
at android.os.AsyncTask$2.call(AsyncTask.java)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:306)
... 4 more
App crashed! Process: com.company.app
This doesn't crash on my Nexus S running Android 4.0 ICS, however it is crashing on another beta test device that I don't have access to. I am using the Google GSON 2.1 library.
I am also using ProGuard however if that was causing the issue I would think that would also cause the issue on my Nexus S.
Any idea why this would not occur on my test device and how I can resolve the issue?
This issue was caused by a custom Android ROM, I assume that inconsistent class files within the ROM were causing the issue as suggested in the question comments.
I fixed it by skipping GSON from obfuscation.
-keep class com.google.gson.Gson {*;}