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
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).
We found failures similar to the #195 issue in the activity
MainActivity: Top bar text disappears, Topbar text changes, various view properties change, fragment with typeable text disappears, message in top bar appears, pop up menu disappears, screen scroll and activity resets.
Hi, this issue has a relation with #195.
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).
We found failures similar to the #195 issue in the activity
Top bar text disappears.
Top bar text changes
Various view properties change.
LongTouchEvent(duration=2000) [[622,54],[720,138]]
KeyEvent(name=BACK)
IntentEvent(intent='am start com.github.ruleant.getback_gps/com.github.ruleant.getback_gps.MainActivity')
KeyEvent(name=BACK)
IntentEvent(intent='am start com.github.ruleant.getback_gps/com.github.ruleant.getback_gps.MainActivity')
ScrollEvent(direction=FULL_LEFT)
IntentEvent(intent='am start com.github.ruleant.getback_gps/com.github.ruleant.getback_gps.MainActivity')
TouchEvent [[272,54],[522,138]]
TouchEvent [[46,910],[307,1005]]
LongTouchEvent(duration=2000) [[622,54],[720,138]]
TouchEvent [[524,54],[622,138]]
Cap01: capture screen properties before rotation
DoubleRotationEvent
Cap02: capture screen properties after rotation
Cap01 != Cap02 (lost several properties)
Fragment with typeable text disappears.
Message in top bar appears.
The pop-up menu disappears.
Fragment disappears
Note:
The text was updated successfully, but these errors were encountered: