Closed bdash closed 6 years ago
The second stack trace matches #2673, but the first does not.
@finnschiermer If you need any additional info I will be happy to assist.
Any idea if the users experiencing this problem have something in common? Android versions? 32 vs 64 bit Hardware?
They all seem to be iOS 10.x on 64-bit HW.
@Reggian Earlier you wrote: "I have managed to obtain the realm db file from one of the crashing apps but when swapping the container with the obtained db the app on my phone launches without crashing."
Question 1: What does the word "container" refer to in this context? Question 2: Do I understand you correctly, that the same realm file will consistently crash the app when opened on one device, but not when opened on another?
On iOS I can replace the app "container", that means all data crated with the app (e.g. realm file, other temporary files etc.) So I have replaced the realm file my app created on my phone with the one I have managed to obtain from one of the users experiencing the crash.
After doing so my app did not crash the first time around. When I repeated the procedure with a file from another user experiencing the crash my app crashed on every launch with the second stack trace posted in the original post.
Aha I see what is the cause of the misinterpretations.
Crashlytics has a strange grouping mechanism. They have grouped all realm crashes that crash on the line realm::util::terminate(char const*, char const*, long)
together, regardless of the stack trace...
This is probably why the realm file from the first user did not crash my app and the one from the second user did.
This also explains your post:
The second stack trace matches #2673, but the first does not.
I am sorry I did not notice this sooner.
@Reggian Are you willing to share the realm file with us? Perhaps I can get something out of it. Perhaps not.
@finnschiermer Unfortunately I can not since our user's data is in it. I can however send you Realm Browser crash logs (when opening those realm files). If you have some instructions on how to obfuscate the user's data we should get in touch on a private channel.
@Reggian I'm sorry, but there is no safe way to obfuscate the users data while still allowing me full access to the relevant meta-data. I also won't get anything from the Realm Browser :-(.
@finnschiermer The same story comes here: https://github.com/realm/realm-cocoa/issues/5617 Do you know something new about this?
The core version used here is very old. Closing as there is no more new information to gather from this.
@Reggian commented on Wed Aug 23 2017
Hi,
I am experiencing consistent crashes for some users. Can anyone please help me solve this?
Goals
I am trying to initialise the realm with a custom configuration (migration purposes).
Expected Results
I have provided the
error
object. The realm initialisation should returnnil
with the filled error and not crash the app.Actual Results
For a small number of users the app constantly crashes upon launch. Here is the stack trace obtained via Crashlytics:
Steps to Reproduce
I can not find the steps to reproduce. I have managed to obtain the realm db file from one of the crashing apps but when swapping the container with the obtained db the app on my phone launches without crashing.
Code Sample
MYDataStore.m
RLMRealm+MYDefaultRealm.m
Version of Realm and Tooling
@Reggian commented on Thu Aug 24 2017
I have managed to obtain another problematic realm file. This is what I have stumbled upon when launched from the app.