I provide a paid feature behind an annual auto-renewable subscription, using StoreKit 2 and Transaction.currentEntitlements. Many of my users work in remote places with no connectivity for days at a time, so I need to know what happens when a device is offline at the moment the current period ends. The renewal succeeds server-side, but the device cannot fetch the updated signed transaction, so the cached transaction still carries the previous expirationDate, now in the past. Does Transaction.currentEntitlements stop returning the subscription once the cached transaction's expiration date has passed, even though the renewal has already succeeded server-side? Is there any built-in tolerance window on the device that keeps the entitlement alive until the next successful sync with the App Store? Does grace period effect the outcome? I want to avoid revoking access from a paying subscriber who happens to be offline when renewal falls due. Many thanks.

Hi, On iOS 17 beta I have drawn a Map inside a NavigationStack with toolbar buttons. The map is drawing itself above the toolbar background and behind the toolbar buttons, that is the map is drawing right to the bottom of the display but the buttons are visible on top of the map. The Apple Maps logo etc has honoured the safe area correctly. Anyone seen this and know why or how to avoid this? If I replace the map with another view the toolbar is handled properly. Any suggestions appreciated, cheers.

Hi, I have an iPad app using a NavigationSplitView in 3 columns. The far left sidebar is initially hidden. NavigationSplitView automatically includes a button to show the sidebar but once it is displayed the button is removed so the user has no obvious way to close the sidebar again (you can swipe it away but who knows that?). The sidebar contains a List just like the builtin Notes app. I have a "columnVisibility" property to track the display state of the third column. Does anyone know how to either: Detect that the user has selected something in the sidebar List so the sidebar can be hidden using the columnVisibility property, or Keep the toggle button around so the user can close the sidebar with that? Thank you for any ideas you may have. J

I have been testing an update to one of my apps this week and I intended to release the app yesterday. All builds uploaded before yesterday (Friday) report a deployment target of iOS14.1 (it is built with SwiftUI) but just in the last upload done yesterday reports a deployment target of iOS 11. On checking further this has happened to another app written with UIKit that has been requiring iOS14.1 until Friday when it changed to iOS11. Anyone else had this completely bazar problem? I believe it's an Apple problem as I don't think Xcode could even build a SwiftUI app with a target of 11 and two apps suddenly change on the same day???