Skip to content
New issue

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

Peculiar behaviors when deleting the offline map #78

Open
mikewilburn opened this issue Oct 30, 2019 · 4 comments
Open

Peculiar behaviors when deleting the offline map #78

mikewilburn opened this issue Oct 30, 2019 · 4 comments

Comments

@mikewilburn
Copy link
Contributor

mikewilburn commented Oct 30, 2019

On WPF:

If you delete the currently-stored offline map, the application will throw an I/O exception like this one:

image

Clicking 'OK' successfully restarts the app and reveals the offline map is indeed deleted.

However, attempting to take offline a new section of map throws this same exception. The behavior loops and I haven't figured out how to work offline yet because of it.

On UWP:

If you delete the offline map, the application will crash right away.

The application can be re-launched just fine and reveals the offline map is indeed deleted, but on a few occasions, I've been re-prompted to sign in. Seems the crash may also force signing out the user?

@mikewilburn
Copy link
Contributor Author

Deleting the offline map is now throwing this error:

WPF UWP
image image

Clicking 'OK' and attempting to re-log-in (ensuring I've used the correct credentials) throws the error:

Map Failed to Load: Response status code does not indicate success: 401 (Unauthorized)

Moreover, I'm still apparently logged in and have an offline map:

CLICK TO EXPAND

image

@nCastle1
Copy link
Collaborator

The remaining errors are a result of an authentication manager bug involving OAuth refresh tokens that is resolved at 100.7. This issue should be resolved by #84

@mikewilburn
Copy link
Contributor Author

@nCastle1 do we need to re-test to ensure that this one was resolved when #84 was merged?

@nCastle1
Copy link
Collaborator

@mikewilburn Yes, I think additional testing would be in order to confirm that this is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants