Develop Reference

Google Play reported app crash but did not point out where

Yesterday I uploaded my aab file to google play for a open testing. Google Play did report some app crashes in my app but it was not really clear, like below:
FATAL EXCEPTION: main
Process: com.boss.theblockhousev2, PID: 25729
java.lang.NullPointerException: throw with null exception
at g.c.a.j.a.h.g.b(:7)
at m.b.run(:1)
at android.os.Handler.handleCallback(Handler.java:790)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6523)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:857)
Detected on 1 device during testing:
Nokia Nokia 1
480x854
Android 8.1 (SDK 27)
1,024 MB
ARM_V7
en_US
How can I find my bug now? Please help.
Thank you guys a lot!

Use Firebase Crashlytics for that. It will tell you all the information like:-
Line of Code where the crash happened.
Exception
On Which Device
the crash occured, etc.

Unable to destroy activity Android: Google Play Console Error

I am trying to launch my app into Production on Google Playstore. I have used Flutter to create the app. But in the pre-launch report I am getting error:
Stacktrace:
java.lang.RuntimeException: Unable to destroy activity {com.stech.ebox_expenses/com.example.ebox_expenses.MainActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.lifecycle.e.c(androidx.lifecycle.h)' on a null object reference
FATAL EXCEPTION: main
Process: com.stech.ebox_expenses, PID: 12391
java.lang.RuntimeException: Unable to destroy activity {com.stech.ebox_expenses/com.example.ebox_expenses.MainActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.lifecycle.e.c(androidx.lifecycle.h)' on a null object reference
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:4504)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:4522)
at android.app.ActivityThread.-wrap5(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1697)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6647)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:811)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.lifecycle.e.c(androidx.lifecycle.h)' on a null object reference
at com.mr.flutter.plugin.filepicker.FilePickerPlugin.j(Unknown Source:21)
at com.mr.flutter.plugin.filepicker.FilePickerPlugin.e(Unknown Source:0)
at io.flutter.embedding.engine.c.h(Unknown Source:54)
at io.flutter.embedding.android.f.o(Unknown Source:58)
at io.flutter.embedding.android.e.G(Unknown Source:7)
at io.flutter.embedding.android.e.onDestroy(Unknown Source:11)
at android.app.Activity.performDestroy(Activity.java:7241)
at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1271)
at androidx.test.runner.MonitoringInstrumentation.callActivityOnDestroy(MonitoringInstrumentation.java:1)
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:4491)
... 9 more
I try to find anything discussing this and I found one Stackoverflow question which was recieved badly and downvoted; Here's a ref to the post. I am not to sure why this is happening and I am not sure whether it is external problem which I can fix or an internal bug.
When I downloaded the app from the Playstore when it was production, it displayed a white screen when I opened it and stayed like this. I am not sure if me getting this error is a result of that or not either.
Any help on the matter will be appreciated!

I have managed to fix both problems which I was having. I fixed the first problem of this error by updating file_picker library to version 2.10. The issue was fixed in version 2.0.12. I also fixed the second issue of the white screen in the app when it started by downgrading to: classpath 'com.android.tools.build:gradle:3.4.3'. Here's the reference to the post which helped me.

NPE on com.android.server.autofill.RemoteFillService$PendingRequest.cancel()

Crashlytics is reporting NullPointerException related to Auto Fill as shown below:
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method
'boolean com.android.server.autofill.RemoteFillService$PendingRequest.cancel()' on a null object reference
at android.os.Parcel.readException(Parcel.java:1965)
at android.os.Parcel.readException(Parcel.java:1905)
at android.app.IActivityManager$Stub$Proxy.reportAssistContextExtras(IActivityManager.java:8297)
at android.app.ActivityThread.handleRequestAssistContextExtras(ActivityThread.java:3210)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6944)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
Caused by android.os.RemoteException: Remote stack trace:
at com.android.server.autofill.RemoteFillService.cancelCurrentRequest(RemoteFillService.java:177)
at com.android.server.autofill.Session.cancelCurrentRequestLocked(Session.java:465)
at com.android.server.autofill.Session.access$1000(Session.java:118)
at com.android.server.autofill.Session$1.onHandleAssistData(Session.java:322)
at com.android.server.am.ActivityManagerService.reportAssistContextExtras(ActivityManagerService.java:14713)
However, the stack does not include anything from my app yet crash is happening on my side.

This is not an issue with your app but with specific Android OEMs. Seems to be happening more frequently on Samsung Devices and not seen on Pixel Devices. Here is an issue report to Google which is closed as 'Won't Fix'.
https://issuetracker.google.com/issues/123311621
Since the crash is happening because of autofill. I would recommend disabling autofill for the specific view by setting importanForAutofill as false/no.
https://developer.android.com/reference/android/R.attr.html#importantForAutofill

Instant app crash on Samsung device with Android O

I met a crash issue when instant app running on Samsung device, here is the crash log:
Fatal Exception: java.lang.SecurityException: Setting aod_show_state is not accessible from ephemeral package xx.xx.xx
at android.os.Parcel.readException(Parcel.java:1958)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.call(ContentProviderNative.java:651)
at android.provider.Settings$NameValueCache.getStringForUser(Settings.java:1923)
at android.provider.Settings$System.getStringForUser(Settings.java:2229)
at android.provider.Settings$System.getIntForUser(Settings.java:2299)
at android.provider.Settings$System.getInt(Settings.java:2294)
at android.view.ViewRootImpl$1.toViewScreenState(ViewRootImpl.java:1363)
at android.view.ViewRootImpl$1.onDisplayChanged(ViewRootImpl.java:1319)
at android.hardware.display.DisplayManagerGlobal$DisplayListenerDelegate.handleMessage(DisplayManagerGlobal.java:966)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6938)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
Seems like it's trying to access the aod_show_state Settings(which is the specific feature called "Always on Display" on Samsung device), and it requires permission WRITE_SETTINGS/WRITE_SECURE_SETTINGS, and the instant app does not support these two permissions, then app crashed...
Is there any way to solve this problem?

NullPointer on toLowerCase but I don't use that method anywhere

I'm getting the following crash dump in Firebase Crash Reports:
Exception java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.String.toLowerCase(java.util.Locale)' on a null object reference
bnp.run (bnp.java:56)
java.lang.Thread.run (Thread.java:818)
The problem is that I don't use the String.toLowerCase() method anywhere in the project. In Android Studio, I did Edit->Find In Path for the method and got no results, however, it does appear 100+ times if I search in the libraries. But I cannot find the "bnp.java" anywhere.
Thanks for your help!
Edit: A previous crash report was not proguard-affected and revealed it may be due to google-play-services or Firebase. I only use gms:play-services-places and gms:play-services-auth in my app, along with many Firebase dependencies.
Exception java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.String.toLowerCase(java.util.Locale)' on a null object reference
bnp.run (:com.google.android.gms.DynamiteModulesC:56)
java.lang.Thread.run (Thread.java:818)

I can't comment yet, so I will post this as a possible solution, but this seems like an error on Google's side. Multiple people are reporting this crash on the exact same device with the exact same region. So it seems Google runs your app on a virtual or automated device and then that device crashes. This device seems to be a Nexus 5x with local us-US and API level 23.
Source: https://code.google.com/p/android/issues/detail?id=233549

I got this error when my code was trying to create a connection to certain amqp service using an invalid URL. Once I modified it to the proper value, the exception is gone. So check your code.

My app ran into a similar issue.
When launched in Stock android devices(Mi A1), the App crashed with " keeps stopping popup". The Crashlytics in Fabric reported it as the
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.String.toLowerCase(java.util.Locale)' on a null object reference
at bfx.run(:com.google.android.gms.dynamite_dynamitemodulesc#13452060#13.4.52 (040708-202483333):80)
at java.lang.Thread.run(Thread.java:818)
But when I checked the Pre-launch report of the Release management in Google Play Console, it showed that the app was crashing for Pixel & Pixel 2 for an entirely different reason. The issue shown was
FATAL EXCEPTION: main Process: in.quickall.quickall, PID: 8345
java.lang.RuntimeException: Unable to start activity ComponentInfo{in.quickall.quickall/in.quickall.quickall.Main.MainActivity}: android.content.res.Resources$NotFoundException: Drawable in.quickall.quickall:drawable/splash_screen with resource ID #0x7f0700c0
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2817)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2892)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1593)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6541)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
And the issue started from the APK version were I implemented the code (given below) to remove the white screen on launch.
<style name="SplashTheme" parent="AppTheme">
<item name="android:windowBackground">#drawable/splash_screen</item>
</style>
I removed this piece of code and now the Pre-launch report shows it as working fine in the Pixel devices.
Now the app launches correctly, but has to have the white screen at launch.