SCEE 60.0 aborts upload and cannot continue uploading

[mnalis]

How to Reproduce

Don't know. I've just been solving few dozen quests and adding few notes with pictures. When I've got home I've tried uploading (I have autouplaod disabled), it uploaded several of them and then failed with "Connection error while uploading answers. Try again later" when it got to last 9 items to upload.

Retrying upload, changing network, restarting app etc. does not help.

Might be related to notes (perhaps some character in the text of the note the app doesn't like?), because IIRC they are being uploaded last (at last I guess so, because last few items to uploaded always take longer per-item, and I usually have pictures attached to notes)

(I'll try to fetch the log manually later, trying to share it unfortunately crashes the app due to streetcomplete#5561)

Expected Behavior
I expect I'd be able to upload all the remaining items.

Does it happen in normal StreetComplete?

Well, no, but it didn't happen in several previous uploads done via SCEE 60.0, so I suspect it is related to specific data I'm uploading. It is still unknown what need to be done.

Versions affected
SCEE 60.0, Android 14. Never had it happen in previous SCEE versions (nor in StreetComplete 60.0).

[mnalis]

Here is the log from About / Show logs -- unfortunately it seems that intersting portion is being truncated?

Crux seems to be this error:

2025-01-01T23:24:16.316: E [Upload] Unable to upload de.westnordost.streetcomplete.data.ConnectionException: Unexpected JSON token at offset 0: Expected start of the object '{', but had '<' instead at path: $
JSON input: <br />
<b>Warning</b>:  Undefi.....
2025-01-01T23:24:23.265: E [Upload] Unable to upload de.westnordost.streetcomplete.data.ConnectionException: Unexpected JSON token at offset 0: Expected start of the object '{', but had '<' instead at path: $
JSON input: <br />
<b>Warning</b>:  Undefi.....

here is rest of the log:
StringContent-58976510.txt

[Helium314]

What's the edit you're uploading? Maybe something wrong with that?

[mnalis]

Today I've tried uploading and it uploaded just fine:

2025-01-02T12:01:57.803: I [Upload] Starting upload
2025-01-02T12:01:58.603: D [NoteEditsUploader] Uploaded a CREATE to 4572635 at 45.799568178384135, 15.953879203761744
2025-01-02T12:01:59.891: D [NoteEditsUploader] Uploaded a CREATE to 4572636 at 45.7896492019421, 15.96764620632419
2025-01-02T12:02:00.846: D [NoteEditsUploader] Uploaded a CREATE to 4572637 at 45.78879138259185, 15.964046042646089
2025-01-02T12:02:01.893: D [NoteEditsUploader] Uploaded a CREATE to 4572638 at 45.788551320886, 15.962972661353263
2025-01-02T12:02:02.811: D [NoteEditsUploader] Uploaded a CREATE to 4572639 at 45.78702698051583, 15.957882434975716
2025-01-02T12:02:03.710: D [NoteEditsUploader] Uploaded a CREATE to 4572640 at 45.786887647913176, 15.95734382510193
2025-01-02T12:02:04.598: D [NoteEditsUploader] Uploaded a CREATE to 4572641 at 45.78657804240751, 15.956404825549583
2025-01-02T12:02:05.540: D [NoteEditsUploader] Uploaded a CREATE to 4572642 at 45.782426300501925, 15.948452679269678
2025-01-02T12:02:07.376: D [NoteEditsUploader] Uploaded a CREATE to 4572643 at 45.78549082963701, 15.917687649302337
2025-01-02T12:02:07.891: I [Upload] Finished upload

So only Notes were being uploaded (and failing to upload). I guess it might have been some temporary error on @westnordost sc-photo-service yesterday which produced those errors; perhaps there is some server-side logging there which can tell us what was the problem (and how to avoid it in the future):

2025-01-01T23:24:23.265: E [Upload] Unable to upload de.westnordost.streetcomplete.data.ConnectionException: Unexpected JSON token at offset 0: Expected start of the object '{', but had '<' instead at path: $
JSON input: <br />
<b>Warning</b>:  Undefi.....

As for the SC(EE) app side, it might be good idea to log whole errors received from remote server (i.e. split them to multiple lines if they are too long instead of having them end up truncated)?

[mnalis]

As that transient error did not repeat, all that remains actionable is to do better logging (i.e. without truncating).