Update RealmSwift version to 3.18 #34
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
can you explain more about
Got any issue link? |
|
I found the issue by myself because I used both RealmSwift and ChartsRealms in the same project. There is the problem with RealmSwift and I need to update to v.3.18 but the error from ChartsRealm prevent me from doing it. I got the solution from https://stackoverflow.com/questions/48810421/rlmexception-primary-key-property-serial-does-not-exist-on-object-book-mig I tested and it works now. |
|
sure thanks. I will work on this after Charts is released. thank you for your patience. |
|
@neetrath did you get warnings for ChartsRealm on Xcode11? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's an issue with iOS 13 and Xcode 11 which may cause the "Primary key property '' does not exist on object". All String properties of Realm classes with a default String value set are disregarded somehow. You can fix this by updating RealmSwift to the latest version (currently 3.18.0)