Alexa Reauthentication Login page shows blank window

Describe the bug After getting notified that Alexa Media Reauthentication Required Reauthenticate on the Integrations page, I go to the integrations page and click ‘configure’. A few days ago, I got a full popup asking for email, password, 2FA code (I have 2FA enabled on Amazon). No captcha appeared. After clicking on submit, a small blank popup appears with only an ‘X’ on the right which closes the popup. All attempts since have given me the blank popup including updating to latest version 3.0 and hard (power off/on) many times. I’ve enabled logging and the html files that appear in the config directory appear to be complete. I’m attaching the log file

To Reproduce Steps to reproduce the behavior:

1. Go to ‘integrations.’
2. Click on ‘configure. for the Alexa integration’
3. blank box appears

1. See error

Expected behavior A popup with text to request email, password, 2fa, captcha if necessary.

Screenshots If applicable, add screenshots to help explain your problem.

System details

• Home-assistant (version):
• Hassio (Yes/No): (Please note you may have to restart hassio 2-3 times to load the latest version of alexapy after an update. This looks like a HA bug). Hassio: Home Assistant Core 0.107.7, Supervisor 245, Operating system Raspbian GNU/Linux 10 (buster) Docker version 19.03.8
• alexa_media (version = “3.0.0”):
• alexapy (version from pip show alexapy or HA startup):
• Amazon 2FA is enabled (y/n). We will not debug login issues if unanswered: YES - I did this a little over 2 weeks ago and it worked fine. When Amazon needed reauthentication 4 days ago, this happened and I no longer have access to alexa devices.

Logs Please provide logs. We’ll be most likely asking for them anyway. home-assistant.log

Additional context Reporter from #941 mentioned: An error message is displayed in the browser after adding the integration.

[alandtse]

No, the issue @denzelm5 has is 2FA is not enabled. It is mandatory. Also this is offtopic so I’ll be marking the comments appropriately.

[Bart56]

.Interesting that I renamed the ‘translations’ dir to something else and edited the en.json file in the .translations dir.

Looking at the image denzelm5 sent, he may be hitting the ‘\n’ issue in the same file. Try editing the en.json file to change ‘\n’ to ‘\n’ in all lines (there are 5 or 6 in there.)