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

[Bug]: Checkout/Payment if refresh window cardId is null #1389

Open
1 task done
bensinca opened this issue Nov 8, 2022 · 5 comments
Open
1 task done

[Bug]: Checkout/Payment if refresh window cardId is null #1389

bensinca opened this issue Nov 8, 2022 · 5 comments
Labels
bug Something isn't working triage-needed Issues that need to be checked

Comments

@bensinca
Copy link
Contributor

bensinca commented Nov 8, 2022

Expected Behavior

On window reload/refresh cartid should still be available.

Actual Behavior

After refresh cart id is null.

vsf-checkout-payment-step.webm

Possible Solution

No response

Steps to reproduce

Add item to cart, go to checkout until payment step.

What version of Magento 2 integration are you using?

1.2.0

What version of Node.js are you using?

16.17.0

What browser (and version) are you using?

Chrome. Safari

What operating system (and version) are you using?

linux

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@bensinca bensinca added bug Something isn't working triage-needed Issues that need to be checked labels Nov 8, 2022
@bartoszherba
Copy link
Collaborator

bartoszherba commented Nov 8, 2022

@bensinca closing. You should not test things on the canary environment, especially on the wrong domain. The demo domain is https://demo-magento2.europe-west1.gcp.vuestorefront.cloud/default

@davidwindell
Copy link

@bartoszherba please do not be so dismissive, this exact same behaviour can be reproduced on https://demo-magento2-dev.europe-west1.gcp.storefrontcloud.io/

@bensinca
Copy link
Contributor Author

bensinca commented Nov 8, 2022

cmon-man.webm

@bartoszherba - you need to update your your docs then. I used what you provided.

Please re-open the issue and I could argue it's quite rude to close an issue like this when it's obviously a bug, it would took you less than a minute to test this and notice the bug.

@bloodf
Copy link
Contributor

bloodf commented Nov 9, 2022

I will reopen the issue because of the evidence shown here.

@bloodf bloodf reopened this Nov 9, 2022
@filrak
Copy link
Contributor

filrak commented Nov 9, 2022

Sorry for the dismissive behavior @bensinca, we will make sure next time the team looks closer at each issue before closing it, and in the meantime @bartoszherba will look into this one.

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage-needed Issues that need to be checked
Projects
None yet
Development

No branches or pull requests

5 participants