Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Open
staskus opened this issue Dec 12, 2024 · 1 comment
Open

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

staskus opened this issue Dec 12, 2024 · 1 comment
Labels
feature: POS priority: low Not many people are affected or there’s a workaround, etc. type: task An internally driven task.

Comments

@staskus
Copy link
Collaborator

staskus commented Dec 12, 2024 •
edited
Loading

Descriptions

Improvements for IPP flow integrated location permission requests within the TTP and Card Reader process.

Implement message views for POS.

Check PointOfSaleCardPresentPaymentEventPresentationStyle and .locationRequestPreAlert and .locationRequired cases.

  • .locationRequestPreAlert is triggered for .nonDetermined location permision state and explains why location is necessary. According to Apple pre-alert guidelines only has a single "Continue" button that requests the location.
  • .locationRequired is triggered for .denied location permission state. Display similar or the same information explaining why location is necessary to proceed. IPP also shows Open Settings button for convenience. Consider during the same for POS. Calling dismiss() action cancels the payment flow.

IPP Screenshots

.locationRequestPreAlert .locationRequired
Image Image
@staskus staskus added type: task An internally driven task. priority: low Not many people are affected or there’s a workaround, etc. feature: POS labels Dec 12, 2024
@dangermattic
Copy link
Collaborator

dangermattic commented Dec 12, 2024 •
edited
Loading

Thanks for reporting! 👍

@staskus staskus mentioned this issue Dec 12, 2024
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature: POS priority: low Not many people are affected or there’s a workaround, etc. type: task An internally driven task.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@staskus @dangermattic