Skip to content
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

gui remains initializing in kiosk browser #3781

Closed
RonaldHiemstra opened this issue Sep 21, 2019 · 14 comments · Fixed by #3797
Closed

gui remains initializing in kiosk browser #3781

RonaldHiemstra opened this issue Sep 21, 2019 · 14 comments · Fixed by #3797

Comments

@RonaldHiemstra
Copy link

Home Assistant release with the issue:
0.99.0 and 0.99.2

Last working Home Assistant release (if known):
0.98.?

UI (States or Lovelace UI?):
lovelace, but states give the same result

Browser and Operating System:

  • android version: 6.0.1
  • browser: A lightweight browser that relies on the System Webview, for low-end devices, also known as Jelly - comes with LineageOS 13.0
  • kiosk app: wallpanel (which I suppose uses the Jelly browser)
  • Note: google chrome works fine...

Description of problem:

The kiosk app does shows "Initializing" remains in that state
2019-09-21 15 50 47

The default browser only shows the blue navigation bar without any info
2019-09-21 15 53 16

Javascript errors shown in the web inspector (if applicable):
don't know how to get it :(

Additional information:
Similar issue is reported here: https://community.home-assistant.io/t/problem-with-0-99-and-fully-kiosk-fire-tablets

@lukastillmann
Copy link

I have exactly the same issue on a Fire Tablet 7. Don't know how to debug this or find any more information

@iantrich
Copy link
Member

@balloob could this be because we removed babel?

@ccmacaluso
Copy link

This is also happening in fully kiosk when using tablets with the same above reported outdated webviews.

@DeviousPenguin
Copy link

DeviousPenguin commented Sep 21, 2019

I'm not using Fully but I get the exact same behaviour on an old iPad with iOs 9.3.5

I'm unable to login due to it just saying 'Initializing'. If this is unrelated however I can post as a seperate issue. I can get Javascript errors shown in the web inspector if it's relative to this issue.

I used to be able to login OK with older versions in the past.

@bramkragten
Copy link
Member

If someone could get the javascript errors from the console that would be helpful, and if someone could tell what path the js files are loaded from, frontend_es5 or frontend_latest

@DeviousPenguin
Copy link

Hi @bramkragten my files appear to be loading from the frontend_es5 folder on my device, I got a screenshot showing the errors in console, hopefully this helps.

Screenshot 2019-09-20 at 01 00 36

@balloob
Copy link
Member

balloob commented Sep 22, 2019

I just downloaded the latest frontend release from PyPI and it looks indeed that we're not transpiling things down to ES5. That implies that this flag is not working properly:

https://github.com/home-assistant/home-assistant-polymer/blob/9a92ed31f631307bb74b7220a9ba9a7d0a02413e/build-scripts/webpack.js#L49-L53

@ccmacaluso
Copy link

Thanks for looking into this balloob! If any of us with the issue can help you test a dev release let us know.

@balloob
Copy link
Member

balloob commented Sep 23, 2019

Bram and I figured out the cause and Bram is on the case. Will publish a hot fix today/tomorrow when fixed.

@ccmacaluso
Copy link

Thanks!

@bramkragten
Copy link
Member

Should be fixed with 0.99.3

@ccmacaluso
Copy link

Confirmed to be resolved in 0.99.3 for me. Great job guys.

@qiz-li
Copy link

qiz-li commented May 23, 2020

I am on 110.1 and this issue seems to be back?

@balloob
Copy link
Member

balloob commented May 23, 2020

Please open a new issue.

@home-assistant home-assistant locked as resolved and limited conversation to collaborators May 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants