breautek commented on issue #1510: URL: https://github.com/apache/cordova-android/issues/1510#issuecomment-1284184394
Actually, the ANR might not be related the splashscreen at all (well it could still be... I guess, considering the issue seems to only occur with the new splashscreen system), according to the [Android Docs](https://developer.android.com/topic/performance/vitals/anr), ANRs are triggered if the UI thread has been blocked for too long. > When the UI thread of an Android app is blocked for too long, an "Application Not Responding" (ANR) error is triggered. > ... >ANRs are a problem because the app’s main thread, which is responsible for updating the UI, can’t process user input events or draw, causing frustration to the user. For more information on the app’s main thread, see [Processes and threads](https://developer.android.com/guide/components/processes-and-threads). > An ANR will be triggered for your app when one of the following conditions occur: > > - While your activity is in the foreground, your app has not responded to an input event or [BroadcastReceiver](https://developer.android.com/reference/android/content/BroadcastReceiver) (such as key press or screen touch events) within 5 seconds. > - While you do not have an activity in the foreground, your [BroadcastReceiver](https://developer.android.com/reference/android/content/BroadcastReceiver) hasn't finished executing within a considerable amount of time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
