-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Realm 2.7.0 Crash on Launch #4972
Comments
We have a similar situation with two of our apps, each using their own Realm schema. The crash is EXC_BAD_ACCESS. It occurs when shouldCompactOnLaunch is active (in our testing, we have the block always return true) and we iterate through an RLMResults object.
In the above case, we're getting the referenced realmObjects here:
Followed by self.realmObjects.count to get the row count. Our other app's crash looks like this:
The Results object lookup: guard let jobs = realm?.objects(Job.self).sorted(byKeyPath: “someProperty”, ascending: false)
for job in jobs { The app crashes at the for loop. |
I also! |
Please share an Xcode project and steps to reproduce that we can follow in order to identify the issue. |
@shaysemireg was kind enough to provide a reproducible case via email, which makes the problem very clear. When |
Fixed in realm/realm-object-store#470, which was included in 2.8.1. |
Goals
shouldCompactOnLaunch
without crashExpected Results
Actual Results
Steps to Reproduce
Code Sample
Version of Realm and Tooling
Realm framework version: 2.6.1 / 2.7.0
Realm Object Server version: N/A
Xcode version: 8.3.2
iOS/OSX version: 10.3.1
Dependency manager + version: CocoaPods 1.0.1
The text was updated successfully, but these errors were encountered: