-
Notifications
You must be signed in to change notification settings - Fork 685
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]: Sign-in broken following 13.3.0 #4219
Comments
Hi @justinconabree. Thank you for your report. Join Magento Community Engineering Slack and ask your questions in #github channel. |
For the dropdown, I was able to reproduce it once this morning, but all subsequent attempts now work properly. Maybe a cache issue.. |
I have the same issue. Did you got any fix. |
@adobe export issue to JIRA project PWA as Bug |
✅ Jira issue https://jira.corp.adobe.com/browse/PWA-3230 is successfully created for this GitHub issue. |
Issue confirmed we are working on it |
Unexpected token '<', "<!DOCTYPE "... is not valid JSON |
Details:
The test link: https://venia.magento.com/sign-in IMHO: Critical issue. Fix-Update: would be great Thank you |
Click to "SIGN IN" button issue details:
|
Behavior: click to a link appended to any component:
"/sign-in" page loading console output details:
Issue: affected routes:
Thank you |
v14.1.0 : the issue still exists. Fix: would be great https://venia.magento.com/singn-in Thank you |
Related PR-4351 |
Describe the bug
Login no longer works following 13.3.0. This is also visible on venia.magento.com
To reproduce
Steps to reproduce the behavior:
Open Sign-in dropdown in menu
Enter credentials
Try to sign in
Dropdown will close without doing anything else
Go to /sign-in page
Enter credentials
Try to sign in
Button will be grayed out (error in console)
Expected behavior
Able to login
Screenshots
Please complete the following device information:
Please let us know what packages this bug is in regards to:
venia-concept
venia-ui
pwa-buildpack
peregrine
pwa-devdocs
upward-js
upward-spec
create-pwa
The text was updated successfully, but these errors were encountered: