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
When testing #4392 I have noticed that the behavior of save using save icon and save on dialog differs. When save on dialog recording is saved but when save using icon and then leave form ignoring further changes recording is not saved. It might be confusing.
Steps to reproduce the problem
Open form with background recording
Click on Save icon in form
Use back button
Ignore changes on displayed dialog
Open files - instance is saved but recording is ignored.
Expected behavior
The recording should not be ignored, it should be saved like after saving on save/ignore changes dialog.
Other information
Things you tried, stack traces, related issues, suggestions on how to fix it...
The text was updated successfully, but these errors were encountered:
Thanks, this is a good one. I doubt it's very common that folks are saving, making changes, and then deciding to discard just those changes but it probably does happen and losing a background recording in that case is definitely unexpected. I think we should consider treating the in-form save as the end of one form-filling session and the start of another so that background audio would be saved and possibly stitched together.
Software and hardware versions
Collect v1.29.x, Android vx.x.x, device used...
Problem description
When testing #4392 I have noticed that the behavior of save using save icon and save on dialog differs. When save on dialog recording is saved but when save using icon and then leave form ignoring further changes recording is not saved. It might be confusing.
Steps to reproduce the problem
Expected behavior
The recording should not be ignored, it should be saved like after saving on save/ignore changes dialog.
Other information
Things you tried, stack traces, related issues, suggestions on how to fix it...
The text was updated successfully, but these errors were encountered: