User Profile

In the "Privacy updates for App Store submissions" section, the addition of a privacy manifest file is required for app releases after May 1. We added a subdomain and defined it in NSPrivacyTrackingDomains, but when we separate the subdomain and main domain as "tracking.example.com" when ATT is allowed and "example.com" when ATT is not allowed would the communication on the main domain not result in an error? I couldn't figure it out exactly from the documentation or the session, so please let me confirm. Documentation: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files Session (domain definition): https://developer.apple.com/videos/play/wwdc2023/10060/?time=387

In the "Privacy updates for App Store submissions" section, the addition of a privacy manifest file is required for app releases after May 1. We added a subdomain and defined it in NSPrivacyTrackingDomains, but when we separate the subdomain and main domain as "tracking.example.com" when ATT is allowed and "example.com" when ATT is not allowed would the communication on the main domain not result in an error? I couldn't figure it out exactly from the documentation or the session, so please let me confirm. Documentation: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files Session (domain definition): https://developer.apple.com/videos/play/wwdc2023/10060/?time=387

Hi, team. We are implementing a process to obtain Bluetooth usage permissions in order to use Bluetooth by iPhone, and we are having some unexpected behavior in the process, so we need someone's help. The problematic behavior is that the centralManagerDidUpdateState is not called after the user makes a selection in the Bluetooth authorization dialog. Expected behavior Instantiation of CBCentralManager Bluetooth authorization dialog appears on the screen Select "Allow" in the permission dialog After selection, centralManagerDidUpdateState is called CBManager.authorization becomes .allowedAlways Problem behavior Instantiation of CBCentralManager Bluetooth authorization dialog appears on screen centralManagerDidUpdateState is called before selection Select "Allow" in the authorization dialog After selection, centralManagerDidUpdateState is not called What could cause the centralManagerDidUpdateState to be called at such a time as the problematic behavior? Supplementary explanation CBCentralManager is held as a property and the instance is not released when the dialog is selected in the problem behavior. CBManagerState of CBCentralManager is .poweredOn and CBManager.authorization is .notDetermined in centralManagerDidUpdateState during problem behavior.