Activities of "mika"

Any updates on this case?

Github issue

Hi @ismcagdas I don't think so.. We run service in Azure as App service, and have the setting "Allways on" set on.

Also, since this problem does not happen on every user/device, I don't believe it is related to that.

For us, the workaround helped to prevent app crash, but we still get the refresh token failure. Now after 24h, some users must login again because refresh token fails to get new access token.

Hi @ismcagdas

This happens only on some users/tenants/sometimes. I have not experienced this, but my collegue has and multiple users are complaining about this. We also use Appcenter to log errors and this has caused several crashes since we updated to V7.3.1

We have also this exact problem

"System.InvalidOperationException: Navigation property 'Claims' on entity of type 'User' cannot be loaded because the entity is not being tracked. Navigation properties can only be loaded for tracked entities" there are some issues at Github for this line, for example this Latest maybe related issue, but that is closed without clear description of the fix.

The Xamarin app crashes because:

1. On startup, UserConfigurationManager.GetIfNeedsAsync() is called and because AppContext.Value.Configuration is null, it will call GetAsync();
2. App notices that login info exists, and uses token.
3. Token is expired => RefreshToken
4. RefreshToken call fails because of the server side problem
5. WebRequestExecuter.Execute will execute inbuild exception handling
6. In exception handling, L.Localize("Error") is called to generate Alert
7. In L.Localize => LocalizeInternal, there is a check that if appContext.Configuration == null => throw new Exception("Set configuration before using remote localization!");

This exception will crash your app :)

We are building a workaround for the UserConfigurationManager.GetIfNeedsAsync() call to ignore any exceptions and if refresh token fails, we will clear Login info and call GetAsync again to be able to navigate to the LoginView.

For Zero people, you should consider rethinking the startup process and make sure that the app will start on every situation.

Hi **@ismcagdas **

Could you tell me how did you test this as you said 4 months ago?

What is changed in latest version that should affect this problem?

Don't know why you closed this.. We use app center and we updated our app last sunday and I have seen one time this since but there was no log in app center.

Problem still exists and if next time problem happens to me and there is no log in our appcenter account, we need more hepl to pinpoint the problem.

Newer mind..

I tested app against my staging server and then changed base url to localhost and then I had staging server tenancy details so I think it messed things up..

I reinstalled app to my ios phone and now that api call works.

Now I took the refreshToken from mobile app, and with postman I was able to get new access token. But with that token, I got Unauthorized access with api call /api/services/app/User/GetUserForEdit?Id=5.

How tenancy is handled with apicalls?