Public Hash Error

[apriddy-16]

Preconditions and environment

• Magento version: 2.4.5-p1
• Anything else that would help a developer reproduce the bug

Steps to reproduce

1. Go to Sales > Orders

2. Click create new order 3. Select an existing client with a saved CC (i.e. AP Anna Priddy) 4. Add a product to the order 5. Select any product to add and configure. 6. Select a stored card 7. Select a shipping rate 8. Click Submit Order 9. The following error is then shown: Order saving error: Public hash should be defined

Expected result

Currently, we have discovered the Public Hash error when customers try to create a new order with a saved credit card, they get this error. Also, we see this error when we try to place an order for an existing customer from the Admin panel. It has to do with the Vault where credit cards are saved.

When the order is placed in the admin and the payment option is selected for a saved CC, we expect the order to process.

Actual result

When the saved payment option is selected, when you hit the 'place order' we expect the order to process.

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”.

[m2-assistant]

Hi @apriddy-16. 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:

• @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.
⚠️ 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.

[m2-assistant]

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).
• 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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[devchris79]

I think this has been reported a couple of times:

#32943
#34424

[apriddy-16]

Thanks for the reference. We saw those and both tickets have 0 resolution with the last comment in July or Octoober 2023.

…

On Fri, Feb 9, 2024 at 5:23 AM devchris79 ***@***.***> wrote: I think this has been reported a couple of times: #32943 <#32943> #34424 <#34424> — Reply to this email directly, view it on GitHub <#38436 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGA3ANJRNYVUFQ7Y5ZDTQ3LYSX2KHAVCNFSM6AAAAABDARMVSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVGY3DSNZVGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Anna Priddy She / Her Account Director Nebo 404-537-1267 ***@***.*** www.neboagency.com <//www.neboagency.com> 680 Murphy Ave #1085, Atlanta, GA 30310 [image: facebook] <https://www.facebook.com/NeboAgency/> [image: twitter] <https://twitter.com/neboagency> [image: linkedin] <https://www.linkedin.com/company/7469/> [image: instagram] <https://www.instagram.com/neboagency/> **I will be OOTO 2/23**

[vipin12117]

Same issue exists in Magento 2.4.6.p3. So looks like this is never checked and fixed.

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Dash, here is your Magento Instance: https://bb496d35baedd3f02017dd5750ad668d.instances-prod.magento-community.engineering
Admin access: https://bb496d35baedd3f02017dd5750ad668d.instances-prod.magento-community.engineering/admin_2777
Login: 6a4ac08c
Password: 8e60e22226a6

[devchris79]

I think this may be fixed in 2.4.6, #33954 seems to be the same with a workaround and Related commits: fd7e45e

[engcom-Dash]

Hi @apriddy-16

Thanks for reporting and collaboration.

Verified the issue in both 2.4.6-p3 and 2.4.7 beta 2.
In 2.4.6-p3 the issue is reproducible. please refer the below screenshot.

But, in 2.4.7-beta2 the issue is not reproducible. please refer the attached screen recording.

Screen.Recording.2024-02-12.at.6.52.20.PM.mov

Seems like the issue is fixed in latest magento.
However, we are trying to test this issue in 2.4 latest dev instance. will update on the results soon.

Thanks.

[engcom-Dash]

Hi @apriddy-16

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

Thanks

[EugenOrosan]

What is the fix for the issue? Is there any patch available?

[vipin12117]

Looks like you are using custom payment method or older magento version. You have to add below line in vault.js

this.$vaultContainer.find('[name="payment[public_hash]"]').val(this.publicHash);