I tried again, starting an upload then backgrounding the app by hitting the side button, keeping the lock screen unlocked (no lock icon). Again the BGContinuedProcessingTask kept updating progress, after which it (correctly) reported the upload as completed. So I think it is safe to say that the issue only happens when the device is truly locked.

It is also failing on iOS 26.2 Beta 3. I've filed a Feedback Assistant issue: FB21233240

Hi Kevin, I just did a quick test on 26.1 and the issue still happens: the BGContinuedProcessingTask is expired even though the upload is progressing and actually completes. I'll have to do more testing to confirm, but it appears to me that this only happens with the screen truly locked (lock icon showing in the status bar/dynamic island). When Face ID has seen me and the lock icon disappears, the BGContinuedProcessingTask is updated properly. We're going to give it a try on iOS 26.2 beta as well and if it still happens, I'll make a FB report.

I'm glad I found this thread because we're experiencing exactly the same thing. We're uploading a large-ish (hundreds of MB) file to AWS S3 and using a BGContinuedProcessingTask to show the progress. The actual upload happens in the background using the AWS S3 SDK. Everything goes fine until we lock the screen, then the BGContinuedProcessingTask is expired even though the upload is still ongoing. Is there any resolution on the horizon for this issue? Would it help if I file a Feedback Assistant report or can I join an existing one?

Xcode 15.4: still happening. Xcode 16 beta: still happening. Come on Apple, do something about this!

We are experiencing the same: a lot of <<<< AVPointCloudData >>>> Fig assert: "_dataBuffer" at bail (AVPointCloudData.m:217) - (err=0) lines in the debug console when we start our ARSession, during which the app appears to hang. It uses an ARSCNView but that just stays blank. Then after some time (10-20s) everything goes back to normal and the camera feed is shown. We've been seeing this on a range of iOS and iPad OS devices. This is obviously problematic because users will think the app has crashed.

We get the same in our app, using ARKit (ARSCNView). Just a ton of these <<<< AVPointCloudData >>>> Fig assert: "_dataBuffer" at bail (AVPointCloudData.m:217) - (err=0) while the ARSession hangs for some time (up to 20s). And then it works normally.

Yes, same here.

I think textContentType should be .newPassword, not .password. Not sure if that will help though, I've been having similar problems but only on iOS 16. On iOS 15.7 everything works fine.

The issue appears to have been fixed in iOS 15.2. Nothing about it in the release notes but it looks like relocalization works like it used to, again.

(or maybe better session(_ session: ARSession, didUpdate anchors: [ARAnchor]) of ARSessionObserver, to not be dependent on SceneKit.)

If I'm not mistaken, the transform of this ARAnchor that was added just before saving will not be updated after a relocalization until the moment it is in the camera's field of view again. So the after relocalization, the user should be made to point the camera at this ARAnchor and then when the ARSCNViewDelegate func didUpdate is called, we can use setWorldOrigin(relativeTransform:)?