DevExpress / testcafe-hammerhead

A powerful web-proxy used as a core for the TestCafe testing framework. :hammer: :smiley:
https://testcafe.io
MIT License
171 stars 161 forks source link

Apple pay failure when using hammerhead as a proxy #2987

Closed sparsh00 closed 8 months ago

sparsh00 commented 9 months ago

What is your Scenario?

I'm using Hammerhead as a stand-alone proxy for running a session on iOS.using

What is the Current behavior?

The Apple pay sheet is getting auto-closed after throwing an error.

What is the Expected behavior?

Should be able to complete payment

What is your public website URL? (or attach your complete example)

https://applepaydemo.apple.com/

What is your TestCafe test code?

Running session drictly by using hammerhead as a proxy

Your complete configuration file

No response

Your complete test report

No response

Screenshots

Expected - Screenshot 2023-12-12 at 8 50 24 PM

Error - Screenshot 2023-12-12 at 8 48 04 PM Screenshot 2023-12-12 at 8 50 51 PM

Steps to Reproduce

  1. Setup your device / machine to make Apple Pay Payments . Refer: https://support.apple.com/en-in/HT204506 ( You need to login to iCloud, ( You can use sandbox too ) and Add Card to Wallet ( Personal cards are not required, Sandbox cards also works if you have logged in with Sandbox account )
  2. Start testcafe hammer-head proxy ( node node_modules/gulp/bin/gulp https-playground )
  3. Open http://localhost:1400/
  4. Enter Apple Pay demo website - https://applepaydemo.apple.com/ in the URL
  5. Click on Apple Pay button.

TestCafe version

null

Node.js version

16.20.2

Command-line arguments

node node_modules/gulp/bin/gulp https-playground

Browser name(s) and version(s)

No response

Platform(s) and version(s)

No response

Other

No response

aleks-pro commented 8 months ago

Hello,

We do not recommend that you use testcafe-hammerhead as a stand-alone package and do not support such usage scenarios. Could you describe in greater details why you need to use testcafe-hammerhead without testcafe?

github-actions[bot] commented 8 months ago

This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don't have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone.