Realms.Exceptions.RealmException
HResult=0x80131500
Message=A system error occurred while waiting for completion. See InnerException for more details
Source=System.Private.CoreLib
StackTrace:
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Realms.Sync.SessionHandle.d__8.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LexSemanticClient.ViewModel.LoginViewModel.d__81.MoveNext() in C:\Users\scf\Source\Repos\Utilities\LexSemanticClient\LexSemanticClient\ViewModel\LoginViewModel.cs:line 624
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LexSemanticClient.ViewModel.LoginViewModel.d__77.MoveNext() in C:\Users\scf\Source\Repos\Utilities\LexSemanticClient\LexSemanticClient\ViewModel\LoginViewModel.cs:line 540
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LexSemanticClient.Services.AppEnviromentService.d__129.MoveNext() in C:\Users\scf\Source\Repos\Utilities\LexSemanticClient\LexSemanticClient\Services\AppEnviromentService.cs:line 369
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LexSemanticClient.Views.Pages.VerbeteSearchPage.<VerbeteSearchPage_Appearing>d__25.MoveNext() in C:\Users\scf\Source\Repos\Utilities\LexSemanticClient\LexSemanticClient\Views\Pages\VerbeteSearchPage.xaml.cs:line 165
Inner Exception 1:
SessionException: InvalidSession
hey @Sergio_Carbonete - what kind of windows app is this ? You mention Xamarin - so is this the iOS version of the same app that works on Android or something else entirely?!
More info, My app work with more than User, switch between users. I change code to go login with error occurs, and is possible to login with other user. But it’s not possible get CustomData from first user receiving same error InvalidSession: invalid session: refresh token expired.
code: user.GetCustomData();
I’m confused - are you saying that the original InvalidSession error that you were hitting for Windows is now resolved and you are getting a new error with custom user data now?
@Ian_Ward sorry for confusion, problem not resolved, InvalidSession occurs for individual User, if i made login with another user(B) it’s ok. But if i try access data from first user (A) problem continuous.
I have a listview to admin all logged users, one(A) can’t access custom data receive InvalidSession and other (B) read ok.
Per the error message - it appears that user A’s refresh token expired. This means the user needs to reauthenticate in order to obtain a new refresh token. It’s a bug that the user wasn’t logged out automatically - we’ll resolve this in a future release, but for now you can just log the user out and then log them back in.
I have a problem to automatic login, same app/user can be in different devices and OS. I can’t store mail/password locally, i use mail/password credential provider. Because they can change password in other device.
Exist any LoginAsync method with Realm User stored in local Realm as parameter ?
Need to register this problem at github ?
Duplicate user’s at User page admin at realm.mongodb.com, is the same problem or another team will take it ?
You shouldn’t be storing credentials for the user. Instead, you should display a message saying their session has expired and they should re-enter their credentials.
The screenshot you’ve attached shows that the user IDs are truncated. My guess is that the final part of the IDs are different. You can verify that by clicking the copy button next to the ID and pasting it in some text editor.
@Sergio_Carbonete Can you share a code snippet for how you are logging in, opening the realm, and then checking that the user has logged in previously (and therefore can just use the cached user)