[Data collection] Changes to data on current screen not saved when app is minimized and "next" not yet clicked

[gino-m]

Please also check text and other types.

[anandwana001]

Supporting Video to this Issue

Screen.Recording.2024-08-22.at.11.56.01.AM.mov

[anandwana001]

So the correct bug we are seeing here is after resuming the application, the location/pointer moves back to the default place, not the place where we last left it.

Screen.Recording.2024-08-22.at.12.04.30.PM.mov

[anandwana001]

Screen.Recording.2024-08-23.at.8.56.33.PM.mov

Without Completing Polygon

[anandwana001]

@gino-m Tested all types of collection, and all are working fine. Check the attached video. I think we can close this issue.
I think I found is with the other option text area, I will check and file other issue if anything required.

Screen.Recording.2024-08-23.at.9.36.37.PM.mov

[anandwana001]

@shobhitagarwal1612 can we close this?

[shobhitagarwal1612]

Discussed offline, the issue is when we kill the app and reopen it.

[anandwana001]

should we close this and create a separate issue for app kill?

[shobhitagarwal1612]

@gino-m Are you still able to reproduce the issue?

[gino-m]

Based on @anandwana001 's video I think we can close this one. What is the issue # of the "app kill" case? We should be sure to enumerate the remaining "draft" states to be saved in the issue.

[anandwana001]

Based on @anandwana001 's video I think we can close this one. What is the issue # of the "app kill" case? We should be sure to enumerate the remaining "draft" states to be saved in the issue.

raised PR for kill case, which includes partial load, so kill case and partial load for all type of task will get done in one PR.
#2720

[anandwana001]

Based on @anandwana001 's video I think we can close this one. What is the issue # of the "app kill" case? We should be sure to enumerate the remaining "draft" states to be saved in the issue.

Closing this issue.