-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Crash on startup #6995
Comments
@kutran There should also be an exception message above the |
Unfortunately, these crash reports are from Google Play Vitals, so there isn't any more information before the **** line. |
I'm having the same issue. In my case, it affects only Samsung Galaxy users with Android 9 and 10. This bug is occuring periodically, so i'm assuming it has something to do with my BroadcastReceiver that is triggered by the AlarmManager. However, i can't find a bug there yet.
|
I'm having the same crashes since I've updated to Realm 7.0.1. |
I'd avoid 7.0.0; that one has #6875 |
I've tried to downgrade to version 7.0.0 anyway, with no luck. |
@MGaetan89 Have you tried 7.0.1? |
@johnsabilla same error. |
Am seeing this also on Samsung Active Tab 2, Android 8.1.... realm 7.0.1 |
In the end, I downgraded Realm back to version 6.1.0, as suggested here:
And so far it seems to work as expected. |
Do you have an idea what can I do if some of our users already updated their realm db format to 7.0.X? |
Did you try what's suggested in the comment I linked? |
Thank you for the reply, yes we were bouncing between the two possible solutions.
|
I'm seeing similar crashes on a lot of devices
Seen on: Running Android 9 and 10. Realm version: 7.0.1 |
We just released 7.0.2 with a number of bug fixes. We have reason to believe this issue was fixed. Unfortunately, we have not been able to reproduce it yet. But any feedback after upgrading to 7.0.2 would be appreciated. |
I'm still seeing the issue
From: |
I am getting another crash into crashlytics with 7.0.2, and it's pointing to a line where we do Samsung Galaxy A8(2018), Android 9:
The message seems similar to the issue in #7025 |
@ninaniiranen Thank you for that. It seems to be the same bug as described here: realm/realm-core#3836 |
Ok, we decided that we will roll back to 6.1.0 for every user because 7.X and 10.X was unstable. We saw this especially on Samsung devices and OnPlus devices, but on others too. The database got corrupted on: schema migration, realm file format migration, and simply by using it after a while it got corrupted after a while. If anybody is interested how we did it then please let me a message. |
@beczesz Is this case where Sync is involved? |
Closing due to inactivity. We believe all issues have been fixed. If it isn't the case for the one first reported, please reopen this ticket. For all others (@ninaniiranen, @mattfiocca, @diogochbittencourt, @MGaetan89, @MeinLieberScholli) please create new issues and we will track them separately as it appears to us they are not caused by the same native crash. We risk making a huge snowball if we keep track of everything in this one ticket. |
Goal
Stable app without crashes on startup.
Actual Results
Crash on startup.
Steps & Code to Reproduce
Version of Realm and tooling
Realm version(s): io.realm:realm-gradle-plugin:6.0.0
Realm Sync feature enabled: No
Android Studio version: 4.0
Android Build Tools version: 28.0.3
Gradle version: 6.1.1
Which Android version and device(s):
The text was updated successfully, but these errors were encountered: