[Mobile Payments] Built-in reader configuration update alerts

[joshheald]

Part of: #8082

Description

In sTAP Away, we're adding support for Apple's built in card readers to take in-person payments. We continue to use Stripe's SDK to handle payments.

Stripe's connection flow is technically very similar to the bluetooth reader flow, but conceptually, there are differences and it's important that we make it clear to users that they are using the built in reader, and don't give the wrong impression that they are connecting to a bluetooth reader, to avoid confusion.

This PR builds on #8299 by adding a specific alert view model for built-in reader configuration updates. This is very similar to the existing software update view model, so the commonalities are extracted out into a new CardPresentModalProgressDisplaying protocol and implemented in an extension, so the implementation can be shared.

Testing instructions

Using an iPhone (XS or above on iOS 15.4 or newer, with a passcode set and signed in to iCloud)

Update the simulator configuration to the following:

Terminal.shared.simulatorConfiguration.availableReaderUpdate = .required

Enable the simulated card reader in Xcode by using Product > Scheme > Edit Scheme > Run > Arguments tab > Check -simulate-stripe-card-reader

Run the app on device or in a simulator, and select a US store with WCPay.

1. Navigate to Menu > Settings > Experimental features
2. Turn on Tap to Pay on iPhone
3. Navigate to Menu > Payments > Collect payment
4. Go through the payment flow, and select Card on the payment method screen
5. When asked for a reader type, tap Tap to Pay on iPhone and go through the Terms of Service Apple ID linking (if you've not done so before)
6. Observe that specific messages for the built in reader are shown during the connecting process (note that images and text are all placeholders!)

N.B. There are known issues with the payment flow after connection. In particular, #8289, #8288, #8274, and #8085. The payment flow "works", but these issues aren't addressed yet, and some are pre-existing in the legacy flow (just a lot less obvious when you use a bluetooth reader.)

Please do note any issues you find, but give me a shout if you want to check they're known first, just to save writing out detailed repro steps.

Screenshots

configuration.update.alerts.mp4

---

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

[wpmobilebot]

You can test the changes from this Pull Request by:

• Clicking here or scanning the QR code below to access App Center
• Then installing the build number pr8312-0af2f5e on your iPhone

If you need access to App Center, please ask a maintainer to add you.

[koke]

I followed the steps on an iPhone XS running iOS 15.5, but I didn't get the option to use Tap on iPhone. Also the modals had some styling that looked off in the learn more link and cancel button

EDIT: I can't read and missed the part about enabling the experimental feature. Leaving this comment as the modals still look off

Scanning	Connect	Multiple readers

[koke]

I'm now getting the following error using iPhone XS on iOS 15.5 (with a passcode set and signed in to iCloud), are you sure about the minimum requirements?

Unsupported mobile device configuration. Ensure the device is running a supported version of iOS and it has the hardware capability you are attempting to use

EDIT: The public docs mention iOS 16.0 as a requirement

[joshheald]

EDIT: The public docs mention iOS 16.0 as a requirement

Hmm... I thought I took that requirement list from Stripe's docs, but perhaps it changed since then. I'll update some things to reflect iOS 16 and use Stripe's checking method rather than Apple's (which we currently do, so you only see the TTPoI button if Apple say your device supports it.)

Thanks for testing with the (expected) minimum hardware!

[joshheald]

Also the modals had some styling that looked off in the learn more link and cancel button

@koke this is a separate issue that's already merged to trunk. @iamgabrielma is looking at it this week.

[koke]

This is looking good. I left a minor note about the copy and apparently it requires iOS 16.0 now

[koke]

The previous message uses iPhone and this one says phone. While its not wrong, we might want to be consistent there.