We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The toEjson() function throws when using RealmValue. The following error will be encountered:
Missing encoder for type RealmValue
Define a Realm model with a RealmValue as a field.
Instantiate the model and then call the toEjson() function on the object.
Flutter 3.22.2
Atlas Device Sync
Flutter Application
Any
class $MyClass { @PrimaryKey() @mapto('_id') late ObjectId id;
late RealmValue realmValue; }
// instantiate and call toEjson() final object = MyClass();
// this throws an error: "Missing encoder for type RealmValue" object.toEjson();
No response
The text was updated successfully, but these errors were encountered:
➤ PM Bot commented:
Jira ticket: RDART-1076
Sorry, something went wrong.
Thanks for reporting. This happens to be a duplicate, so I will close this one.
Duplicate of #1737
nielsenko
Successfully merging a pull request may close this issue.
What happened?
The toEjson() function throws when using RealmValue. The following error will be encountered:
Missing encoder for type RealmValue
Repro steps
Define a Realm model with a RealmValue as a field.
Instantiate the model and then call the toEjson() function on the object.
Version
Flutter 3.22.2
What Atlas Services are you using?
Atlas Device Sync
What type of application is this?
Flutter Application
Client OS and version
Any
Code snippets
class $MyClass {
@PrimaryKey()
@mapto('_id')
late ObjectId id;
late RealmValue realmValue;
}
// instantiate and call toEjson()
final object = MyClass();
// this throws an error: "Missing encoder for type RealmValue"
object.toEjson();
Stacktrace of the exception/crash you're getting
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: