react-native-screens: 2.4.0 [Android] Crash: No view found for id 0x531 (unknown) for fragment ScreenFragment

Can you check if this PR fixes the issue and does not introduce any new ones: https://github.com/software-mansion/react-native-screens/pull/1006/files ? It should be enough to apply changes from ScreenContainer.java and ScreenStack.java. It would be really helpful to get feedback about it since we would probably merge it if it does not introduce any new problems.

I have been facing the same issue. Not able to reproduce this, but seeing a number of crashes on Crashlytics. Here are the dependencies I am using - I am passing null to super.onCreate

"@react-navigation/drawer": "5.1.1"
"@react-navigation/native": "5.0.9"
"react-native": "0.63.0"
"react-native-screens": "2.10.1"

Stacktrace -

Fatal Exception: java.lang.RuntimeException: Unable to pause activity {*.*.*/*.*.MainActivity}: java.lang.IllegalArgumentException: No view found for id 0xa9 (unknown) for fragment g{c2f6631} (3d710c8a-fa3f-42a1-a496-69d9773638ef) id=0xa9}
       at android.app.ActivityThread.performPauseActivityIfNeeded(ActivityThread.java:4078)
       at android.app.ActivityThread.performPauseActivity(ActivityThread.java:4033)
       at android.app.ActivityThread.handleRelaunchActivityInner(ActivityThread.java:4817)
       at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4756)
       at android.app.servertransaction.ActivityRelaunchItem.execute(ActivityRelaunchItem.java:69)
       at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
       at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
       at android.app.ClientTransactionHandler.executeTransaction(ClientTransactionHandler.java:55)
       at android.app.ActivityThread.handleRelaunchActivityLocally(ActivityThread.java:4806)
       at android.app.ActivityThread.access$3300(ActivityThread.java:200)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1841)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:201)
       at android.app.ActivityThread.main(ActivityThread.java:6823)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)

Caused by java.lang.IllegalArgumentException: No view found for id 0xa9 (unknown) for fragment g{c2f6631} (3d710c8a-fa3f-42a1-a496-69d9773638ef) id=0xa9}
       at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:18)
       at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:18)
       at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1)
       at androidx.fragment.app.FragmentManager.W(FragmentManager.java:47)
       at androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:9)
       at androidx.fragment.app.FragmentManager.dispatchPause(FragmentManager.java:2)
       at androidx.fragment.app.FragmentController.dispatchPause(FragmentController.java:2)
       at androidx.fragment.app.FragmentActivity.onPause(FragmentActivity.java:2)
       at com.pgapps.MainActivity.onPause(MainActivity.java)
       at android.app.Activity.performPause(Activity.java:7444)
       at android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1466)
       at android.app.ActivityThread.performPauseActivityIfNeeded(ActivityThread.java:4068)
       at android.app.ActivityThread.performPauseActivity(ActivityThread.java:4033)
       at android.app.ActivityThread.handleRelaunchActivityInner(ActivityThread.java:4817)
       at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4756)
       at android.app.servertransaction.ActivityRelaunchItem.execute(ActivityRelaunchItem.java:69)
       at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
       at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
       at android.app.ClientTransactionHandler.executeTransaction(ClientTransactionHandler.java:55)
       at android.app.ActivityThread.handleRelaunchActivityLocally(ActivityThread.java:4806)
       at android.app.ActivityThread.access$3300(ActivityThread.java:200)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1841)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:201)
       at android.app.ActivityThread.main(ActivityThread.java:6823)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)

Device coverage -

@WoLewicki Please let me know if any other info is required to help you debug.

We’re seeing the same issue in production. Working to find a device and replication steps.

@WoLewicki good news 🙂 the issue is gone adding the super.onCreate(null). False alarm from my side, sorry about that. The problem was that we still had quite many users with the older version of the app that was with this crash. I can’t force update them for now, but I will ask them to update the app manually if it shows up 👍

What a bummer! Had to uninstall react-native-screens because of this issue 😕 Tried using the latest version 3.0.0 on rn 0.63.3. The crash happens almost every time when I navigate to a stack screen which was the first screen of the app in react-navigation from a screen that is inside a tab navigator (Usually when someone presses logout) Also, the crash only happens on the play store release build and not on debug (Could it be a pro-guard issue?)

java.lang.IllegalArgumentException: No view found for id 0x215 (unknown) for fragment ScreenFragment{8fa1bf3} (e241da77-f232-46ca-ba62-2ed17e002540) id=0x215} at androidx.fragment.app.FragmentStateManager.a(FragmentStateManager.java:131)

Same here. Can’t reproduce on debug, only release apk

@WoLewicki I no longer work where I reported this issue, but have reached out to someone there to see if they can test

@WoLewicki I will test your PR and notice any problems here too.

@WoLewicki So far so good. Hasn’t crashed on me yet. I’ll continue to do some testing over the next couple of days.

Looking at our error logs, the large majority of crashes are on app start, of the ones not happening on app start, I don’t see any correlation with screens that have web views.