Conversation
Extract docId once from the incoming JSON and use it for Realm lookups/creation (changed query key from "_id" to "id"). When creating or fetching the RealmCourseProgress, assign the _id field explicitly and avoid repeated JsonUtils calls. This ensures correct lookup/creation of course progress records and that the _id is populated on the Realm object.
dogi
changed the title
dogi
approved these changes
Apr 20, 2026
…rash-due-to-duplicate-primary-key-during-bulk-sync
Okuro3499
deleted the
13014-realmprimarykeyconstraintexception-crash-due-to-duplicate-primary-key-during-bulk-sync
branch
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
fixes #13014
duplicates are found correctly via the PK lookup, and the object's _id field is always populated so any existing code that queries by _id elsewhere also works