Android Question [SOLVED] App crashes after SDK update

Computersmith64

Well-Known Member
Licensed User
Longtime User
[SOLVED] - After some searching, I found a thread that made reference to an updated FirebaseAnalytics library (v1.02) that fixes an issue with FirebaseAuth. It didn't specifically say that it fixes crashes related to the latest Firebase SDK, however I updated from v1.01 & it fixed the crashes I was seeing.

=======================================================
I ran the B4A SDK Manager tonight & updated all the packages it recommended - after which the app I had been testing immediately prior to the update now will not run at all on any device in any mode (rapid, legacy or release).

I initially got the "Maven artifact not found: com.google.android.gms/play-services-measurement-api" message when trying to compile, so I downloaded & installed the relevant packages & the app compiles & installs on the device (or emulator), however crashes as soon as it runs. There are no filtered logs. I do get a popup "Rapid debugger failed to connect..." message. Here is what is in the unfiltered logs at what appears to be the point of the crash:


- Colin.
 
Last edited:

Computersmith64

Well-Known Member
Licensed User
Longtime User
Trying a different app, I get this in the unfiltered logs:


I have updated all the analytics, fabric, etc... packages & I still can't get any apps to run. Something seems to have gone very wrong with the SDK update process.

- Colin.
 
Upvote 0

wizard699

Active Member
Licensed User
Longtime User
Only after SDK update and after have updated Firebase library, all applications crash!!!
And this is the rows that apper in log:

Logger connesso a: emulator-5554
--------- beginning of system
--------- beginning of main
** Receiver (startatboot) OnReceive **
*** Service (starter) Create ***
** Service (starter) Start **
** Service (startatboot) Create **
** Service (startatboot) Start **
** Service (starter) Destroy (ignored)**
** Service (startatboot) Destroy **
--------- beginning of crash

How can we resolve the problem? It's a big problem!!! Something was wrong in SDK update!!!
 
Upvote 0

Computersmith64

Well-Known Member
Licensed User
Longtime User

Not seeing a crash in that log. That "---------- beginning of crash" I think just indicates that crash logging is enabled. Are there any other messages in the logger? What is the problem you're having?

- Colin.
 
Upvote 0

wizard699

Active Member
Licensed User
Longtime User
In the filtetred Log ... nothing else.
Every app I've developed and use firebase libraries .... goes in crash at the moment of execution.
 
Upvote 0

Computersmith64

Well-Known Member
Licensed User
Longtime User
In the filtetred Log ... nothing else.
Every app I've developed and use firebase libraries .... goes in crash at the moment of execution.
You're not really giving us much to help you with. Have you looked in the unfiltered logs for an indication of what's causing the crash? Have you updated the FirebaseAnalytics library to v1.02 (as mentioned in the edit of my first post)?

Honestly - posting "my app crashes" & then no other information doesn't help the other members of this forum help you.

- Colin.
 
Upvote 0

wizard699

Active Member
Licensed User
Longtime User
I've a new problem after I've update today last required sdk files.
Now b4a doesn't contact the emulator .....
 
Upvote 0

wizard699

Active Member
Licensed User
Longtime User
I want to say that something strange was happned with two last update of sdk.
I've changed nothing else then SDK .... and now also communication with emulator .... is a problem.
Something serious happened because now I can not even test apps in emulation anymore.
It's all linked.
 
Upvote 0

Computersmith64

Well-Known Member
Licensed User
Longtime User

Sometimes SDK updates are breaking - ie: they change / remove / add functions, properties, etc... & require the associated B4A libraries to be updated. The problem with your posts to this forum is that you aren't providing any information that can be used to help you. You've been posting requests for help & then completely ignoring the responses.

So:

* Which two SDK updates are you referring to? (versions?)
* What errors / messages are you seeing in the filtered & unfiltered logs in B4A?
* Which Libraries & versions are you using in your app(s) that are having issues?
* What steps are you taking to troubleshoot the issues & what are the results?
* Have you updated your FirebaseAnalytics library to v1.02?

I'd suggest that before you post any more questions, you take a look at this thread -> https://www.b4x.com/android/forum/threads/how-to-ask-a-question.9140/

If you want to answer some (or all) of the various questions I've asked in my responses to your posts, then I'll try to help you - otherwise I'm out.

- Colin.
 
Upvote 0

wizard699

Active Member
Licensed User
Longtime User
SDK: all required file that B4A SDK Manager have suggested in these last two days

Error: in unfiltered log now appear this error

Failed to load crash reporting
com.google.android.gms.internal.measurement.zzyc: com.google.android.gms.dynamite.DynamiteModule$LoadingException: No acceptable module found. Local version is 0 and remote version is 0.
at com.google.android.gms.internal.measurement.zzyb.zztc(Unknown Source)
at com.google.firebase.crash.zzc.zzta(Unknown Source)
at com.google.firebase.crash.zzd.call(Unknown Source)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
Caused by: com.google.android.gms.dynamite.DynamiteModule$LoadingException: No acceptable module found. Local version is 0 and remote version is 0.

and this

java.lang.NoSuchMethodError: No virtual method isDataCollectionDefaultEnabled(Landroid/content/ContextZ in class Lio/fabric/sdk/android/services/common/FirebaseInfo; or its super classes (declaration of 'io.fabric.sdk.android.services.common.FirebaseInfo' appears in /data/app/in.raguso.educom-2/base.apk)
at com.crashlytics.android.core.CrashlyticsCore.onPreExecute(CrashlyticsCore.java:216)
at com.crashlytics.android.core.CrashlyticsCore.onPreExecute(CrashlyticsCore.java:209)
at io.fabric.sdk.android.InitializationTask.onPreExecute(InitializationTask.java:44)
at io.fabric.sdk.android.services.concurrency.AsyncTask.executeOnExecutor(AsyncTask.java:611)
at io.fabric.sdk.android.services.concurrency.PriorityAsyncTask.executeOnExecutor(PriorityAsyncTask.java:43)
at io.fabric.sdk.android.Kit.initialize(Kit.java:69)
at io.fabric.sdk.android.Fabric.initializeKits(Fabric.java:440)
at io.fabric.sdk.android.Fabric.init(Fabric.java:384)
at io.fabric.sdk.android.Fabric.setFabric(Fabric.java:342)
at io.fabric.sdk.android.Fabric.with(Fabric.java:313)
at com.crashlytics.android.CrashlyticsInitProvider.onCreate(CrashlyticsInitProvider.java:27)
at android.content.ContentProvider.attachInfo(ContentProvider.java:1751)
at android.content.ContentProvider.attachInfo(ContentProvider.java:1726)
at android.app.ActivityThread.installProvider(ActivityThread.java:5811)
at android.app.ActivityThread.installContentProviders(ActivityThread.java:5403)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5342)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1528)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6077)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:866)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:756)


Library:
FirebaseAdMob (1.52)
FirebaseAnalytics (1.02)
FirebaseNotifications (1.21)
FirebaseRemoteConfig (2.01)
 
Upvote 0

asales

Expert
Licensed User
Longtime User
A little tip: make an backup or copy the folder of your SDK before update it.
I had a similar problem and to not stop my work, I restored the folder the previous SDK and will check the problem later.
 
Upvote 0
Cookies are required to use this site. You must accept them to continue using the site. Learn more…