I wanted to reach out here to see if I can get any information on our specific similar-but-different scenario: We are implementing interactive Live Activities for iOS 18. We have everything working perfectly where tapping a toggle on the live activity sends the intent to the App, the App updates the state and the Live Activity updates. This works totally fine and exactly as expected. We aren't doing updates frequently so they all seem to be delivered. Our App however uses background audio in order to play a rest timer expiration sound (it's a workout logging App). As soon as we start using background audio the Live Activity updates become very unreliable and we start seeing the logs above. What I can't understand, is that it works fine without the background audio. In that scenario, iOS wakes up the App to process the intent, compute the new state, and send it back to the Live Activity. In the background audio scenario, the App is already running in the background, but in that scenario iOS blocks the Live Activity state update. Is this just some sort of edge case we've run into here? Not supporting background audio isn't really an option since rest timers are a critical part of our App, but it feels like an iOS bug that our Live Activity would work perfectly without background audio, but is almost completely broken with it.