I'm impressed by how you discovered that. For intellectual interest, could you describe how you reached that accurate conclusion using Instruments? As for the workaround, I'd recommend using a serial Queue.

-- error -- can be deleted

Thank you, much appreciated!

@DTS Engineer: any idea? Because stripping my project to a test project will take a considerable amount of time. Since I narrowed the bug to the last line of the Spotlight indexation, it might be a valuable clue: CSSearchableIndex.default().indexAppEntities([entity]) Thank you 🙏🏻, because my large app update is blocked because of this.

I'll do that. How am I to send it to you?

Hi Ed, Thank you for your answer. I tested with attributeSet.contentType = UTType.plainText.identifier but it does not help, unfortunately.

Same here, files are left on the watch!

relative altitude updates are still the same, I agree with you. However, absolute altitude updates are definitely not. Also, while I appreciated your suggestion, which makes total sense, I don't think it is the reason. Why? Because CMAltimeter can be used without CLLocationManager, and the issue is still present. I have extra information though: 1 of the 2 test devices has the altimeter that works again. There is something new in Core Motion that somehow can block the absolute altitudes.

Hi! Thank you for your help, but one important detail is missing, hence the 2nd bullet in the original post: will the callback always be called at some time, even if the transfer finishes while the app is in background? Thanks a lot!

Same issue here :/

This is the correct solution.

Thank you for posting this. Unfortunately, I do not have that extra "." Must be something else.

Filed FB11655726 Oct 6th

How could it work? I thought ATS that is enabled by default would prevent this?

Yes my workflow looks like this. My shortcut-step would be the 'Mark up' step on the screenshot. I'm in contact with DTS saying it's a bug that I can't link to 'shortcut input'