Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collect 1.4.10 won't restart form after interrupted responding #214

Closed
yanokwa opened this issue Oct 24, 2016 · 5 comments
Closed

Collect 1.4.10 won't restart form after interrupted responding #214

yanokwa opened this issue Oct 24, 2016 · 5 comments
Labels
help wanted Issues that are well-specified and don't require too much context. needs information needs reproduction

Comments

@yanokwa
Copy link
Member

yanokwa commented Oct 24, 2016

Sometimes responding to a form is interrupted because of low battery etc. When trying to restart the same form from the Collect menu, "Unsaved changes recovered from savepoint!" flashes briefly and the menu reappears.

This is fixed by manually deleting the instance folder, but this is too much to ask from some less technically savvy users, who are locked out of the form. Is there some shortcut?

I'm using Collect 1.4.10 in Android 5.1.1.

From sebastian.therman@gmail.com

@yanokwa yanokwa added the help wanted Issues that are well-specified and don't require too much context. label Oct 24, 2016
@yanokwa
Copy link
Member Author

yanokwa commented Nov 7, 2016

A good first pass is to set up an emulator image, set the power in that emulator low to trigger the low battery message, and see if this can be reproduced.

@max2me
Copy link
Contributor

max2me commented Nov 10, 2016

@yanokwa I'm unable to reproduce this on my Android device (running Android 6.0). Lollipop emulator on my machine is incredibly slow so it is not much help either :(

I've looked through the code and dont see any obvious reasons for this issue to occur.

In the cases that I was able to encounter this message (by starting to fill out form > killing the app > then starting to fill out new form again), I was able to get out of that screen by pressing Back button several times.

@yanokwa
Copy link
Member Author

yanokwa commented Nov 10, 2016

@max2me I've asked the bug reporter for a stack trace to see if that helps.

If Sebastian responds, it'd also be good to know exactly how to reproduce this. Is the problem at 10%, 5%, 1%? Does the phone turn off? Is it the dialog that pops up that is the problem? Does it seem to be phone specific? Form specific?

If we don't get a response in a week, then we can close this issue and focus instead of #241 which is another take on this problem.

As to the emulator, I find that installing HAXM (this might be Mac only) and using a Nexus 5 with x86_32 image works a lot better.

@max2me
Copy link
Contributor

max2me commented Nov 10, 2016

@yanokwa I have HAXM installed and running but I suspect fairly old CPU I have on dev machine does not have all virtualization capabilities. it's interesting that Android 4.x images run significantly smoother than 5.x when I tried it yesterday. Another unfortunate part is that new emulator that's being shipped with AS 2.0 doesnt support snapshots yet so one has to wait a long time for emulator to boot up.

@yanokwa
Copy link
Member Author

yanokwa commented Nov 23, 2016

We have not received any feedback from OP for about two weeks, so I'm closing this issue.

@yanokwa yanokwa closed this as completed Nov 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Issues that are well-specified and don't require too much context. needs information needs reproduction
Projects
None yet
Development

No branches or pull requests

2 participants