oauth2: Tasker Android 13 problem with OAuth2
Bryan B
Hey João,
I have a Tasker project that has been working great on Android 9, 10 and 12 for years. I just bought a Samsung S8 tablet with Android 13, imported the projects and quickly found I could not authenticate with OAuth2 services.
The symptom is that when I manually start the task Tasker opens the browser window so I can login and grant permission and then something goes wrong with Tasker and it doesn't successfully exchange the grant for a refresh_token. In fact the task just stops with no error message and returns to the list of tasks. The same code with the same service and login credentials is working correctly on older Android version.
I did Google the issue and saw references to other Tasker problems with Android 13 thanks to API changes. I enrolled in the Beta program and have Tasker/6.2.5-beta (Android/13) installed. This did not change the behavior.
On the server end, after Tasker gets the auth grant I see Tasker submit headers that are missing the "Authorization:Bearer ..." header so of course the grant is never replaced with a refresh_token.
The task that generates the problem is attached (with privacy edits). A couple of notes:
- The "Flash" alert will display the expected Authorization header on an Android version that is working as expected. On Android 13 the "Flash" is never executed, as mentioned above, and the task just stops with no error message displayed after the first OAuth2 step in the task.
- I am using my own redirect_uri but it is a copy of yours. To be certain, I also verified this fails if I used your default redirect_uri.
Can I provide any additional information to help with debug?
Join