You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These are the crash issues I see on acrarium when I click "reports" and filter by version "2.19.1"
Note that some may be slightly duplicated, note that some may be carried over from older versions, but all seem like they could be addressed.
Anyone could work on any of these, and/or add more information here, and/or create sub-issues for each one.
Note that you will likely want to fetch the mapping file from the releases page that matches the build type in the given report, then use the retrace Android command line tool to symbolicate / deobfuscate the code
In the absence of anyone else doing something better, my plan is to use this as a task list with these steps:
follow each link and get a count of similar ones in order to rank by priority and group similar ones via indentation here
add a brief title to each one
create a sub-issue for each one as I work on it, with retraced stack trace in the sub-issue
make a PR in as pragmatic a way as possible to stop the crash, see that merged and cherry-pick it for 2.19.2
For documentation, the retrace command used was aliased in shell to this:
pbpaste | "${ANDROID_SDK_ROOT}/cmdline-tools/latest/bin/retrace" "/Users/${USER}/Downloads/AnkiDroid_current_proguard/build/outputs/mapping/playRelease/mapping.txt" | sed "1d" | pbcopy
(note: I/Mike edited the command slightly to work for current logged in user and "current" mappings now so that the command is stable enough to leave as a persistent shell alias for permanent use :-) )
These are the crash issues I see on acrarium when I click "reports" and filter by version "2.19.1"
Note that some may be slightly duplicated, note that some may be carried over from older versions, but all seem like they could be addressed.
Anyone could work on any of these, and/or add more information here, and/or create sub-issues for each one.
Note that you will likely want to fetch the mapping file from the releases page that matches the build type in the given report, then use the
retrace
Android command line tool to symbolicate / deobfuscate the codeIn the absence of anyone else doing something better, my plan is to use this as a task list with these steps:
add a brief title to each onecreate a sub-issue for each one as I work on it, withretrace
d stack trace in the sub-issueResult::unwrap()
on anErr
value: PoisonError { .. } #17382...
is not valid; is your activity running? #17389PermissionsUntil29Fragment
: PermissionsActivity cannot be cast tocom.ichi2.anki.DeckPicker
#17372/storage/emulated/0/AnkiDroid
#17373onQueryTextChange
-NullPointerException
onfilter
#17391Multimedia
MultimediaActivity
:ActivityNotFoundException
: No Activity found to handle Intent { act=android.intent.action.PICK dat=content://media/... } #17376NoteEditor.getCurrentMultimediaEditableNote
: NullPointerException #17380Lower Priority
NullPointerException
#17377BackendDbFileTooOldException
: calledResult::unwrap()
on anErr
value: PoisonError { .. } #17375Not new, but no issue existed
Existing
Not Adding an issue
content://media/external/downloads/...
The text was updated successfully, but these errors were encountered: