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
Always
Expected results use the same anonymous user ID with every session
Actual Results every time I log in with the anonymous user Realm generates a new user with a different ID so I can not trace the user
No response
var app by mutableStateOf( App.create("appid"))
val anonymousCredentials = Credentials.anonymous(reuseExisting = true) user = app.login(anonymousCredentials) println("userId"+user!!.id)
kotlin SDK 1.16.0
Both Atlas Device Sync and Atlas App Services
No
windows 10
Android Studio version: ... Android Build Tools version: ... Gradle version: ...
The text was updated successfully, but these errors were encountered:
➤ PM Bot commented:
Jira ticket: RKOTLIN-1081
Sorry, something went wrong.
This is a duplicate of realm/realm-core#7709.
No branches or pull requests
How frequently does the bug occur?
Always
Description
Expected results
use the same anonymous user ID with every session
Actual Results
every time I log in with the anonymous user Realm generates a new user with a different ID so I can not trace the user
Stacktrace & log output
No response
Can you reproduce the bug?
Always
Reproduction Steps
var app by mutableStateOf( App.create("appid"))
val anonymousCredentials = Credentials.anonymous(reuseExisting = true)
user = app.login(anonymousCredentials)
println("userId"+user!!.id)
Version
kotlin SDK 1.16.0
What Atlas App Services are you using?
Both Atlas Device Sync and Atlas App Services
Are you using encryption?
No
Platform OS and version(s)
windows 10
Build environment
Android Studio version: ...
Android Build Tools version: ...
Gradle version: ...
The text was updated successfully, but these errors were encountered: