-
Notifications
You must be signed in to change notification settings - Fork 990
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
temporary fix for realm issues #8367
Conversation
See: * #8366 * realm/realm-js#2282 * facebook/react-native#25060 Signed-off-by: Jakub Sokołowski <jakub@status.im>
Pull Request Checklist
|
Realm makes the bug more obvious but it seems these crashes happen a lot on 64 bits capable devices and are caused by RN, we'll have to follow up on facebook/react-native#24261 |
Jenkins Builds
|
100% of end-end tests have passed
Passed tests (49)Click to expand |
@jakubgs @yenda first launch of the app was fine but if close it and try to launch again then unfortunately, Status can't be launched and popup "Status PR has stopped" is shown. Steps:
full logcat: |
@jakubgs can you confirm that this is the only place where 64bits stuff has to be excluded? |
Yes. |
I've tested this on my OnePlus 6 with a Snapdragon 845 which a 64 bit cpu and it works fine. I tested as @annadanchenko did, with closing it and re-opening and everything worked fine. But then again I installed the nightly and it works just fine, so maybe this isn't just 64 bit specific, maybe it's CPU specific. |
This did not work for me. Using Samsung S6 Edge, Android 7. |
Thanks for the info, try #8368. |
Closing because #8368 is a better fix |
Dropping 64bit platforms as a temporary workaround for Realm.js issues in #8366.
We will have to undo-this using #8326 once Realm.js issue is fixed.
See for context: