android beta: crashing on sync + open (fixed in 1.0.0-222)

edited yesterday at 7:07pm
android log: https://bin.disroot.org/?8a355d72c0a5c93f#HKg4cBASYXUVAw23bYbQLQAMhyRZSiJLCvq2oQCLn34r

Zotero report ID: 1582918730

Currently cannot use Zotero as it crashes as soon as it is opened.
  • Interestingly this crash is not happening on a second android device running a16.

    Is there anything I can do to get back to working state? Currently zotero crashes on very open and the crash is persisting after a device restart.
  • persisting after updating to 1.0.0-221. Should this be filed on GitHub?

    Report ID: 1272086403

    log:
    java.lang.NullPointerException
    at org.zotero.android.screens.allitems.data.ItemCellModel$Companion.init(ItemCellModel.kt:28)
    at org.zotero.android.screens.allitems.processor.AllItemsProcessor.generateCellModels(AllItemsProcessor.kt:393)
    at org.zotero.android.screens.allitems.processor.AllItemsProcessor.access$generateCellModels(AllItemsProcessor.kt:55)
    at org.zotero.android.screens.allitems.processor.AllItemsProcessor$processUpdate$1.invokeSuspend(AllItemsProcessor.kt:575)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
    at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
    at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:124)
    at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
    at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:820)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)
    Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@16ba874, Dispatchers.IO]
  • In version 1.0.0-222 an attempt was made to fix this issue.
    Please tell us it fixes it. If not, then before we try investigating it further, since this issue only seems to appear on just one of your devices and not for any other user (according to crashlogs), i think just reinstalling the app on that device, should fix it. Especially since it seems to work fine on your other device as you mention.
  • edited yesterday at 7:32pm
    I was considering re-installing, but to ensure I was able to provide debug data when requested I keep installation untouched. Happy to report though, that 1.0.0-222 no longer crashes on open.

    Thanks so much for investigating DimaP.
Sign In or Register to comment.