It’s working but only when I redeem it through the sandbox account management in the developer settings. If I try to redeem it via my app I get a message saying I need iOS 16.3 or later, when I’m clearly on iOS 26. Clear Purchase History is also not working. Even after reinstalling my app it still fetches the redeemed purchase.

I'm on the latest beta and I'm still not seeing the dividers in my iPadOS menu bar.

18.6.1 is only available for iPhone.

Sorry for the late response. Just got around to testing it on iOS 26 beta 8. It's still the same as before, but when locked it doesn't always fail the task. But it remains paused and doesn't progress until I wake up the screen. Feedback ID: FB19916760 I've also added setTaskCompleted(success:) and now it shows a tick when the background task is complete.

Done. Feedback ID: FB18653201

Looks like it’s been fixed in iOS 18.5 beta 2

I've recently found that the crash also happens on my old iPad with iOS 16.7.10 when using .backgroundTask(.appRefresh) and attempting to run a shortcut while force closed. This makes it seem like it's an old bug that has returned in iOS 18.4. Looks like the modifier is no longer an option for me and will have to permanently stick with the old way.

Looks like uploads are working now

FB17006467

This bug made it into the release candidate. Very disappointed! Now, to move over to the old way completely I need to switch the task identifier to the reverse DNS. But the problem is: The SwiftUI .backgroundTask modifier can't be there at all otherwise the crash will persist Not having the modifier means the old identifier won't be registered and thus if the old background task runs when the user updates but doesn't open the app, it will crash as the launch handler hasn't been registered How can I migrate to the old method without causing any crashes?

With my app force closed from multitasking I tried running my app's shortcuts and control centre buttons. I was able to make it crash almost every time if the app was swiped away from multitasking. This however only happens with the .backgroundTask modifier in iOS 18.4. I wasn't able to reproduce the crash with BGTaskScheduler.shared.register(forTaskWithIdentifier:). So my question is, if I move over to using the old way, do I have to make my identifier reverse DNS? Or can I keep using the existing notifications identifier that I already have?

On macOS 15.4 beta 4, the toolbar button isn’t truncated anymore but the issue of the back button overlapping the title and being not clickable is still present. The only way to get around this issue is to hide the back button using .navigationBarBackButtonHidden(true) and then make my own back button using the navigation toolbar placement.

This bug is still present in macOS 15.4 beta 3 24E5228e. Is there anyone from Apple that can help with this? It's affecting one of my apps on the App Store.

Looking at the macOS 15.4 screenshot more closely, it looks like the back button is overlapping the navigation title.

Fixed in iOS 18.4 beta 2