Hass.io store not working

Cannot get to addon depository

Used Windows 10 to download Hassio for rpi 3.
used etcher to burn sandisk 16 gig class 10
installed sd card in rpi3 connected ethernet cable and power
waited 1 hour
using firefox went to hassio.local:8123
homeassistant loaded perfectly
clicked hamburger icon and got the menu
overview works
map works
logbook works
history works
configuration works
hass.io clears the screen but nothing more
the address bar shows the not locked pic and then hassio.local:8123/hassio
i have tried firefox browser and microsoft edge browser and my ipad with no luck

?? what am I missing??? cannot edit yaml file cannot access the store??

any help would be appreciated !!!1

There is an issue with Firefox with v 0.70.0 Try chrome…

Thanks David, I installed chrome and now my hassio on RPI works !!! Thanks so much for taking the time to help out a newbee. Hope I can return the favor some day…

I’m not complaining, any help is good but why does every response I see to this problem always repeat the fact that this is a known problem with Firefox?

It is a known problem with other browsers too (Edge for sure) and I am pretty certain I have seen someone on here saying it still didn’t work when changing to Chrome. And, it was a problem for me since a good few releases before 0.70.0.

I’m sorry for appearing to rant on this (I’m definitely not) but it seems to me that this is a pretty big issue (front end not working properly) for HA.

I am sorry my answer was not precise enough for you. Pretty much EVERY browser other than chrome (at the moment) has this bug.

This has been a long standing bug with many browsers and in attempting to fix it it’s broken. It will be fixed in the next release I think… certainly they want to fix it.

Sorry David, as I tried (and maybe failed) to emphasise, it wasn’t a swipe at you or your response - you are one of those on here that always seems happy to try to help.

I am just surprised that this issue isn’t more visible (as an issue). I for one had no idea that it had been recognised as a long standing problem in any other browser than Firefox since 0.70.0 and neither was I aware of the ‘attempting-to-fix-it’ history.

My point was more about the apparent lack of any real statement about what is in fairness a fairly major issue (in that it potentially affects everyone using HA).

Now I know the history I am more than happy, I was just afraid it was being somewhat brushed under the carpet.

It was in the release notes which it seems a lot of people don’t read (for v0.70). I pick up some stuff in the Discord chat - 0.70 was a whole new frontend from what I gather.

I do read the release notes (maybe not all of it gets absorbed!) but I was sure it has only ever mentioned Firefox and as I said I experienced it with Edge a long time before 0.70.0.

Anyway… no big deal. Maybe I should hang around Discord a bit…

OK so this is now fixed in 0.71.0