Token is not clearing in Android emulator after app uninstall

[skyshine999]

I integrated this plugin it is working fine in ios and android.In android I am able to run and done successful login. After that i uninstalled the app from emulator and try to run again and clicking on login it is going to silent login.i kept backup= false in android manifest still it is storing token in async storage.

[vmurin]

You are right - currently there is no such feature like "clear all cached data"

I will think about possible implementation but it can not be called on uninstall automatically. It is rather the OS task...

[skyshine999]

Are you storing token in async storage or somewhere. If you are storing in async storage it will be cleared after uninstall.

[vmurin]

In have today published new version with the new method clearPersistentCache (link)
You can use it on your own. And on uninstall cached in AsyncStorage data will be cleared as well (as you wrote)

So I close this issue.

[skyshine999]

i have taken your latest plugin after that i logged in and uninstalled the app. Again i installed the app i am able to see previous user login details.
Everywhere if we uninstall app it will delete all login details. Have you implemented same feature here

[vmurin]

Where and how you can see the user login details? Which details you see?

[skyshine999]

I am able to see emailid and it is showing message like "Are you trying to sign in myapp?". If i press yes it is doing silent login without my password.

[vmurin]

Just want additionally comment this issue to clear the behavior.

The library uses system browser (different components on iOS and Android but with similar behavior) to login into Azure. There is a number of reasons to do so. A good explanation you can find for example here.

If you uninstall your app it does affect of course the system browser component. And if you reinstall the app und login shortly after that, the browser component uses saved cookies to re-login into Azure.
There is no security breach, this is intended behavior as long as the tokens saved in cookie are valid. The cookie tokens are short-lived, usually not longer as 1 hour. After this period of time the user will be re-prompted to enter his password.