We are observing an issue on iOS 26.6.x where the Personal Hotspot SSID stops being advertised after a period of time, making it unavailable for discovery by nearby devices. This behavior impacts our device onboarding workflow, which relies on connecting to the iPhone's Personal Hotspot. Once the SSID is no longer advertised, nearby devices are unable to discover and connect to the hotspot. Based on our testing, the behavior appears to be independent of our application and seems to be controlled by the operating system. The same behavior is observed even when our application is not running. Observed Behavior Personal Hotspot is enabled and initially discoverable. After a few minutes, the hotspot SSID is no longer visible to nearby devices. Devices can no longer discover or connect to the hotspot. Simply opening the Settings app again causes the hotspot SSID to start advertising immediately and become discoverable once more. The behavior is reproducible on iOS 26.6.x. Expected Behavior While Personal Hotspot remains enabled, the hotspot SSID should continue to be advertised and discoverable by nearby devices without requiring the user to reopen the Settings app. Alternatively, if this behavior is intentional, clarification on the expected hotspot advertisement lifecycle and any related system policies would be appreciated. Impact This issue affects workflows that depend on persistent hotspot availability for accessory provisioning and device onboarding. Users may be required to repeatedly open the Settings app to make the hotspot discoverable again, which negatively impacts the provisioning experience. Questions Is this a known change in Personal Hotspot behavior in iOS 26.6.x? Is it expected for the hotspot SSID to stop advertising after a period of inactivity? Is reopening the Settings app expected to restart hotspot advertising? Are there any new power management or system-level restrictions affecting hotspot discoverability? Is there a recommended approach for applications that depend on consistent Personal Hotspot availability during device setup?

We have developed an app that communicates with an external reader using BLE, and the reader also supports NFC. We are implementing a feature that uses PKPassLibrary.requestAutomaticPassPresentationSuppression to prevent the Wallet from appearing when unlocking a lock. We have already completed the approval process for the entitlement required to enable Pass Presentation Suppression, referencing Apple’s documentation: https://developer.apple.com/documentation/passkit/pkpasslibrary/requestautomaticpasspresentationsuppression(responsehandler:) In most cases, this works as expected and the Wallet popup does not appear. However, in some cases — particularly when the app is running in the foreground — the Wallet still appears for users. We have verified that the app bundle includes the required entitlement, and the Info.plist correctly specifies the Pass Presentation Suppression key set to true. Could you please help us understand under what conditions this behavior might still occur, or if any additional configuration is required?