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

Card not visible on Fire (Fully Kiosk) #144

Closed
silversmarty opened this issue Sep 11, 2022 · 18 comments
Closed

Card not visible on Fire (Fully Kiosk) #144

silversmarty opened this issue Sep 11, 2022 · 18 comments
Labels
bug Something isn't working

Comments

@silversmarty
Copy link

Checklist:

  • [V ] I updated to the latest version available
  • [ V] I cleared the cache of my browser

Release with the issue:
4.3.1

Last working release (if known):
unknown

Browser and Operating System:
Fully Kiosk on Amazon Fire

Description of problem:

The card is not visible on Fully Kiosk Browser

Additional information:

THe card is visible on my laptop without any problem

@silversmarty silversmarty added the bug Something isn't working label Sep 11, 2022
@decompil3d
Copy link
Owner

Interesting -- is there any way for you to see if there are any script errors in Fully Kiosk?

@silversmarty
Copy link
Author

silversmarty commented Sep 12, 2022 via email

@decompil3d
Copy link
Owner

Can you try some of the ideas suggested in the second FAQ item here: https://www.fully-kiosk.com/en/#faqs

Does the card work on Chrome and/or the basic Android browser on the same device?

If it's just in Fully Kiosk, are you able to try the Chrome remote debugger to see if it is throwing some sort of error in the console?

@silversmarty
Copy link
Author

No problem with Chrome on the same device.

I must admit I don't know how to debug Webview, it seems there is a line of code to be embedded in the app (FullyKiosk ?) itself.
From what I can see in the tablet "developpers settings", it's using Amazon System Webview (it's an Amazon Fire tablet).

Hope it helps

@decompil3d
Copy link
Owner

That's all helpful info. Can you try checking the Amazon Silk browser on that device too? Just trying to eliminate possibilities.

@silversmarty
Copy link
Author

It's a Fire on which I've installed Android, so no Silk available (nor on the Play Store) :-(

@decompil3d
Copy link
Owner

Ah, so it's normal Android webview, not Amazon. Do you know what version of Android it is?

@silversmarty
Copy link
Author

70.amazon-webview-v70-3538.3538110.137

@silversmarty
Copy link
Author

Hello, any update on this bug ?
Thanks a lot !

@decompil3d
Copy link
Owner

Sorry -- I haven't had time to look into this more. I've been taking care of a new baby so my computer time is pretty limited right now. I'll likely have more time in October and November. Apologies for the delay.

@silversmarty
Copy link
Author

Having 3 kids myself, I know what you're going through ;-) Take your time, and enjoy the moment!

@decompil3d
Copy link
Owner

Yup, this is number 3 for me as well. They definitely grow up fast. Thanks for your patience on this.

@rkoehler2017
Copy link

here are 3x Fire 7 Tablets with Fully Browser (for fire tablet) wich are working with this addon a 2 or three month
(only today the problem with a unknow Icon on Cloudy Snowy condition)

@decompil3d
Copy link
Owner

(only today the problem with a unknow Icon on Cloudy Snowy condition)

Which weather integration are you using?

@rkoehler2017
Copy link

type: custom:hourly-weather
today it is working, the state is cloudy, yesterday the state was unknown or so, unfortunately no screenshot made

@decompil3d
Copy link
Owner

type: custom:hourly-weather

today it is working, the state is cloudy, yesterday the state was unknown or so, unfortunately no screenshot made

I mean the weather entity you're using. Which provider is it? I haven't seen cloudy-snowy before so wondering if I need to add support.

@rkoehler2017
Copy link

Deutscher Wetterdienst
and it was Cloudy Snowy outside, the state was unknown from hourly-weather integration
here
image

@decompil3d
Copy link
Owner

Gotcha -- sounds like the integration provided bad data. Thanks for the info.

Regarding the original issue reported in this ticket, it sounds like it may not repro for other users with similar setups. As such, I'm going to close this.

@decompil3d decompil3d closed this as not planned Won't fix, can't repro, duplicate, stale Dec 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants