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

Background updates eventually hang #2638

Open
lwis opened this issue Mar 10, 2024 · 32 comments
Open

Background updates eventually hang #2638

lwis opened this issue Mar 10, 2024 · 32 comments
Assignees

Comments

@lwis
Copy link
Member

lwis commented Mar 10, 2024

iOS device model, version and app version

Model Name: iPhone 15 Pro
Software Version: 17.4
App version: 2024.2

Home Assistant Core Version
2024.3.0

Describe the bug
Eventually background sensor updates stop happening, running the "Update sensors" shortcut times out. Force closing the app brings everything back to life and the shortcut starts working again.

To Reproduce
Have iOS app pushing sensor updates in background for a ~period of time.

Expected behavior
App continues to function without repeatedly force closing.

@bgoncal
Copy link
Member

bgoncal commented Mar 11, 2024

When you open the app, does the sensors get updated correctly? I mean, when it is in foreground all works?
Do you have "local push" enabled?

@bgoncal bgoncal self-assigned this Mar 11, 2024
@lwis
Copy link
Member Author

lwis commented Mar 11, 2024

It does not update when the app is in the foreground.

I do not have local push enabled, or an internal URL configured.

@bgoncal
Copy link
Member

bgoncal commented Mar 11, 2024

Did you observe a pattern for when does it stop reporting? In background I know for sure the sensor updates wont be live without local push enabled but foreground should be working properly.

@lwis
Copy link
Member Author

lwis commented Mar 11, 2024

Unfortunately there doesn't seem to be a pattern to it, I have no way to reproduce. Is there anything useful I can capture the next time it happens?

@bgoncal
Copy link
Member

bgoncal commented Mar 11, 2024

Your logs. You can export going in Debugging > export

@bgoncal
Copy link
Member

bgoncal commented Mar 20, 2024

Can you check the latest testflight beta? It may have fixed this

@lwis
Copy link
Member Author

lwis commented Mar 20, 2024

I'll update to the latest beta and continue to monitor! 🤞🏻

@lwis
Copy link
Member Author

lwis commented Mar 20, 2024

Still happening unfortunately, this is what I see when the shortcut fails;

image

@dmulcahey
Copy link

dmulcahey commented Mar 22, 2024

POSIXErrorCode(rawValue: 28): No space left on device) Is thrown constantly by the app when the WS connection breaks

was something changed in the test flight version related to URLsessions or any kind of networking introspection libraries?

@dmulcahey
Copy link

@bgoncal let me know if there is anything you need to assist in debugging this.

@bgoncal
Copy link
Member

bgoncal commented Mar 22, 2024

https://stackoverflow.com/questions/67318867/error-domain-nsposixerrordomain-code-28-no-space-left-on-device-userinfo-kcf

This looks related, I'll investigate next week

@dmulcahey
Copy link

RC still has the issue. I’ll also note that when this happens and you open the app after it has been in the background it doesn’t connect to HA at all. It fails and HA logs the following:

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/http.py:461
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: March 24, 2024 at 6:32:56 PM (6 occurrences)
Last logged: 7:21:09 AM

[281473247231552] from 192.168.1.68 (Home Assistant/2024.3 (io.robbie.HomeAssistant; build:2024.603; iOS 17.4.1)): Disconnected: Did not receive auth message within 10 seconds
[281472302263104] from fe80::1460:ed53:6ed7:34ed (Home Assistant/2024.3 (io.robbie.HomeAssistant; build:2024.603; iOS 17.4.1)): Disconnected: Did not receive auth message within 10 seconds
[281472222859200] from 192.168.1.68 (Home Assistant/2024.3 (io.robbie.HomeAssistant; build:2024.603; iOS 17.4.1)): Disconnected: Did not receive auth message within 10 seconds
[281471861314368] from fe80::1460:ed53:6ed7:34ed (Mozilla/5.0 (iPhone; CPU iPhone OS 17_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Home Assistant/2024.3 (io.robbie.HomeAssistant; build:2024.608; iOS 17.4.1) Mobile/HomeAssistant, like Safari): Disconnected: Did not receive auth message within 10 seconds
[281471753716160] from fe80::1460:ed53:6ed7:34ed (Mozilla/5.0 (iPhone; CPU iPhone OS 17_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Home Assistant/2024.3 (io.robbie.HomeAssistant; build:2024.608; iOS 17.4.1) Mobile/HomeAssistant, like Safari): Disconnected: Did not receive auth message within 10 seconds

hard closing the app and reopening it resolves the issue. I have been running test flight versions since they started getting published again and this just started with this cycle of work: after CarPlay release version so maybe 2 or 3 test flight pushes back.

@dmulcahey
Copy link

I just thought of something else. The timing could possibly coincide with the release of iOS 17.4

@bgoncal
Copy link
Member

bgoncal commented Mar 25, 2024

Can you consistently reproduce the issue in some way? Like rebooting HA with the App open for example. I would like to have the same issue happening on my device to investigate it better, for now I couldn't reproduce

@lwis
Copy link
Member Author

lwis commented Mar 25, 2024

Having a Shortcut automation which fires on power connect and disconnect to "Update Sensors" in the background is the way this manifests most often for me.

@dmulcahey
Copy link

Can you consistently reproduce the issue in some way? Like rebooting HA with the App open for example. I would like to have the same issue happening on my device to investigate it better, for now I couldn't reproduce

Just leaving the app alone in the background for like 30 mins is all it takes for me

@bgoncal
Copy link
Member

bgoncal commented Mar 25, 2024

@dmulcahey Im checking your logs, when they happened were you somewhere http://192.168.1.78:8123 was accessible? (your home probably) or were you using external URL?

@dmulcahey
Copy link

I work from home and am generally here. I just opened the app from the background again. Last open was around the time of my last reply and it happened again. I’ll get new logs for you in a few. Can you give me somewhere to send an iCloud link so I can get you the full bundle from the app?

@bgoncal
Copy link
Member

bgoncal commented Mar 25, 2024

Are you in discord? You can ping me there @bgoncal2

@bgoncal
Copy link
Member

bgoncal commented Mar 26, 2024

Im preparing a testflight build with a possible fix , when you see 2024.612 in testflight you can test it

@dmulcahey
Copy link

Im preparing a testflight build with a possible fix , when you see 2024.612 in testflight you can test it

Just saw this update and installed it. Will report back

@dmulcahey
Copy link

Im preparing a testflight build with a possible fix , when you see 2024.612 in testflight you can test it

Initial testing looks good. Let’s see how it does overnight

@dmulcahey
Copy link

Everything is still working. What was the issue?

@bgoncal
Copy link
Member

bgoncal commented Mar 27, 2024

I'm still investigating but initially I believe the issue is that StarScream lib we use for websocket interaction creates one URLSession per request, which in a retry loop goes over iOS limits. I believe this wasn't happening in some updates ago because we were still supporting iOS 12 at that time and this limit was not applied.
I created a PR to starscream daltoniam/Starscream#1011

@bgoncal
Copy link
Member

bgoncal commented Mar 27, 2024

Heads up that this fix is not on our main branch yet, so if you see new builds coming in testflight, they may revert this fix

@bgoncal
Copy link
Member

bgoncal commented Mar 27, 2024

@lwis can you also check if this works for you?

@lwis
Copy link
Member Author

lwis commented Mar 27, 2024

Updated this morning, so maybe too early to tell, but I've not run into any issues yet.

@bgoncal
Copy link
Member

bgoncal commented Apr 3, 2024

Feel free to reopen this issue if needed, I'm closing this issue for now and planning the next release to include the fix

@bgoncal bgoncal closed this as completed Apr 3, 2024
@lwis
Copy link
Member Author

lwis commented Apr 6, 2024

Bad news; it happened again this morning. I'm unable to run the shortcut directly at all. The app is fully functional. Closing the app allows the shortcut to run again.

I grabbed logs before closing the app.

image

image

2024.624

@lwis
Copy link
Member Author

lwis commented May 12, 2024

This is still happening, please let me know if there's any way I can help!

@bgoncal bgoncal reopened this May 12, 2024
@bgoncal
Copy link
Member

bgoncal commented May 12, 2024

Im doing some clean up around shortcuts, widgets and intents in general, I'll let you know when you can test it again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants