Open zhartaunik opened 1 year ago
Hi @zhartaunik. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:
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:
@magento give me 2.4-develop instance
- upcoming 2.4.x release
For more details, review the Magento Contributor Assistant documentation.
Add a comment to assign the issue: @magento I am working on this
To learn more about issue processing workflow, refer to the Code Contributions.
Join Magento Community Engineering Slack and ask your questions in #github channel.
:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
:clock10: You can find the schedule on the Magento Community Calendar page.
:telephone_receiver: 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.
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
@magento give me 2.4-develop instance
Hi @zhartaunik. Thank you for your request. I'm working on Magento instance for you.
Hi @zhartaunik, here is your Magento Instance: https://b3c368ddfc2f6397201b87d78638b72e.instances.magento-community.engineering Admin access: https://b3c368ddfc2f6397201b87d78638b72e.instances.magento-community.engineering/admin_b0a6 Login: d02bd5aa Password: b59ba9c956c3
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: :point_down:
Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.Issue: Clear Description
label to the issue by yourself.Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Please help me to understand. There is no Braintree section there. However according to vendor/composer/installed.json
"name": "magento/product-community-edition", "requires": "paypal/module-braintree": "4.4.0", __"required": "paypal/module-braintree-core": "4.4.0",
I assume that it's not complete vanilla Magento version.
Hi @zhartaunik ,
We are able to reproduce the issue in 2.4.5 magento instance and we are getting actual results like endless progress bar loading and JS error is appeared in console.
Screenshots for reference:
Steps to reproduce:
1.Navigate to Stores / Configuration / Sales / Payment methods / Braintree section 2.Fulfill all credentials for it and make Enable Card Payments = NO 3.Navigate to Frontend. 4.Add any product to the cart. 5.Go to Checkout.
We got same error----Like---->JS Error in the console adapter.js:66 Uncaught TypeError: Cannot read properties of undefined (reading 'clientToken')
So we are confirming the issue in 2.4.5 magento instance.
Let us know if we are missing anything
Thanks!!!
Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x
, ^Area:.*
Once all required labels are present, please add Issue: Confirmed
label again.
Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x
, ^Area:.*
Once all required labels are present, please add Issue: Confirmed
label again.
Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x
, ^Area:.*
Once all required labels are present, please add Issue: Confirmed
label again.
@magento give me 2.4-develop instance
Hi @Viktorja1. Thank you for your request. I'm working on Magento instance for you.
Hi @Viktorja1, here is your Magento Instance: https://b3c368ddfc2f6397201b87d78638b72e.instances.magento-community.engineering Admin access: https://b3c368ddfc2f6397201b87d78638b72e.instances.magento-community.engineering/admin_3e95 Login: 9a44f240 Password: 536e109ea2f0
@Viktorja1 I tried to reproduce but this vanilla magento doesn't contain a module braintree. I put the description above that there is a necessary dependency, but by some reason this module is absent.
@zhartaunik Please try to reproduce this issue on 2.4.5 brunch only
@Viktorja1 in my vision magento from this branch differs from those magento which is installing via composer. It doesn't contain a dependency it must.
:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-6417 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @AmyJZhao. Thank you for verifying the issue.
Issue Available: @AmyJZhao, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
It looks like there's an example of how to fix this on the older gene/module-braintree, but the fix is not available in the magento marketplace yet.
5388 4105 3200 7731 09/32 CVV 812
Preconditions and environment
Steps to reproduce
Expected result
Paymen method should be selected and progress-bar should disappear.
Actual result
Endless progress-bar loading
JS Error in the console adapter.js:66 Uncaught TypeError: Cannot read properties of undefined (reading 'clientToken') at Object.getClientToken (adapter.js:66:66)
Additional information
The issue occurs because of not existing part of configuration which name is 'braintree'. window.checkoutConfig.payment.braintree
This config is passing via the following PHP Class: \PayPal\Braintree\Model\Ui\ConfigProvider::getConfig()
Release note
No response
Triage and priority