I suspect you're running into a known issue in the 100.6 release, which will be addressed by the upcoming 100.7 release. We aim to have that wrapped up soon...
Thanks Michael. If that's the case we can probably put this issue to rest until 100.7 is released. The only side effect is that the user has to log in every time they open the app.
It is not fixed, at least in our use case. We'll start up a ticket. Any bug numbers or other ticket numbers we can put on the ticket so its easier to associate with the original issue?
During the investigation of the original issue, we did note some cases that required additional work. This was undertaken in the 100.8 release lifecycle.
I'd like to share a current 100.8 preview with you: which of the .NET SDK APIs are you referencing? (Android, iOS, UWP, and/or WPF)
We've noticed the issue on Xamarin (iOS) and WPF. We'd love to test in both places.
For reference, our workflow is very similar to Johnathan's. We store the refresh token on login. It is placed in the Runtime's OAuth authentication API's on start of the app, or after login. We know we've needed to call RefreshTokenAsync in order to get Runtime to work correctly with federated services. Our code:
var serverInfo = new ServerInfo
ServerUri = portalUri,
TokenAuthenticationType = TokenAuthenticationType.OAuthAuthorizationCode,
ClientId = appClientId,
RedirectUri = redirectUri
var cred = new OAuthTokenCredential
Token = accessToken,
OAuthRefreshToken = refreshToken,
ServiceUri = portalUri,
GenerateTokenOptions = new GenerateTokenOptions
TokenAuthenticationType = TokenAuthenticationType.OAuthAuthorizationCode