Open thirtythreeforty opened 6 years ago
I can fix this by calling Binder#clearCallingIdentity
at the start of my authenticator method implementation. I'm of the opinion that Chuck should do this because it is an implementation detail that Chuck uses a ContentProvider
.
I get the following SecurityException when using Chuck from a custom authenticator implementation:
If I had to guess, the authenticator is running with the permissions of the AccountManager (uid=1000 strikes me as the user's account, not the app's).
Obviously, this breaks the HTTP calls; the request is never made.