-
Notifications
You must be signed in to change notification settings - Fork 24.2k
-
Notifications
You must be signed in to change notification settings - Fork 24.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[android] IncompatibleClassChangeError: Couldn't find ReactProp.name crash on createContextInBackground #9354
Comments
Seems to be hitting other frameworks with other annotations on Samsung devices :( google/gson#726 |
Here is the Android bug tracker issue: https://code.google.com/p/android/issues/detail?id=172339 |
(it might be helpful if you cross post on that issue) |
@facebook-github-bot label Icebox |
Hi there! This issue is being closed because it has been inactive for a while. But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/android-incompatibleclasschangeerror-couldnt-find-reactpropname-crash-on-createcontextinbackground ProductPains helps the community prioritize the most important issues thanks to its voting feature. Also, if this issue is a bug, please consider sending a PR with a fix. |
@facebook-github-bot close |
@charpeni tells me to close this issue. If you think it should still be opened let us know why. |
Hey @lelandrichardson did you end up finding a fix to this? We're still seeing a lot of crashes on React native 0.53 with the same Stack trace, all Samsung 5.x devices. |
We are using React Native 0.30.0 and are seeing a (relatively infrequent) hard crash when running
createReactContextInBackground()
.This crash only happens on Android and, from what we can tell, seems to only be affecting Samsung devices.
It also only seems to be happening to devices running Android 5.0.x.
The crash appears to be reflection related. It says that
ReactProp
is missingname
. I cannot tell which ViewManager it appears to be crashing on, but for a sanity check I have double checked all of our viewmanagers and none of them are missing aname
prop.Full stack trace is here:
Has anyone else observed this? We haven't been able to reproduce on a device ourselves.
The text was updated successfully, but these errors were encountered: