PayPal Express not Working from Shopping Cart Page

[nikoelgatito]

Preconditions (*)

1. Magento 2.3.5
2. The Paypal Express Checkout payment method is enabled
3. Paypal Express Checkout config: "Display on Shopping Cart" = Yes (Default)

Steps to reproduce (*)

1. Guest user, initial visit (no localStorage or session)
2. Add any product to cart
3. Visit the shopping cart page
4. Apply a coupon code
5. Click on the Paypal button to start express checkout

Expected result (*)

1. The PayPal Express login popup opens

Actual result (*)

1. The error message "To check out, please sign in with your email address." is displayed.

Temporary Fix

1. Refresh the page and try again.

Similar Issue Already Reported

A very similar issue has already been reported on July 18th 2019 and was never fixed.

Reference to original issue #23761:

Notes:

1. The new steps provided above should allow the issue to be reproduced.
2. A possible fix has been shared by @domeglic; Guest can't use Paypal Express in cart #23761 (comment)
3. This is an important issue resulting in lost sales.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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 @nikoelgatito. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-November. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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-November]

Verified the issue on Magento 2.4-develop branch and the issue is reproducible:
Steps:
Configure PayPal Express Checkout - Advanced Settings - (Stores - Configuration - Sales - Payment Methods - PayPal Express Checkout)
Set Display on Shopping Cart - Yes
Clear Cache and cookies
Navigate to Front end - Guest user - Add a product to Cart
Go to Product Cart page
Apply Coupon
Click on PayPal button
Issue: Warning message: To check out, please sign in with your email address." is displayed.
User have to refresh the page and click on PayPal button again to display PayPal login popup

[magento-engcom-team]

✅ Confirmed by @engcom-November
Thank you for verifying the issue. Based on the provided information internal tickets MC-42855 were created

Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[engcom-Hotel]

PR Merged

[ihor-sviziev]

@engcom-Hotel, could you add more details about what PR you are talking about? Was this issue fixed? Where can we find related changes?
Now I see the only one PR linked to this issue that still not merged yet #33902

[engcom-Hotel]

@ihor-sviziev, the original PR for this issue is this. It has already been merged with the 2.4-develop branch.

Let me check further on how we can find the related changes. I will get back to you on this.

Thanks

[ihor-sviziev]

Ok, now I see - this issue was fixed in the following commits in the 2.4-develop branch:

• d1ca5e5
• 40585f4

BTW, I don't see any test coverage for these changes