Location pre-alert view for card reader payments

[staskus]

Closes: #14168

Description

Add location permission pre-alert modal before requesting location permission and handle the location denied state during the card reader connection process.

This PR builds on top of the functionality already developed for TTP:

• Location pre-alert view for TTP payments #14660

POS doesn't show any new permission modals. If the location is not determined it immediately shows a native alert and continues with the payment flow regardless of the response. I created a task to implement the functionality:

• [Woo POS] Implement message views for location permission #14671

Steps to reproduce

Prerequisites

• Install a fresh app or go to Settings -> Privacy & Security -> Location Services -> Woo and set to "Ask Next Time Or When I Share"
• Store eligible for IPP
• Card Reader

1. Make an order with product or custom amount
2. Select Card Reader
3. Confirm Location pre-alert appears
4. Tap Continue
5. Confirm native iOS alert appears
6. Not Allow the permission
7. Confirm Location required alert appears
8. Dismiss
9. Confirm the modal closes
10. Select Card Reader again
11. Confirm Location required alert appears
12. Select Open Settings
13. Change Location access to 'While Using the App'
14. Return to the app
15. Confirm the payment flow proceeds

Testing information

Tested on iOS 18 simulators, and iOS 17 devices. Tested POS for regressions. Tested alternative flows during the reader discovery process - selecting a list of multiple readers, or canceling the search.

Videos

Card Reader Connection

iOS.-.Location.mp4

POS regression testing - location allowed

POS.-.Location.Allowed.mp4

POS regression testing - location denied

POS.-.Location.Denied.mp4

---

• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Reviewer (or Author, in the case of optional code reviews):

Please make sure these conditions are met before approving the PR, or request changes if the PR needs improvement:

• The PR is small and has a clear, single focus, or a valid explanation is provided in the description. If needed, please request to split it into smaller PRs.
• Ensure Adequate Unit Test Coverage: The changes are reasonably covered by unit tests or an explanation is provided in the PR description.
• Manual Testing: The author listed all the tests they ran, including smoke tests when needed (e.g., for refactorings). The reviewer confirmed that the PR works as expected on all devices (phone/tablet) and no regressions are added.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce iOS by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce iOS
	Build Number	pr14672-eb3cc2e
	Version	21.2
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	eb3cc2e
	App Center Build	WooCommerce - Prototype Builds #12126

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

[jaclync]

LGTM I'm guessing unit testing CardReaderConnectionController isn't straightforward on the state transitions, originally to .connectToReader?

[staskus]

I'm guessing unit testing CardReaderConnectionController isn't straightforward on the state transitions, originally to .connectToReader?

Thanks! Good point, I'll check how to be safer and cover these changes with unit tests.

Update:

I noticed that these tests are disabled #10536

However, I added additional tests and ran them. When the location is authorized, all the previous tests pass.