Skip to content

Conflict of sessions when migrating to Parse Server #3380

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

Closed
MateusCarvalho opened this issue Jan 15, 2017 · 1 comment
Closed

Conflict of sessions when migrating to Parse Server #3380

MateusCarvalho opened this issue Jan 15, 2017 · 1 comment

Comments

@MateusCarvalho
Copy link

MateusCarvalho commented Jan 15, 2017

I recently released the version of my application pointing to my own parse server, however, the old application users who were already logged in (existed session), when they updated by google play, generated a conflict because of the sessions on the servers.

I was able to resolve this conflict by deleting the application's cache data, and logging into the app again. But how do I do this to be done automatically by the application when the user upgrade to version that points to my own parse server?

@flovilmart
Copy link
Contributor

because there is a conflict of sessions

What do you mean by that? Can you please fill the issue template and reopen the issue?

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

No branches or pull requests

2 participants