-
Notifications
You must be signed in to change notification settings - Fork 572
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
React Native android app crashes on restart after integrating Realm (v0.73.2, Realm v12.5.1, @realm/react v0.6.2) #6433
Comments
@AaronDsilva97 It is possible to provide a small app which can reproduce the crash? It will make it easier for us to investigate it. |
Same here, to reproduce, just init a new react native project, add the realm and @realm/react dependencies, and wrap the app with Steps:
|
I'm getting a similar error. |
This happens to me too. I guess this might help.
It goes in Navigation page added in fallback.
First console gets printed and the second doesn't. Error - Error: No user found. Did you forget to wrap your component in a UserProvider? Happens every time I make a build in Android. Not sure about iOS. It was working in @realm/react v0.4.1 |
same issue |
Having the same problem, tried following some other advice about putting the providers into their own files/wrappers which sadly didn't fix the problem either. Same issue when running it on ios as well. Here's a clean repo using expo with prebuild: https://github.com/BubbleTrouble14/RealmCrash |
Same issue here, above reproductions causes the error, we also get it after making a clean project with: |
Same issue here. "realm": "^12.3.0",
|
Issue is still present, it hapens for us often after a restart from Expo Updates. I mean it bassicly happens on every kind of restart (but not 100% of the time as others mentioned above)
|
The same error for me, how to fix it, any help would be appreciated |
https://github.com/BubbleTrouble14/RealmCrash This reproduction is giving me exact same result, is this a core issue in realm? @kneth |
I have same issue after integrating realm 12.6.2, and I reported a related issue: #6542 |
I am getting this error: "in realm open FAIL" whenever i am trying to access anything from realm. |
This is such a annoying thing while developing, android app crashed 90% of all reloads :( |
same issue, but the error is '#00 pc 0000000000363b74 /data/app/~~pU7ixGmBpZw1jO_0O32FFg==/EC4dcRGYNr2D4uJfLmFswQ==/base.apk!librealm.so (BuildId: edf6f0d435afef43e7dfceba74cfdd58b0289992)' |
I have exactly the same issue. Its also crashing in production version now and then without even sending anything to sentry |
SIGSEGV We do get segfaults now 😅🥲 |
This issue is still persist when hot reload with realm version 12.7.1 |
I am also facing same issue
|
Same issue
|
Still persist, it happens on EAS Update as well. |
any followup here? also experiencing this! |
I have change dev env don't report |
Is there any fix, patch, downgrade that has worked for anyone?. This is a bit weird, I really like Mongo Atlas and I was going to use this in a big project, but this is a giant bug, how is this not being elevated. I'm reevaluating spending money on Atlas if this can't be resolved and will probably re write my app with another stack, since random crashes in my realtime app are a critical bug. |
Seeing this in my app as well. Any help here would be really appreciated |
Is it related to #6824? |
@kneth looks promising, might be related to the bug. |
|
How frequently does the bug occur?
Always
Description
Android app crashes on restart
Stacktrace & log output
Can you reproduce the bug?
Always
Reproduction Steps
Version
12.5.1
What services are you using?
Local Database only
Are you using encryption?
No
Platform OS and version(s)
MacOS Sonoma 14.2.1
Build environment
Which debugger for React Native: ..
Using Flipper to debug
Cocoapods version
No response
The text was updated successfully, but these errors were encountered: