Reinitialise repo on main activity (re)creation - #202
Merged
Conversation
Owner
|
Are you closing the app somewhere in your steps ? Is there a difference in GrapheneOS that you're aware? |
Contributor
Author
Ah, not explicitly, but I do have "allow background usage" disabled. Could you test with that? I think issue can still happen without this (as well as stock Android), just less frequently. |
Owner
|
So Thanks for the fix |
wiiznokes
force-pushed
the
fix/repo-not-init-remember
branch
from
July 29, 2026 16:41
2f5f504 to
3e2c530
Compare
wiiznokes
enabled auto-merge (rebase)
July 29, 2026 16:41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This ensures the repo is properly opened if the main activity is killed/re-opened.
Tested via:
With this and the same steps, after the process is recreated,
tryInitruns and I can't repro.Closes #196, closes #197.