Closed mnalis closed 3 weeks ago
It looks like the fault is here:
The column already exists in your database. The column is part of a feature implemented in #5474, released in v57.0.
It would be very helpful if we knew from which version you tried to upgrade so that it can be reproduced. There must be something special about upgrading from that version, because otherwise this error would have happened for others upgrading to v57.0, too.
As it was signed by GitHub key (given that upgrade worked), it would indicate I downloaded previous version from GitHub too, which in turn indicates I was doing testing on some previous version (otherwise I'd be installing from F-droid)...
Rummaging through the logcat, I've found this about the time of upgrade/crash:
09-04 22:43:29.399 13717 13717 I Finsky : [1] aryp.h(131): UCtl: Capture account null for next update of de.westnordost.streetcomplete
09-04 22:43:32.322 13717 14013 I Finsky : [883] ahir.run(436): UCtl: For package de.westnordost.streetcomplete, first update discovery timestamp is set to 2022-07-16T12:27:28.051854Z
09-04 22:43:32.375 13717 14013 I Finsky : [883] ahir.run(640): UCtl: Package de.westnordost.streetcomplete client staleness timestamp changed from 2022-07-16T12:27:31.408Z to 2022-07-16T12:27:31.408Z, available version changed from 5501 to 5803 or in-app update priority changed from 0 to 0, Server update discovery timestamp is changed from 2022-07-16T12:27:28.051854Z to 2022-07-16T12:27:28.051854Z
09-04 22:43:32.977 15473 15473 I StreetCompleteApplication: onTrimMemory, level 60: 445 MB of 1850 available, mem low: false, mem low threshold: 216 MB
09-04 22:43:36.117 7141 7224 D PowerKeeper.Event: notifyAMProcDied pacakageName: de.westnordost.streetcomplete, pid:15312
09-04 22:43:37.450 13717 13717 I Finsky : [1] aryp.h(131): UCtl: Capture account null for next update of de.westnordost.streetcomplete
That available version changed from 5501 to 5803
seems like it might be a clue? (And that first update discovery timestamp is set to 2022-07-16T12:27:28.051854Z
might indicate that 5501
was in itself an upgrade from some previous version?)
Could you try if it is reproducible when you download and install 5501, then upgrade to current?
That 5501
turned out to be red herring, but going by the versions/dates of other apps, I've found that after uninstalling, and then freshly installing SC 52.0, starting it up, and upgrading to v59.0-alpha4 leads to that crash.
Thank you for your investigation!
Updated from old SC version (exact old SC version unfortunately unknown, but probably about a year to year and a half old - as Vespucci 19.0.3.0 is installed and was probably current at that time), app crashes on startup, and attempted restarts also crash (instead of offering to send logs)
Crash log:
How to Reproduce
v59.0-alpha4
and upgrade to itExpected Behavior I'd expeect SC to start up normally.
Also, if crashing, it would be nice if offering to send crash log on app startup was done very early; i.e. before database updates, map initialization and other things that are somewhat likely to crash again.
Versions affected StreetComplete
59.0-alpha4
on Android6.0.1
(Xiaomi Redmi Note 3)