Crash on invalid database import #160

Closed
opened 2023-06-24 10:24:15 +00:00 by jimr · 2 comments

Issue

I exported the database, pulled the sets table out, and edited it as a spreadsheet so I could get some history into the log.

When I imported and scrolled to the new records the app blank screened, and needed exiting to quit. Importing a previous iteration of the database fixed it.

I can go back to replicate it if you need some more details.

Solution

We need some try/catch logic on loading the database. Users will break anything they can get their hands on.

# Issue I exported the database, pulled the `sets` table out, and edited it as a spreadsheet so I could get some history into the log. When I imported and scrolled to the new records the app blank screened, and needed exiting to quit. Importing a previous iteration of the database fixed it. I can go back to replicate it if you need some more details. # Solution We need some try/catch logic on loading the database. Users will break anything they can get their hands on.

Please attach either the adb logs at the time of the crash, and or the database file you are trying to import.

Please attach either the [adb logs](https://developer.android.com/tools/adb) at the time of the crash, and or the database file you are trying to import.
brandon.presley added the
bug
label 2023-06-25 00:25:57 +00:00

Closed due to inactivity

Closed due to inactivity
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: brandon.presley/Massive#160
No description provided.