Closed tholhubner closed 3 years ago
@steffenagger this is the crash I was asking about in the #3511 comment I made
@tholhubner
const anonUser = anonymousLogin()
-> const anonUser = await anonymousLogin()
-- anonymousLogin()
is an async function
partitionValue: "_partitionKey"
- is the value really _partitionKey
? Which partition key is configured server side but the value is set client side
Thank you @tholhubner.
@kneth yes, this looks like our validation accepts a Promise
, where it should only accept a User
- and fails quite ungracefully.
@kneth that is the partition value that I have setup in the admin, and in the code for the Schema.
I made the change, adding await to the anonymous login function call, but it still seems I am getting the same crash
@tholhubner The stack trace indicates that anonUser
is not a valid Realm.User
object. To verify it is, do you get some valid output from console.log("Logged in with the user: ", anonUser.identities)
?
Goals
I am attempting to open a synced Realm on iOS that I setup using the documentation on the mongoDB website.
Expected Results
Connected to synced Realm and continue in querying and writing.
Actual Results
The app crashes with an EXC_BAD_ACCESS. when running on an iPhone 11 simulator on iOS 14.4. Below is the crash report that I get from the crash, but I have to be honest, crash reporting is something I don't have much experience with. EXC_BAD_ACCESS-logs.txt
Steps to Reproduce
I am opening the app, logging in with an anonymous user and opening a realm that I created on the MongoDB web portal. I followed the instructions for a simply asyncronous connection from the documentation on the website as well. But as soon as I call
Realm.open(config)
the app crashes on me with an EXC_BAD_ACCESS.Code Sample
Below is the code that I am using when receiving this error.
Import Realm
Get the Realm App
Login with Anonymous user
Version of Realm and Tooling