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

Magento ver. 2.3.0 - Perpetually loading screen for #PAYMENT #38577

Closed
1 of 5 tasks
abubuioc opened this issue Apr 3, 2024 · 33 comments
Closed
1 of 5 tasks

Magento ver. 2.3.0 - Perpetually loading screen for #PAYMENT #38577

abubuioc opened this issue Apr 3, 2024 · 33 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.3.0 Indicates original Magento version for the Issue report.

Comments

@abubuioc
Copy link

abubuioc commented Apr 3, 2024

Preconditions and environment

  • Magento version: Magento ver. 2.3.0

  • The end user adds an item to the cart, and clicks for payment. The "Payment" page (payment method) loads perpetually without any pop-ups or error messages.
    loading screen

  • The browser in use is Google Chrome Version 123.0.6312.106

Steps to reproduce

To reproduce...

  1. Access our page's link for vendor registration (product example)
  2. Link https://www.cronsrud.com/store/vendor-registration-2024.html
  3. Select 1 unit, add to cart.
  4. A pop up screen shows, select go to cart.
  5. To the right side of the screen, select proceed to checkout.
  6. Bug Appears! Loading screen... will not pass this point.
    Screenshot 2024-04-03 at 10 04 36 AM

Expected result

Order is completed successfully and we are past the loading screen and off to submit payment method and complete order.

Actual result

Loading screen, will not allow the end user to enter payment information.

Additional information

No response

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Copy link

m2-assistant bot commented Apr 3, 2024

Hi @abubuioc. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

Copy link

m2-assistant bot commented Apr 3, 2024

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Bravo engcom-Bravo added the Reported on 2.3.0 Indicates original Magento version for the Issue report. label Apr 3, 2024
@abubuioc
Copy link
Author

abubuioc commented Apr 3, 2024

Area: PAYMENTS
Reproduced on 2.3.0

@abubuioc
Copy link
Author

abubuioc commented Apr 3, 2024

Issue: Confirmed

@abubuioc
Copy link
Author

abubuioc commented Apr 3, 2024

Hi @engcom-Bravo - Could you advise if there is additional information needed for this open issue?

@abubuioc
Copy link
Author

abubuioc commented Apr 3, 2024

Issue: Confirmed

Copy link

m2-assistant bot commented Apr 3, 2024

Hi @engcom-Dash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

    1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
    1. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
    1. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
    1. Verify that the issue is reproducible on 2.4-develop branch
      Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
      - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
      - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

@abubuioc
Copy link
Author

abubuioc commented Apr 3, 2024

Area: PAYMENT

@abubuioc
Copy link
Author

abubuioc commented Apr 3, 2024

Hi Team - can we have an update please..

@devchris79
Copy link

Have you looked in the Chrome console to see if any errors are displayed?

@devchris79
Copy link

devchris79 commented Apr 3, 2024

Tried your page and it works for me....

junk

It may be that your browser simply needs its cache cleaning.

@abubuioc
Copy link
Author

abubuioc commented Apr 3, 2024

I have cleaned the cache, cookies, history... This screenshot was just now..
Screenshot 2024-04-03 at 12 58 03 PM

@abubuioc
Copy link
Author

abubuioc commented Apr 3, 2024

Hello - looking for an update...

@engcom-Dash
Copy link
Contributor

Hi @abubuioc

Thanks for reporting and collaboration.

Verified the issue by following the below mentioned steps to reproduce :

1.Access our page's link for vendor registration (product example)
Link https://www.cronsrud.com/store/vendor-registration-2024.html
2.Select 1 unit, add to cart.
3.A pop up screen shows, select go to cart.
4.To the right side of the screen, select proceed to checkout.
5.Bug Appears! Loading screen... will not pass this point.

But we are able to fill the payment details. The page is working fine for us.

Please refer the below screenshots. Let us know if we have missed anything.

Screenshot 2024-04-03 at 9 02 47 PM

@engcom-Dash engcom-Dash added the Issue: needs update Additional information is require, waiting for response label Apr 4, 2024
@abubuioc
Copy link
Author

abubuioc commented Apr 4, 2024

Hello @engcom-Dash ! Thank you for your message...

But by following the same steps... this happens on our end... there is a bug that is not letting that page pass.

Screenshot of just now attached.
Screenshot 2024-04-04 at 8 42 38 AM

@abubuioc
Copy link
Author

abubuioc commented Apr 4, 2024

Hello - checking in ...

@abubuioc
Copy link
Author

abubuioc commented Apr 4, 2024

Hello,

Please note we continue to have this issue. Do you need to remote log in?

@abubuioc
Copy link
Author

abubuioc commented Apr 5, 2024

Good morning... looking for an update.

@abubuioc
Copy link
Author

abubuioc commented Apr 5, 2024

issue: needs update

@abubuioc
Copy link
Author

abubuioc commented Apr 5, 2024

Issue: needs update

@engcom-Dash
Copy link
Contributor

Hi @abubuioc

We are not able to access the link provided

https://www.cronsrud.com/store/vendor-registration-2024.html

We are seeing the below error.

"There has been an error processing your request
Exception printing is disabled by default for security reasons.

Error log record number: 1556876686153"

Please refer the attached screenshot.

Screenshot 2024-04-10 at 1 24 04 PM

@abubuioc
Copy link
Author

abubuioc commented Apr 10, 2024 via email

@engcom-Dash
Copy link
Contributor

Hi @abubuioc

While trying to signin in the link you have provided we are getting the below error. "Error log record number: 924887178473"

https://www.cronsrud.com/store/vendor-registration-2024.html

Please refer the attached screenrecording.

Screen.Recording.2024-04-10.at.6.30.30.PM.mov

@abubuioc
Copy link
Author

abubuioc commented Apr 10, 2024 via email

@abubuioc
Copy link
Author

abubuioc commented Apr 11, 2024 via email

@digitalrisedorset
Copy link
Contributor

Evening, I am looking at reproducing the issue at my end. I have just created a new account and I can see the billing address form and the payment for too.

I suspect the bugs you mention may happen with customers who are returning customers. Ideally, we could benefit to get some credentials of the customer you use to trigger the bugs? then, using them, we may be able to debug further

@abubuioc
Copy link
Author

abubuioc commented Apr 11, 2024 via email

@abubuioc
Copy link
Author

abubuioc commented Apr 11, 2024 via email

@digitalrisedorset
Copy link
Contributor

digitalrisedorset commented Apr 11, 2024 via email

@abubuioc
Copy link
Author

abubuioc commented Apr 11, 2024 via email

@digitalrisedorset
Copy link
Contributor

digitalrisedorset commented Apr 12, 2024

Hi, thanks for coming back to me. This issue has a long trail of messages and I might miss something.

  • I understand the issue you have raised is on a live environment.
  • I understand we are currently trying to replicate your issue so that we can pinpoint the origin for it. In reality, even if we can find out the origin of the issue, it is likely the debugging will be limited since we have a live environment

Currently, my focus is to login as a user that has the issue. That's why I would like to have the credentials you use and I can't find them anywhere: I see a password but I am missing an email.

The way the email appears at the moment is: ***@***.***

@engcom-Dash
Copy link
Contributor

Hi @abubuioc

Thanks for reporting and collaboration.

Verified the issue again on the latest URL provided.

https://www.cronsrud.com/store/vendor-registration-2024.html

We can proceed with the payment.Please refer the attached screenshot.

Screenshot 2024-04-15 at 4 08 00 PM

@engcom-Dash
Copy link
Contributor

Hi @abubuioc

We have noticed that this issue has not been updated for a long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel free to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.3.0 Indicates original Magento version for the Issue report.
Projects
None yet
Development

No branches or pull requests

5 participants