You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Realm 11.9.0 and 12.3.1 (I suppose it since 12.0.0) have different behavior when setting the embedded object field to null.
While 11.9.0 allows us to do it, 12.3.1 doesn't set null to an object field. Will it be fixed, or are these new validation constraints?
Stacktrace & log output
No response
Can you reproduce the bug?
Always
Reproduction Steps
I've created an example to show the difference between Realm 12.3.1 and 11.9.0.
First, sorry for the late reply. Second, thank you for the bug request. Unfortunately we have had a chance to investigate it yet, but I will bring it up with the next early next week.
How frequently does the bug occur?
Always
Description
Realm 11.9.0 and 12.3.1 (I suppose it since 12.0.0) have different behavior when setting the embedded object field to null.
While 11.9.0 allows us to do it, 12.3.1 doesn't set null to an object field. Will it be fixed, or are these new validation constraints?
Stacktrace & log output
No response
Can you reproduce the bug?
Always
Reproduction Steps
I've created an example to show the difference between Realm 12.3.1 and 11.9.0.
https://github.com/andreyukD/reproduce-realmjs-issue (branch v12-3-1)
Starting point was
npx create-expo-app MyAwesomeRealmApp --template @realm/expo-template
I've added a new field
items
inTask
schemacommit with 12.3.1 - andreyukD/reproduce-realmjs-issue@8270070
commit with 11.9.0 - andreyukD/reproduce-realmjs-issue@b1ce350
v11-9-0.mp4
v12-3-1.mp4
Version
12.3.1 / 11.9.0
What services are you using?
Local Database only
Are you using encryption?
No
Platform OS and version(s)
macOS 14.0
Build environment
Which debugger for React Native: ..
Cocoapods version
No response
The text was updated successfully, but these errors were encountered: