I am getting this crash on many users in my application which is on the play store. I don't understand the reason because logcat showing in crashlytics is weird.
Fatal Exception: java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState
at android.app.FragmentManagerImpl.checkStateLoss(FragmentManagerImpl.java:1882)
at android.app.FragmentManagerImpl.enqueueAction(FragmentManagerImpl.java:1905)
at android.app.BackStackRecord.commitInternal(BackStackRecord.java:688)
at android.app.BackStackRecord.commit(BackStackRecord.java:646)
at com.jojoy.delegate.JojoyInstallerActivity.switchContent(JojoyInstallerActivity.java:78)
at com.jojoy.delegate.JojoyInstallerActivity.access$000(JojoyInstallerActivity.java:35)
at com.jojoy.delegate.JojoyInstallerActivity$FragmentHandler.handleMessage(JojoyInstallerActivity.java:139)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:246)
at android.app.ActivityThread.main(ActivityThread.java:8633)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:602)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1130)
Here, what is this JojoyInstallerActivity? I don't understand totally. because I am not using it in my whole application. Even I tried to search on google but didn't find a single piece about that.
Related
I am getting this below crash on fresh app install. This happens only once. If I restart the app the crash won't happen. Event after clear app data the crash doesn't happen. Any solution for this?
Fatal Exception: java.lang.RuntimeException: Illegal meta data value: the child service doesn't exist
at Fj.a(Fj.java:95)
at org.chromium.content.browser.ChildProcessLauncherHelperImpl.a(ChildProcessLauncherHelperImpl.java:134)
at tk.run(tk.java:434)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:233)
at android.os.Looper.loop(Looper.java:344)
at android.os.HandlerThread.run(HandlerThread.java:67)
Some week ago I noticed crashes in Crashlytics:
Fatal Exception: java.lang.IllegalArgumentException: Activity client record must not be null to execute transaction item
at android.app.servertransaction.ActivityTransactionItem.getActivityClientRecord(ActivityTransactionItem.java:85)
at android.app.servertransaction.ActivityTransactionItem.getActivityClientRecord(ActivityTransactionItem.java:58)
at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:43)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2438)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8663)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)
Seems it occurs on app start but 100% on Android 12 and 95% on samsung (75% samsung Galaxy A51) devices. I checked on A51 but for me it works fine and I can't reproduce the issue. Maybe someone already solved this issue or has some insight into what or where could be something wrong? Thanks!
Looks like this is a bug in Android that has been fixed, but not rolled out fully yet. Ref:https://issuetracker.google.com/issues/210886009
My app got "android.app.RemoteServiceException" exception. I've use the "JobScheduler" to instead of "Service". It worked, besides OPPO 8.1.
That's all message i got.
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1987)
android.os.Handler.dispatchMessage(Handler.java:106)
android.os.Looper.loop(Looper.java:187)
android.app.ActivityThread.main(ActivityThread.java:7025)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:514)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:888)
This was happening for me too after migrating to JobScheduler. Turned out there were some alarms scheduled by the previous app version that would still try to launch the migrated service in the foreground. I fixed it by renaming the JobService class, that way the system could no longer locate it when one of those prior alarms would trigger.
I get this exception on occasion:
Context.startForegroundService() did not then call
Service.startForeground() android.app.ActivityThread.main
The fun thing is I have no idea from the stack traces when or where startForegroundService is being called. I know it's not in my code, but it could be in one of the 3rd party libs I'm using. Unfortunately, the stack traces are all but useless. Of course, I can't reproduce it reliably, that would be too easy! Does anyone have any tips/ideas on how to track down the origin?
Fatal Exception: android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground()
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1790)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6651)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:810)
If it is crashing "in the lab", you could look at Logcat to see what service was started ~10 seconds before the crash.
Beyond that, use the "Merged Manifest" tab in Android Studio's manifest editor and see what services are showing up in your manifest (plus, what libraries contributed those manifest entries). That at least narrows down which libraries might be the culprit. If any of those are open source, you could then poke through the source code to see if they seem to call startForegroundService().
On Pixel2 Phone, after we launched Instant App, we could see the Instant App Icon as the BuzzFeed icon shows on the top left of image
This is cool, as it allow one to open the Instant App with default URL on the phone.
However if we install the main App using the Copy-Into-Device-&-Install (e.g. Fabric Beta), the Icon didn't get replace. When we click on the Icon, it will try to launch the main App, but crashes with
Fatal Exception: java.lang.RuntimeException: Unable to create application com.mypackage.app.MyApplication: java.lang.SecurityException: uid 10166 cannot explicitly add accounts of type: com.mypackage.app.account
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5743)
at android.app.ActivityThread.-wrap1(Unknown Source)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1656)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6494)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
I think it's a google bug. But thought would be good to check out further if anyone know this is something we should handle on our main App instead.
(note: using GooglePlay to install the Main App doesn't cause the problem, as the Instant App Icon goes away and replace with the main App Icon)