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.

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

Compatibility issue between Google Pay and Distance Rate Shipping #245

Open
thuautp opened this issue Nov 23, 2024 · 0 comments
Open

Compatibility issue between Google Pay and Distance Rate Shipping #245

thuautp opened this issue Nov 23, 2024 · 0 comments
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug.

Comments

@thuautp
Copy link

thuautp commented Nov 23, 2024

8959062-zen

Description of the issue

Google Pay doesn't show shipping rates from the Distance Rate Shipping extension. However, the rates do return on the Checkout page and Apple Pay correctly.

Steps to replicate

  1. Enable digital wallets option
  2. Install and set up Distance Rate Shipping
  3. Create a Distance rate under WooCommerce > Settings > Shipping
  4. Add a product to cart and go to Checkout. Enter a shipping address, observe how the rate is returned on the Checkout page and Apple Pay, but not Google Pay

Screenshots of the issue

Screenshot of a Distance Rate settings:
Image

Screenshot of the rates at Checkout where the distance rates are in the red boxes:
Image

Apple Pay:
Image

Google Pay (only shows the core shipping options):
Image

@thuautp thuautp added the type: bug The issue is a confirmed bug. label Nov 23, 2024
@vikrampm1 vikrampm1 added the priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug.
Projects
None yet
Development

No branches or pull requests

2 participants