-
Notifications
You must be signed in to change notification settings - Fork 0
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
NMS Android: Autoruns don't start again after settings are changed #263
Comments
@jbonisteel does it never run again, or does it only start much later? I believe right now, if you change auto-run settings, we set an initial delay of 1 hour before it runs again. So changing the settings might delay an auto-run that would run sooner. That's something we can tweak. But if it never runs again, then that's a bug we haven't seen before. |
@sdsantos as far as I can tell, it never runs again. I tried testing it over yesterday afternoon and this morning and it never seemed to kick on again. |
@aanorbel I've investigate this issue using the Background Task Inspector (https://developer.android.com/studio/inspect/task) and everything looks OK. Any idea what else could be happening here? |
I cant think of any other cause of this error. I also inspected on android and everything looks OK. |
I have been testing this again this afternoon and it does look like auto runs are working more consistently on Android.
So not sure if we changed anything but it seems better now. |
@jbonisteel should we close this for now? |
Yes, we can close |
This is similar to what I see on iOS: #230
If I change the autorun settings (disable 'only while charging'), and then re-enable 'only while charging' + plug phone in - autoruns never seem to start again.
Worth noting - it is possible this is sort of an edge case, I don't know how many people really change those settings that often
The text was updated successfully, but these errors were encountered: