ADFA-4957: clone RECEIVE return-to-op — reopen lands on the Clone tab - #311
Merged
Conversation
A live clone receive is already app-scoped in SyncProgressRepository (CloneFragment observes it and re-binds to the transfer). On a plain reopen (launcher -> SplashActivity -> LibraryActivity, no explicit EXTRA_TAB) with a receive active, land on the Clone tab so the user returns to the in-progress transfer instead of Home. Only receive: the send daemon state is still Fragment-scoped, so routing a send would show the fork, not the share — full send-session app-scoping + a clone-specific notification are a follow-up.
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
1 participant
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.
A live clone receive is already app-scoped in SyncProgressRepository (CloneFragment observes it and re-binds to the transfer). On a plain reopen (launcher -> SplashActivity -> LibraryActivity, no explicit EXTRA_TAB) with a receive active, land on the Clone tab so the user returns to the in-progress transfer instead of Home. Only receive: the send daemon state is still Fragment-scoped, so routing a send would show the fork, not the share — full send-session app-scoping + a clone-specific notification are a follow-up.