But it's not semantics or 'my opinions' - I'ts wrong. Xcode highlights the line locationServicesEnabled() and suggests I should instead wait for locationManagerDidChangeAuthorization which does not do the same thing. Your answer "locationServicesEnabled() has everything to do with authorization" is simply incorrect and it's unfortunate that it becomes a highlighted answer next to my original post. I want the warning to go away, but the remedy suggested by Xcode will not solve the problem. I suppose I do agree that it's fruitless to argue any more. :) I'll try and file a support ticket.

Hey, thanks for responding so quickly. Yeah we only have png images. They're defined as a resource in the widget target. I have found one resource that works that I was using in the "minimal" view, but other images that are in the same resource collection don't work. Could it be a size issue?

Hey thanks for responding. Yeah sure I know what to do to try and fix it, my question was more about why it looks so different :)

Thank you so much, Frameworks Engineer! :)

Rico, thanks for response. That's a great hack :) It feels strange though to go through all those hoops and unnecessary server traffic for a local-only need, when it could be solved by letting the user give the app permission or something. It could be a dialog like it is for live activities now, but for background initializations?

Hey thanks for responding. What's puzzling is that widgets updating from app have basically zero problems. It's only when the live activity is the one updating. To me, it would make sense that since the docs say that button presses from widgets are not subject to the budget, neither should live activity button presses be subject to the budget restrictions for updating the widgets, but it seems not. Is it possible to confirm that live activities ARE restricted by the update budget? In that case, I can at least know that I don't have a bug in my app.

Hey, I already have a case-id, 9879068 is that good or do you need me to file something separate? (I have included my test project in that ticket)

Hi there, any chance of an update here? As I mentioned I tried to use up one of my 2 code-level support tickets, no response there either.

Hey huge thanks for responding and sorry for being late I missed it! OK. A couple of comments: 1 - Your last comment, it's not accurate. In our app, we have Lock Screen widgets. They are visible at the same time and it looks very strange that they do not get updated when the live activity does. If you do it from the Dynamic Island and have a widget below on the Home Screen, you can see it there too. This is a big reason to why we think it's so bad. 2 - It's not really an issue if the widget being updated 5-10 seconds, or perhaps even 30 at times. However if you run my example app you quickly see that often the widget isn't updated at all, even hours later. 3 - This happens a lot. We have been running this for weeks, and we quickly get in to situations where the widgets aren't updating for hours or for the rest of the day even though the live activity has been updated over 50 times. Again, always works in Xcode. To me, it's clear that this is not a battery or prioritization issue because it happens consistently after a while. This is why I mentioned the "budget" thing possibly being an issue despite the documentation saying otherwise. 4 - I've seen this behavior in other apps that have both Lock Screen widgets and live activities. To summarize: To me, this is an obvious flaw. It provides a bad user experience. If you tested my simple project, surely you saw this? So, my final 2 questions are these: 1 - I am not doing anything wrong as in the code has errors that can be fixed? The inconsistent or skipped updates is working as intended? 2 - Should I create a bug report? Would be great with a confirmation/response so that we can think about whether to actually go live with this. Again, thanks for your time, appreciated.

Hello, in addition to here and a support ticket, I now also went ahead and created a bug report, FB15909487. I would also really appreciate further discussion in this thread.

i am using xcode 26.0. If i deploy it from there on my phone running 26.1 or 26.2 i get the strange flip. but if i instead deploy it on one running 18.5 (all iphone pros) , the animation is wrong.

I guess not :)

Please find attached a small demo view controller i made that shows the bug. It looks as expected prior to 26.1 but is bugged in 26.1 and onwards. (i tried attaching a zip of the entire project but alas not allowed here) Demo view controller

Yeah, i've seen that tech talk, and i know it's deprecated. I know the limitations and agree, but i mean, it wasn't deprecated before :) None of the texts refer to situations where you only have a short time to do your thing, such as a network request in response to user interaction from a live activity or a geofence trigger like we do a lot. For our geofence triggers for example: It's crucial for us that if a network request fails in the trigger, we can end it by posting a local notification to the user "the thing failed because of X". This won't happen if the system kills the trigger in the middle of the request waiting for network connectivity. In that case, it's better with a false positive for us, than nothing at all, because then we can be certain that the user is informed.

In addition to my comment to your post: i tried the demo project on 26.2 and it's still there.