"A new version of the frontend is available. RELOAD" button is missing in android app

[mib1185]

Checklist

• I have updated to the latest available Home Assistant version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

after updating to current beta 2024.8.0b0 in the android app i do not get shown the "A new version of the frontend is available. RELOAD" overlay. Even clearing the app cache via system settings did not fix this. Further on the android app the about screen still shows the old frontend version, while on my pc the correct version is shown

android app	pc

unfortunately i'm not such familiar with these deep insides of the frontend, but maybe it is a regrssen of #21177 🤔

Describe the behavior you expected

The "A new version of the frontend is available. RELOAD" overlay is reliable shown on every frontend update

Steps to reproduce the issue

1. HA core 2024.7.4 running
2. android app 2024.7.3-full up and running
3. update to current beta 2024.8.0b0
4. expect to see the "A new version of the frontend is available. RELOAD" overlay, but it did not show up

What version of Home Assistant Core has the issue?

2024.8.0b0

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

android app 2024.7.3-full

Which operating system are you using to run this browser?

android 14

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[bramkragten]

The file name of the service worker changed, but it should still load the new one, it might be that the old one can not be loaded anymore (as it doesnt exist anymore) and that causes an error somewhere. Do you see any errors in your log?

[mib1185]

Do you still need a feedback here? 😀
If yes, which log you're interested in?

[Anto79-ops]

it seems on b1 this is not fixed for me. #21533
Anyone confirm its fixed for them? At least then I can try to troubleshoot more on my end if its fixed for others thanks.

[mib1185]

For me it is also not fixed with 2024.8.0b1 on my android app.

[steverep]

I'll do some research to fix this, but in the meantime...

If the new service worker is not being registered, I'd expect some sort of error in the browser console. I'm not sure how to access that while running the app, but you can try turning on debug logging for the frontend integration. That will send any errors to the core log (as long as they occur after the core connection, which may or may not be the case).

Also, does the problem occur only in the app or in the browser on android too?

[bschatzow]

Browser works fine on my android device. Only the app.

[Anto79-ops]

Sure I'd be happy to get logs for you. Can you please tell me how to turn on logging for the front end? I don't think I've ever done that before.

And yes like others have said it's only the Android app that's giving the issue everything else is fine

[steverep]

Sure I'd be happy to get logs for you. Can you please tell me how to turn on logging for the front end? I don't think I've ever done that before.

logger:
  default: info
  logs:
    homeassistant.components.frontend: debug

[Anto79-ops]

@steverep i added that to the configuration.yaml and restarted, After, I made a change the dashboard on Chrome so that it will force a refresh on the app while I had the dashboard open ( that was at 12:30 pm). Unfortuantly, there is nothing in the log at 12:30 pm or any other time about frontend issues. I'd be happy to send you the entire log, privately as there are some things in the log with names etc.. My discord handle is Anto79-ops.

[steverep]

@Anto79-ops no need to send logs if there is nothing in there from the frontend. You would see an unhandled exception or rejection with a stack trace if there was something to help here.

Let's try something else:

1. Confirm you have the beta installed, and that you are still seeing the old frontend (go to Settings > About and what's the frontend version).
2. Manually refresh. On iOS this can be done just by trying to scroll up past the top of the page, but I'm not sure if that works on android or if there's another way.
   If that works and updates the frontend version, then that tells me that the registration is successful but something is stopping the toast message. If it doesn't work, then android is refusing to register the new service worker for some reason.

Unfortunately I don't have an android device with HA to diagnose this myself, so thanks for bearing with me on the instructions.

[Anto79-ops]

Oh, check this out. It looks like the app is NOT on beta.

But, on PC Chrome, it's on 20240802.0

This looks like the problem. I'm tempted to delete the app and start all over again, but I don't know if that's a good solution if others are going to run into the same issue.

Yeah, I'm not able to refresh the screen manually on Android. Does anybody know how?

[steverep]

Don't delete the app - that's what is expected. Your core version is on beta, but your frontend hasn't updated because a page refresh is needed. The toast message you see on other browsers is doing nothing but telling you to reload the page (and clicking the refresh button does exactly that).

[Anto79-ops]

ok, i just have to figure out how to refresh the app. let me ask in the android channnel and report back....thanks

[steverep]

AFAICT from searching, there's no way to do it unless built-in by the app developer.

If you haven't done so already, can you close the app (not just putting it in the background) and also close all HA tabs in browsers on the same device. Then reopen the app and check the frontend version again.

[Anto79-ops]

Thanks, Steve.

I "Force Stop" the app, cleared the cache, and opened it again, and it's still at the older frontend version.

[steverep]

Okay I think I understand what is happening, and will submit a probable fix shortly. I just don't know enough about android web view to say why it's behaving like that when other browsers do not.

[tsvi]

Might this explain why I can't access any of the add-ons in the android app with the beta installed?

[bschatzow]

Why close before a release of the proposed fix?

[mib1185]

it is automatically closed because of a merged bugfix PR, the next release will contain this fix

[steverep]

Actually I'm going to reopen because only the core change was merged. I ran out of time last night and still need to submit the frontend change.

[Anto79-ops]

Might this explain why I can't access any of the add-ons in the android app with the beta installed?

Yes, that is correct.

[steverep]

I submitted a change that just needs to be reviewed and merged, but should make it into the next beta. As I said, I don't have an android device setup to fully test, but fairly confident it will solve it. 🤞🏻

[bschatzow]

@steverep If you want me to test something prior, let me know where I can download the change (s) and I will test it. Thanks as always to the team for the quick action to resolve issues.

[steverep]

@steverep If you want me to test something prior, let me know where I can download the change (s) and I will test it. Thanks as always to the team for the quick action to resolve issues.

I'd expect the next beta tomorrow so that's not worth the trouble to set up. Thanks for the offer though.

[tsvi]

Still not working with 2024.8.0b2.
I tried clearing the cace from the all. Nothing. I still get the old UI. I see this because I can't see the ffmpeg integration from YAML. Only when accessing via the browser.

[mib1185]

can confirm, it is unfortunately still not providing the update/reload button

[mib1185]

now i see that the new frontend 20240805.0 did not get it into 2024.8.0b2, therefor the fix is just not released yet. We need to wait for home-assistant/core#123194 gets merged and 2024.8.0b3 released

[bschatzow]

Not sure why an untested fix is automatically closed prior to any testing? Doesn't make sense to me.

[bramkragten]

If a fix has been merged the issue is closed, as we assume the issue was fixed by the fix. If it is not fixed the issue can be reopened or you can open a new issue. Otherwise issues will never get closed, because people often will not close them to report it was fixed, but will report it wasnt fixed.

[steverep]

Not sure why an untested fix is automatically closed prior to any testing? Doesn't make sense to me.

The change was tested, just not on the android app, and there is high confidence it solves the problem as it just becomes like any other update in the past. It can also be reopened at the click of a button.

[bdraco]

We use GitHub for tracking development, and it does not operate like a traditional ticket system/support desk. Issues are closed when the PR merges. Support is done via the community forums and discord.

[bschatzow]

Thanks for the clarification. I understand that a new issue can be opened, I don't realize any user could open a closed issue ? I was never able to do this and many times useful information is lost when opening a new issue for the same issue. Anyway we should know shortly if it is fixed

[Anto79-ops]

Thanks @steverep and frontend team. All is working for me in b3 now. Cheers!

[bschatzow]

All good for me as well.