I have an active app on Google Play. My users are often experiencing a crash that I can't figure out where to debug.
java.lang.NoClassDefFoundError:
at jl.b (jl.java:3)
at jk.a (jk.java:3)
at jm.a (jm.java:18)
at com.google.android.gms.ads.internal.util.ap.a (ap.java:17)
at ip.a (ip.java:19)
at ip.run (ip.java:8)
Caused by: java.lang.ClassNotFoundException:
at dalvik.system.BaseDexClassLoader.findClass (BaseDexClassLoader.java:134)
at java.lang.ClassLoader.loadClass (ClassLoader.java:379)
at ac.loadClass (ac.java:4)
at java.lang.ClassLoader.loadClass (ClassLoader.java:312)
at jl.b (jl.java:3)
at jk.a (jk.java:3)
at jm.a (jm.java:18)
at com.google.android.gms.ads.internal.util.ap.a (ap.java:17)
at ip.a (ip.java:19)
at ip.run (ip.java:8)
The last portion makes me think it's related to AdMob
at com.google.android.gms.ads.internal.util.ap.a (ap.java:17)
But I can't figure out where's exactly the problem. Everything on my test devices seem to be fine, but still other users are experiencing these crashes.
I've uploaded the de-obfuscator file, but these stack traces are all obfuscated.
I'm currently using the version 16.0.0 of play services ads
implementation 'com.google.android.gms:play-services-ads:16.0.0'
It appears there's a temporary workaround while we wait for this to be officially fixed from Google. Maps library is also affected.
Just put this tag into the Manifest file:
<uses-library
android:name="org.apache.http.legacy"
android:required="false" />
I tried it and it appears to be working. I'm going to mark this as an answer but I'll update this post when an official fix will be available.
As you say this is almost certainly an AdMob problem. They might be aware of it already, but with this sort of issue it is good to contact AdMob customer support, and then they can route the issue to the AdMob developers. It is very unlikely to be your fault.
You could do this on this page or in this form or
Related
I'm having a crash in a Xamarin.Android App, but this ONLY happens in RELEASE mode.
The issue is when accesing the map. So, I've extracted the device log and after analyzed it, I've found these lines:
03-19 19:55:10.305 HUAWEI JKM-LX3 Error 14753 AndroidRuntime java.lang.NoSuchFieldError: no "Lcom/google/android/gms/location/SettingsApi;" field "SettingsApi" in class "Lcom/google/android/gms/location/LocationServices;" or its superclasses
at mono.android.content.DialogInterface_OnClickListenerImplementor.n_onClick(Native Method)
at mono.android.content.DialogInterface_OnClickListenerImplementor.onClick(Unknown Source:0)
at com.android.internal.app.AlertController$ButtonHandler.handleMessage(AlertController.java:174)
at android.os.Handler.dispatchMessage(Handler.java:112)
at android.os.Looper.loop(Looper.java:216)
at android.app.ActivityThread.main(ActivityThread.java:7625)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:987)
03-19 19:55:10.305 HUAWEI JKM-LX3 Error 14753 AndroidRuntime Process: com.companyname.app, PID: 14753
03-19 19:55:10.305 HUAWEI JKM-LX3 Error 14753 AndroidRuntime FATAL EXCEPTION: main
After a few google searches, I've found this answer, but it comes from 2018, and it's not related to Xamarin. One of the comments says that "Google just deprecated GoogleApiCLient" in 2018.
Another resource I've found is this one which, kinda seems familiar, but it comes from a plugin repo in github. A user says that he had to reverse to 1.5.7, but what package is he talking about?
Again, this happens only in RELEASE mode, for Google Play. In DEBUG mode the maps works fine, no problem at all.
If you require more data, just tell me.
Thanks for your help.
I was recently investigating an issue related to a delay in rendering a welcome/greeting message for the first time when webchat is launched. The very first activities network request (before showing the welcome/greeting message) is usually 2-6s long(mostly it's either 2.5s or 5-6s). We are trying to implement this using BotFramework webchat version: 4.10.1 with react (minimizable version).
What I'm trying to accomplish is to load welcome/greeting message faster than the current time and upon checking the performance profile I found that activities network request(directline.botframework.com/v3/directline.../activites) is taking either ~2.5s or ~5.5s and after that, there is some more buffer time in between before the welcome message gets rendered.
I tried to record the performance profile of both cases(2.5s/5-6s)
2.5s
https://i.imgur.com/InEyHxl.gif
5s
https://i.imgur.com/yl3l6Z8.gif
Trying to find more information on how to improve/fix this behavior and gain more insights on this. I would be really glad if anyone can share your thoughts on this issue. Please let me know if I need to provide more information.
This is probably a bug that should be solved in a more recent version of webchat
bugreport in github
I decided to try out Firebase hosting and wanted to start fresh so I deleted my one and only app, but when I tried to create a new app with the same name I was unable to due to the error:
"This Firebase URL is not available"
I can only guess this is because of caching of app names/URLs? Hopefully it will become available (unless someone else beats me to it) after some timeout? Any info from others who have experience with this issue or otherwise know the answer is appreciated!
Not sure whether this is the right place to ask although Firebase suggest coming to SO because they apparently monitor Firebase-related questions closely according to their website.
Thanks!
Once you delete a Firebase URL, it is permanently unavailable. It cannot be recovered.
During confirmation, you should see a message like this, which explains in detail:
This stems from a number of abuse vectors that are possible by misappropriating a project id that the prior owner believes is deleted and could still have apps/releases in the wild attached to the defunct backend. Since compliance requires that we purge all data related to the project, including information about ownership, there's not even a way to restore one you personally deleted.
I built my first forefox addon and trying to submit it but when I try to submit if gives an error
Your add-on failed validation with 1 error.
There was a problem contacting the server.
It doesnt give any other error or warning. What does the above error mean. Did any one else face this problem?
Sounds like a temporary outage. Or your add-on really crashes the validator.
Having said this, SO isn't really the AMO support forum...
Better suited places would be the AMO forums, the AMO editors mailing list amo-editors#mozilla.org or the #amo and/or #addons IRC channels on irc.mozilla.org.
You may also run the validator locally if you're adventurous, but the correct setup of the tool can be quite a hurdle...
As of 2013-04-16 WEST, the official getting started example of the YouTube iframe API results in error messages when run in Chrome 25 on WinXP/SP3:
I am accessing the example hosted on a web server, i.e. not via the local file system.
Am I doing something wrong? Is the example / the API broken? Can you reproduce the issue?
This error message has been around for quite a while -- as this Google Group post explains, it's due to an unresolved (4-year unresolved!) bug in WebKit:
https://groups.google.com/forum/?fromgroups=#!topic/youtube-api-gdata/VKGl4ahBGyk
It shouldn't affect anything -- it certainly hasn't for our projects, and in visiting the demo URL you posted, it looks like it isn't affecting the API functionality there (i.e. in that demo, the video still stops after 6 seconds per what the code states). There was an SO question a while back that thought it might be affecting analytics:
youtube "Unable to post message to..." causing video analytics to not be tracked
But it was never confirmed as being relevant.
It will be interesting to see if Chrome's move to the new Blink fork of WebKit leads to the bug itself being resolved.