Occasionally, my Android app will forget about the authorization it holds for my Discourse sites and I’ll have to reauthorize it.
Here’s the list of the dates I’ve had to reauthorize it on meta:
Approved: Jul 22
Approved: Sep 9
Approved: Sep 14
Approved: Sep 19
Approved: Sep 26
Approved: Oct 18
Approved: Oct 19
Approved: Nov 9
Approved: Nov 15
Approved: Nov 16
Approved: Nov 24
Approved: Nov 30
Approved: Dec 7
and on another site:
Approved: Sep 14
Approved: Sep 26
Approved: Nov 9
Approved: Nov 18
Approved: Nov 30
Approved: Oct 19
Approved: Nov 15
Approved: Dec 7
Approved: Jul 22
Approved: Sep 19
Approved: Sep 9
Approved: Oct 18
Approved: Nov 24
It seems to happen at the same time for all sites in the list, so I think something is happening on the phone that wipes out the authorization.
Current Chrome version: 63.0.3239.83
Current Android version: 7.0.0; LG-H873 Build/NRD90U
Does it say “connect” in blue when this happens? Or when you click on the site your cookie is gone?
Sounds to me like its saying “connect” there, so somehow storage for the app is blown which is very confusing @joffreyjaffeux we got to get a new version of the app out there to see if it fixes this on android?
Yes, everything reverts back to asking to ‘connect’. When I do connect, I just need to re-authorize the application again, I don’t need to re-login entirely.
Not Falco, but I also use the Android app quite extensively, including the two sites Michael mentioned. I saw this happen a few times in the past, but not recently. The last time I recall this happening was at least 5 months ago.
It just happened again. I noticed I hadn’t gotten any notifications in a while, fired it up, it polled the sites then reverted back to ‘Connect’ after it was rejected.
From the meta logs I see:
a request to message-bus (status=200): https://meta.discourse.org:443/message-bus/_ID_/poll?dlp=t
a request to topic_tracking_state (status=403): https://meta.discourse.org:443/users/supermathie/topic-tracking-state.json
Seems that the app didn’t lose its token, as it thought it had one, but Discourse doesn’t like it for whatever reason.
Is there any way to dump the app’s store so I can see what it thinks it has stored locally?
EDIT: currently I have 1.2.1 which was allegedly pushed on 2017-12-17 - we have a version history? It’s a wild guess but maybe new versions of the app are breaking it?
It was working for me on December 14th 2017, 22:35:31Z. It broke sometime in between then and December 20th 2017, 02:29:41Z.
EDIT again: from the logs the user-agent is: Discourse android App / 1.0 - maybe we should update that with the correct version of the application automatically.
This has been happening to me for quite some time and is still going on. I believe I have been using the latest version of the app most of the time (I definitely am now and it just happened again).