Really annoying that there is no answer or no one working on fixing this.
For anyone who has not done so, you need to contact Amazon to report the issue (posting in this customer to customer forum does not accomplish that).
Forum Moderators (such as the one who replied above) are the only Amazon staff that reads the forum, and they are not directly involved in fixes, and, in most cases, will refer customers to Amazon customer service for feedback or reporting needs. Unless a Forum Moderator has posted and specifically mentions that an issue is a known issue, or specifically mentions they are/will escalate the problem to the tech departments, it shouldn't be assumed that Amazon techs know about it or are working on it.
Amazon can be reached at Help>>Need More Help>>Contact Us.
If a CS rep escalates a ticket, if they say someone will get back to you in X days, if you don't hear from anyone in X+1 days, YOU contact Amazon again. Otherwise, tickets tend to get lost in the shuffle (likely due to how busy they are, not to imply they are sitting around not doing their job).
Since this isn't an "end all", "must have a fix NOW" issue (easily resolved, it seems, by a simple change in browsers), it's not likely to be a priority fix, or one that is likely to be pushed through quickly. Just my opinion, though.
Rollback Post to RevisionRollBack
I'm being extremely clever up here and there's no one standing around looking impressed. What's the point in having you all? - Dr Who
Same problem and just searched for an issue fix to find this page. Interesting thing is the latest photos I could see in the background behind the error message were the photos uploaded on June 24, just a couple days before this first post....so it's like the website itself isn't updating to the new photos that have uploaded from my phone or something?
Same issue I'm having on Chrome as well. It has been happening for months but this time decided to do more of a search to see if anyone else has this issue. Looks like tons of people do.
I also tried logging in with Edge and it works fine there. I don't prefer using that browser and its strange that Chrome would just not work. So please take a look into this Amazon. Seems like an oversight not to fix something like this. I'm sure it affects more than are reporting the problem.