Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I don't have a complete answer for you, but maybe I can help you a bit on your way.</p> <p>When looking at the <a href="http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/4.1.1_r1/android/accounts/AccountManagerService.java#1032" rel="nofollow noreferrer">getAuthToken</a> implementation you can see that permission is automatically granted if the authenticator is using <a href="http://developer.android.com/reference/android/accounts/AuthenticatorDescription.html#customTokens" rel="nofollow noreferrer">customTokens</a>. The documentation for <a href="http://developer.android.com/reference/android/accounts/AuthenticatorDescription.html" rel="nofollow noreferrer">AuthenticationDescription</a> also mention that the "Authenticator handles its own token caching and permission screen" if custom tokens is used. So if this is the case for you I don't think it's possible to get this screen to appear.</p> <blockquote> <p>I tried to insert a custom check and mimic the GrantPermissionActivity, but the problem is that AuthToken is cached...</p> </blockquote> <p>If you invalidate the the token with <a href="http://developer.android.com/reference/android/accounts/AccountManager.html#invalidateAuthToken%28java.lang.String,%20java.lang.String%29" rel="nofollow noreferrer">invalidateAuthToken</a> it should be cleared from the cache. Just remember to pass the token you want to invalidate to the method (see <a href="https://stackoverflow.com/questions/12523471/accountmanager-invalidateauthtoken-does-not-invalidate-the-token/13579281#13579281">AccountManager: invalidateAuthToken does not invalidate the token</a>).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload