Mitigation: Custom Amounts CTA not being tappable unless keyboard is manually dismissed

[iamgabrielma]

Closes: #13955

Description

We’ve seen some instances where the Custom Amounts CTA button is not tappable unless the keyboard is manually dismissed first, this issue hasn’t been replicable consistently, but we can infer that either the keyboard layout is interfering with the button tap gesture, or the timing of SwiftUI managing the keyboard vs the view dismissal.

We attempt to mitigate this problem by:

• Allowing keyboard dismissal when a merchant taps anywhere else within the view. Adding this within the button closure wouldn’t work, as if the button happens to be non-tappable due to the keyboard layout constraints, we wouldn’t be able to call it’s dismissal either.
• Alleviate potential layout conflicts involving the keyboard within SwiftUI by ignoring the keyboard safe area.

Testing information

As shared in the PR issue, this is cannot be consistently reproduced, but we can run the flow a few times and test the changes:

• On a physical device, start order creation
• Add a few products
• Tap "Add Custom Amount" > Select any option
• Enter details
• Tap the CTA "Add Custom Amount" to save the changes
• Notice that the tap works normally, the keyboard is dismissed, as well as the view
• Observe that when the keyboard is open, you can tap outside to dismiss it, then tap again within the name text field or the number textfield (limited to where the actual placeholder is) in to make the keyboard appear again.

No new Unit Tests have been added, as it's merely an UI update.

Since the keyboard dismissal logic is encapsulated to this view only, we've just added as an extension of the view. We can move this to the view model if you prefer, but I opted to keep it in the view since we don't need to expose it to other views through the view model if the problem hasn't been reported anywhere else.

---

• 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.

[dangermattic]

	1 Warning
⚠️	View files have been modified, but no screenshot or video is included in the pull request. Consider adding some for clarity.

Generated by 🚫 Danger

[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	pr13994-e807202
	Version	20.6
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	e807202
	App Center Build	WooCommerce - Prototype Builds #11049

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

[selanthiraiyan]

The reasoning for dismissing the keyboard upon tapping the view sound good to me. 👍

I tested on an iPhone running iOS 18.0 and didn't face issues with dismissing the keyboard 🚢