-
Notifications
You must be signed in to change notification settings - Fork 582
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
Reload leads to SIGSEGV or "Error: no internal field" #5904
Comments
It seems I'm able to reproduce this on iOS as well:
I can share more details confidentially if it would help. |
@durasj Which version of Expo do you use? |
@kneth 48.0.18 - the latest one. As I've mentioned in the steps to reproduce this, it happens when creating a new project from the expo template, so the latest one. The video shows exact versions, but those are basically the latest ones one gets from the template. |
@kneth is there please anything else needed from my side considering the "Waiting-For-Reporter" label? |
It looks like our automation bot didn't pick it up quickly enough. No need for you to do something. We have experienced issues with reloads, and unfortunately we don't know the root cause yet. It is unrelated to Expo as it also happens with you use React Native alone. We need to investigate it. |
Thanks, @kneth. It happens almost every single time on our project, so there is no need to reload several times as I did in the video. It looks like some kind of a race condition, but it's not clear to me - yet - what on our project causes it to happen more often. That's something I will try to find out once the time permits - likely next week. So far, I've tried to take the template and:
Next, I'll slowly try to copy the rest of the setup - the expo router, e.g., is a major difference. |
Still present |
How frequently does the bug occur?
Sometimes
Description
Reloading the app (pressing
r
) either leads to a crash withSIGSEGV
or an errorError: no internal field
once the Realm is accessed. There is no crash or error on the first lunch.Stacktrace & log output
Can you reproduce the bug?
Always
Reproduction Steps
This is reproducible almost 100% of the time on our project, but it can also be reproduced using the
@realm/expo-template
:expo init MyAwesomeRealmApp --template @realm/expo-template
.yarn android
.r
a couple of times.Video:
Screencast from 2023-06-17 20-04-00.webm
On our project, almost every reload leads to this problem. On the template it requires a few reloads - I haven't figured out why that is.
Version
11.7.0
What services are you using?
Local Database only
Are you using encryption?
No
Platform OS and version(s)
Android 12
Build environment
Which debugger for React Native: ..
Cocoapods version
No response
The text was updated successfully, but these errors were encountered: