Data loss while using the app (differences between view properties)
A data loss problem occurs when data is accidentally deleted or state variables are accidentally assigned with default or initial values. This issue is related to the activity's lifecycle (1). When a screen rotation occurs, the activity is destroyed and resumed. Data loss will happen if the developer does not save the variables before the destruction and restore them after creation. To avoid this, the developers have to implement both the logic necessary to save the activity state in the onSaveInstanceState() callback method and the logic to resume its state in the onRestoreInstanceState() callback method. Another way to avoid data loss problems is to use the view model, designed to store and manage UI-related data in a lifecycle-conscious way (2).
When executing this sequence of actions, there is a loss of data in the activity MainActivity:
- ScrollEvent(direction=UP) [[21,526],[701,1560]]
- TouchEvent [[283,421],[437,505]]
- IntentEvent(intent='am start com.dosse.airpods/com.dosse.airpods.ui.MainActivity')
- TouchEvent [[35,722],[220,757]]
- IntentEvent(intent='am start com.dosse.airpods/com.dosse.airpods.ui.MainActivity')
- Cap01: capture screen properties before rotation
- DoubleRotationEvent
- Cap02: capture screen properties after rotation
- Cap01 != Cap02 (differences between view properties)
Device:
- Device: Moto G30 with OS: Android 11
- Device: MI5X with OS: Android 7.1.2
- Version: 1.7
Note:
- Double screen rotation: It is executed twice to reach a state that should be exactly the same as the screen before if no data loss occurred.
- A data loss problem occurs when data is accidentally deleted or state variables are accidentally assigned with default or initial values.
- https://developer.android.com/guide/components/activities/activity-lifecycle
- https://developer.android.com/topic/libraries/architecture/viewmodel