Uploading stops every few (<20) quests and prompts to re-authenticate against OSM about streetcomplete HOT 12 CLOSED

sc 57.1 is on f-droid since yesterday

from streetcomplete.

Actually that might be some issue with OSM. I remember a few hours ago I wasn't able to open the website, maybe there are still some hiccups.

from streetcomplete.

Do the quest answers get lost btw?

from streetcomplete.

Most likely not, as the upload is not successful

from streetcomplete.

Do the quest answers get lost btw?

Answers should be safe IMHO, but you can make sure by looking at https://www.openstreetmap.org/user/YOURUSERNAME/history yourself (and replacing YOURUSERNAME with your actual username) and see if those previous batches got uploaded successfully.

First I though if that might perhaps be related to rate limits for new users (e.g. https://community.openstreetmap.org/t/the-new-rate-limiting-prevents-participants-to-missing-maps-mapathons-from-saving-buildings/106610) but if you've been actively using the account for more than a month then it is somewhat unlikely...

03-11 21:02:48.030 12660 12670 I .streetcomplete: Background young concurrent copying GC freed 2379073(80MB) AllocSpace objects, 157(5136KB) LOS objects, 56% free, 65MB/149MB, paused 253us,88us total 179.763ms
03-11 21:02:48.030 12660 12670 W .streetcomplete: Reducing the number of considered missed Gc histogram windows from 193 to 100
03-11 21:02:48.155 12660 12660 E chromium: [ERROR:aw_browser_terminator.cc(154)] Renderer process (22498) crash detected (code -1).

I wonder if that garbage collection being triggered just before the error might have something to do with it? I seem to recall some other discussions lately where android could remove and reinstate activities resulting in broken data flow; could something like that be possibly happening here in the middle of the upload?

from streetcomplete.

I am quite sure this must have been a hiccup with the OSM API. See also this forum post from today: https://community.openstreetmap.org/t/forbidden-beim-klick-auf-eine-note/110413

StreetComplete force-logs-out the user when the OSM API responds with HTTP Error code 403 (Forbidden) or 401 (Unauthorized) since it assumes that something is wrong with the user's login. (E.g. you revoked the access token on the website)

Your edits are safe. Edits are only deleted from your device after they have been successfully uploaded.

Can you confirm that this does not happen anymore?

from streetcomplete.

I'm not able to confirm that this does or doesn't happen anymore, I upgraded to 57.0 via F-Droid, which crashes due to #5522. AFAIK, you cannot downgrade Android apps, so I can't go back to 56.1. I also can't upgrade to 57.1 in my understanding because I'd need a 57.1 signed by F-Droid.

This means I'll have to wait until 57.1 is released by F-Droid to test this again.

from streetcomplete.

OK, can't be long till it hits F-Droid

from streetcomplete.

prompts to re-authenticate against OSM

see also https://community.openstreetmap.org/t/what-is-normal-login-cookie-duration/110452/2

I imagine you’re asking this because you got logged out yesterday and the reason that happened is that we were subject to a DOS attack which caused a lot of sessions to be created which in turn caused the session store to overflow and evict older sessions.

from streetcomplete.

I imagine you’re asking this because you got logged out yesterday and the reason that happened is that we were subject to a DOS attack which caused a lot of sessions to be created which in turn caused the session store to overflow and evict older sessions.

Interestingly, I was still logged in in the browser session, so I only had to click "authenticate", not enter my password again

from streetcomplete.

Anyway, will close this as the source of the issue was clear and the behavior of StreetComplete is fine.

from streetcomplete.