Made me test overlays in my apps in airplane mode. I have MKTileOverlay, the bottom one. TailOverlay : NSObject , for the track line. CourseLine : NSObject , for the top course line. They have drawing renderers (except for the MKTileOverlay) and Apple fixed, with that mentioned MKOverlays fix in iOS 16.4, the performance and reliability of drawing on top of MKTileOverlay among other things. All shown in the airplane mode. Am I missing something else to make it fail? If you want to run any "what is different in our code", let me know. Similar experience with Apple for the FBs/TSI. I used "Ask Apple" in December (I think) and a nice guy checked the status for that "performance and reliability of drawing on top of MKTileOverlay" and at least I knew it's being fixed. No updates to related FBs, ever. --Stan.

@nickradar. Went for a drive now with iOS 16.4 public and for me it all works 100% unless I'm severely overlooking something. I do have showsBackgroundLocationIndicator = true on the location manager that records a track. I don't have it on the location manager that listens for regions (iBeacons), but I do call startUpdatingLocation() on a region location manager before handing it over to the track location manager with showsBackgroundLocationIndicator = true, otherwise my track recording location manager would not start/stay recording in the background, I thought it was iOS specific - it might be iOS 16.4 specific then. I have competitor apps installed for the automatic mileage tracking, and 2 of 5 (all that really track) recorded now something like: That would correspond to points in the significant location updates, maybe. No recording in between. That's going to be interesting. One more thing, on significant location events I do ask for the background time extension. Not sure that plays any role, I ask due to other things, but also start a probing location manager that has showsBackgroundLocationIndicator = false and it works. Hope this will not give Apple any wrong ideas :).

I tried now on my iPad with iOS 16.4 RC and there is no problem with the app staying in the background. I switched off significant location updates as well as part of the experiment, the app still stays in the background with no problem. ~20 minutes now. If you can test this on iPad with iOS 16.4 then we can see if this is iPad vs iPhone that makes a difference or something in your vs mine configuration of a LocationManager.

I've been testing iOS 16.4 on iPad since day 1 and it runs in background location 24x7, I specifically and continuously test for this use case. Are you sure this is not some kind of crash that would be happening after these 10 minutes that might be bringing the app down? There might be differences between location services on iPad and iPhone though.

Looks like iOS 16.4 Beta 1 solved the performance issue with drawing on MKTileOverlay. Looks like a few performance issues might have been solved. Hopefully is stays this way.

I might have a related FB to this issue, or more related to iOS 16 MKMapKit performance degradation when it comes to overlays that need to draw. It's "iOS 16 regression - MKMapView flicker with MKTileOverlay and MKOverlayRenderer with draw().". I have FB FB11805267 with the sample project that reproduces the issue. I used "Ask Apple" and I got confirmed that issue is known and is assigned a high priority. Then I used a DTS to ask if there is a workaround (e.g. I hoped I could only provide the overlay path and will not draw) and that returned back unused. Going to add a link to this thread to my FB.

I'm trying now in iOS 16 and setting Background Refresh as OFF for the app doesn't affect regular background location updates. Looks like documentation for this permission has been significantly changed to only relate to the Background Refresh Tasks: https://developer.apple.com/documentation/uikit/uiapplication/1622994-backgroundrefreshstatus

Monterey with M1, same problem.

Didn't work for most of Wednesday, then started to work Thursday morning (CET) for me. And now, Thursday evening CET it is not working again. I see the new build in the Testflight, but after a spinning circle on UPDATE/INSTALL it returns to the non-installed, non-updated status.

Not working for me as well. I have swift+objc codebase, not sure if this can be the reason.

Same here. What worked for me was to remove the preview part from the code, save. Added it back and it all worked.

Be sure to report it to Apple.

As I understand, it should be a bug with Xcode and App Store Connect. You better create a feedback for Apple. See the related thread: https://developer.apple.com/forums/thread/714736?answerId=727968022#727968022

In my case (Dell 40" with thunderbolt/usb hub) it was me tweaking the power management settings earlier and then all usb ports being down after OS update every time mac book went into sleep and woke up. sudo  pmset restoredefaults and restart helped for good.

Same thing here, with different selector names.