[Bug; Android]: Changes not saved #12

Closed
opened 2026-05-31 07:21:38 +02:00 by PhoenixPhantom · 0 comments

Due to how android works, it is currently possible for the user to race the saving process when the app is exited. Closing the app before the save's completion results in the changes being dropped as the app is then force-closed.

Waiting 1-5 seconds before closing the app from the recent apps screen ensures data is saved. (this should obviously not be neccessary)

This problem does not exist for jvm desktop (Windows, Linux, MacOS) targets since these platforms allow processes to complete arbitrary amounts of work when they are closed by the user.

Due to how android works, it is currently possible for the user to race the saving process when the app is exited. Closing the app before the save's completion results in the changes being dropped as the app is then force-closed. Waiting 1-5 seconds before closing the app from the recent apps screen ensures data is saved. (this should obviously not be neccessary) This problem does not exist for jvm desktop (Windows, Linux, MacOS) targets since these platforms allow processes to complete arbitrary amounts of work when they are closed by the user.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
PhoenixPhantom/Spellbook#12
No description provided.