-
Notifications
You must be signed in to change notification settings - Fork 145
[WOOMOB-3851] Request the Android 17 local network permission for POS phone-as-reader #16418
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
Open
kidinov
wants to merge
7
commits into
issue/increment-target-sdk-37
Choose a base branch
from
issue/WOOMOB-3851-local-network-permission
base: issue/increment-target-sdk-37
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
db57773
Add the Android 17 local network permission and its checks
kidinov 462fd6b
Ask for local network permission before the phone advertises itself
kidinov 2a2e2b6
Ask for local network permission before connecting to a phone reader
kidinov 917bbe3
Add release note for the Android 17 local network permission
kidinov 3e24f78
Recheck reader mode permissions on resume so granting in Settings con…
kidinov 680fa9a
Keep the local network permission constant behind WooPermissionUtils
kidinov 78c069a
Merge branch 'increment-target-sdk-37' into issue/WOOMOB-3851-local-n…
kidinov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AI Code Review [follow-up]
Issue: When local-network permission is granted (here and in
recheckPermissions()on line 214), you reconnect with thephonecaptured in theMissingLocalNetworkPermissionstate. While that state is active,shouldIgnoreDiscoveryUpdates()still letslatestDiscoveredPhonesrefresh, so a phone that re-advertised on a new host/port during the permission prompt leaves the stored address stale. The first connect would then fail and only recover on retry (which does callrefreshAddressOf).Suggestion: Refresh the address before reconnecting, mirroring
onPhoneRetryConnectClicked, e.g.onPhoneConnectClicked(latestDiscoveredPhones.refreshAddressOf(currentState.phone))in both spots.