-
Notifications
You must be signed in to change notification settings - Fork 120
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 Object broke after ea87088 #300
Comments
Can confirm, I have the same problem. Took me a day to figure out what happened with the project. |
When using Xcode 10.2 you should use EVReflection version 5.10.1 or later. If cocoapods installs an earlier version, then you should upgrade cocoapods to version 1.7.0. |
@megavirus74 and @guilhermearaujo could you confirm that you are using EVReflection version 5.10 or later and still have this problem? |
@evermeer a while ago I decided not to use Realm anymore and switched to the regular EVReflection. |
If someone still has this issue, then just reopen this. |
I also encountered the same issue. Finally, I find source cause of this issue. I modified if let c = original as? EVCustomReflectable {
if let v = c.constructWith(value: value) {
value = v
}
} Then solved this issue of Realm crash. (But, this is a temporary solution) I think we need rethink how to "construct" better. |
@bennettyuan18 I will have a look at this later. Reopening this issue so that I won't forget. |
For anyone with the same issue for now you can use my fork in your podfile:
|
I am using EVReflection 5.7.0 and it works fine. After upgrading to 5.8.0 (or 5.90), my Realm Object models no longer work.
Nothing wrong happens during the deserialisation, but when I try to access one of their properties, I get a SIGABRT.
I tested each commit and found changes on ea87088 to be causing this.
This is my model declaration:
And this is some lldb data from the deserialised object:
Using 5.7.0, however:
The text was updated successfully, but these errors were encountered: