2.4.0 [Android] Crash: No view found for id 0x531 (unknown) for fragment ScreenFragment #463
Comments
|
Hey @henrymoulton, thank you for reporting. Is this crash something you can reproduce locally, or just traces collected from the app running in production? |
|
Thanks for responding @kmagiera, this was collected in production. We’ve since turned Screens off and not had this crash. |
|
Just got a similar stack trace on production today as well: It's slightly different from what @henrymoulton has attached as mine clearly has an |
|
We're seeing the same issue in production. Working to find a device and replication steps. |
|
We have the same issue in production. According to logs in Crashlytics we know that it happens on screens with webview. |
|
@ardentum if you are talking about #105 (comment) as a workaround, it only works on |
|
@WoLewicki Yes, I mentioned your comment for #105. We use |
|
Hmm Ok, @adkenyon @henrymoulton @akontaroudis can you elaborate on if this crash happens only on screens with |
|
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. |
|
Not sure if related to this issue 100%, but I have noticed an increasing amount of crashes also in our prod release for Here's the last step of the stacktrace: If any other info is needed, I'm happy to help 🙂 |
|
@pedpess do you pass null to |
|
Hi, I am getting this error in production build of our app,: |
|
@WoLewicki Yes I do, first I initiate the After that, I invoke |
|
@pedpess no, it is not recommended, just thought maybe you didn't do it since from the stack trace it seems like the crash happens in |
|
@WoLewicki Sorry for the delay. I think we don't use These are the top 10 devices with this crash: |
|
@pedpess based on the stack trace, it looks like you are not passing |
|
@WoLewicki good news 🙂 the issue is gone adding the |
|
@akontaroudis @ANIBIT14 can you provide a repo with the configuration needed to reproduce the issue? Your crashes are caused by |
|
I have been facing the same issue. Not able to reproduce this, but seeing a number of crashes on Crashlytics. Stacktrace - Device coverage - @WoLewicki Please let me know if any other info is required to help you debug. |
|
@anirudhagarwal365 (and others), if you want to help, please provide some details of when the crashes happen in the lifecycle of the app. It looks like they happen only when pausing/resuming the activity, so if you would try to reproduce it to provide a repo, this is the direction I would go. You can try to make the app go into the background and then back. The important information would be if it happens when there is no navigation happening, or maybe only if e.g. you switched the screen and immediately paused the activity. You can also try #556 (comment) and see if it helps. |
|
@WoLewicki We tried out the fix you pointed in our production app. This seemed to have reduced the number of crashes, but recently we faced another crash at here. The stacktrace is - |
|
Actually the above PR actually fixes this issue(related to onPause). The stacktrace shared above is for another crash. @WoLewicki Any insights on the above mentioned crash? Wanted to check with you, since we have moved to sync implementation of committing fragments, would it be safe to remove executePendingTransactions() from onUpdate method in ScreenContainer class? |
|
I cannot help you much because I need a repo with a reproduction to work on it and see how the behaviors change. You can try and remove it, maybe it is forbidden when there are only synchronous transitions. It would be best if you could make a repo in which any of these crashes can be seen, otherwise, there is very little I can do. |
|
Any workaround about this? |
|
What a bummer!
|
|
So I think I found where the issue is |
|
@shubhamverma27 can you provide a test example in TestsExample project (https://github.com/software-mansion/react-native-screens/tree/master/TestsExample) with minimal configuration needed to reproduce the issue? There still isn't one for this issue so there is not much we can do about it. Setting |
|
Same here. Can't reproduce on debug, only release apk |
|
I'm having the same issue in release. The app crashes on launch. "react-native-screens": "~3.0.0",
"react-native": "https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz",
"react-native-gesture-handler": "~1.10.2",
"@react-navigation/bottom-tabs": "^5.11.7",
"@react-navigation/drawer": "^5.12.3",
"@react-navigation/material-top-tabs": "^5.3.15",
"@react-navigation/native": "^5.9.2",
"@react-navigation/stack": "^5.14.2",
"expo": "^41.0.0",This is an Expo Managed app using the native stack throughout the app. I'm reticent to switch to the default stack due to the performance impact. |
|
@ideopunk please provide the reproduction of the crash so we can work on it. |
|
I'm also receiving this error. It appears that we are getting it when the app is going to a background state. I've gone through a good number of logs and they all show the below output before crashing Here is the crash as logged in Sentry Here are my related packages: |
|
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 |
|
@WoLewicki So far so good. Hasn't crashed on me yet. I'll continue to do some testing over the next couple of days. |
|
@WoLewicki I will test your PR and notice any problems here too. |
|
It still crashes for me on release and debug both
Here is my main activity java
|
|
@WoLewicki I no longer work where I reported this issue, but have reached out to someone there to see if they can test |
|
@akshaymulgavkar can you post the whole stacktrace? It looks like the problem from #17, not this issue. |
|
I managed to fix this using react-navigation/react-navigation#7242 (comment) this approach |
|
same issue but i don't think so this is good options any other work around please |
|
@Hatta-Food-Hub switching |
Thank you for the reply <Tab.Navigator |
#54 was closed, I'm creating a new issue for the following dependencies:
Raw Exception:
MainActivity.java:
enableScreens()is called in the same way ashttps://github.com/software-mansion/react-native-screens/blob/master/Example/App.js#L16Additional information that might be helpful:
Android Versions:
Manufacturers:
Models
--
Thanks for all your help in advance!
The text was updated successfully, but these errors were encountered: