fix/refresh-assigned-request-after-release#245
Merged
Conversation
erinc00
requested review from
delibas-rojhat and
kckagancan
and removed request for
kckagancan
April 7, 2026 14:35
Contributor
|
Looks good to me. No conflicts and structure is clear. Approved. |
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
2 participants
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 PR fixes stale assignment behavior on Android after releasing a request.
Summary:
Refreshes Assigned Request state when returning to the screen.
Re-fetches current assignment from backend after “Release Assignment” instead of relying only on immediate response state.
Prevents outdated assignment details from remaining visible after release.