file uri scheme

so the BluetoothManager.scan... was a hardware problem. now I see {msg:#Warning Error reading file, file://private/var/Managed Preferences/mobile/com.apple.CoreMotion.plist, error:Error Domain=NSCocoaErrorDomain Code=257 The file “com.apple.CoreMotion.plist” couldn’t be opened because you don’t have permission to view it. UserInfo={NSFilePath=//private/var/Managed Preferences/mobile/com.apple.CoreMotion.plist, NSURL=file:////private/var/Managed%20Preferences/mobile/com.apple.CoreMotion.plist, NSUnderlyingError=0x14cc64ea0 {Error Domain=NSPOSIXErrorDomain Code=1 Operation not permitted}}} I have the motion privacy tag in the plist for the code doing request camera assistance in the connect handler for the nearby operation.. in setup accessory dump of capabilities direction = false device does not support direction measurement device DOES support camera assistance here is the code logger.info(dump of capabilities direction = (NISession.deviceCapabilities.supportsDirectionMeas

Through additional page modifications, we've confirmed that the volume of font files linked within CSS also affects the crash. While the site currently loads without errors when scheduled for live service, this means the issue could reoccur if the volume is increased at any point in the future. Furthermore, page load failures are also affected by the native volume of the app loading the page. Our own WebView app for the App Store, in previous versions (version 2.0.1 on TestFlight), was able to load pages before the workaround was applied with a very high probability. However, even if the source code was maintained, simply updating the included libraries to the latest version resulted in unconditional load failures. Our current, upcoming release version of the app has increased the volume even further, resulting in a lower page volume limit than the maximum page volume allowed in Safari on iOS 26. (The amount of CSS used during the initial load must be reduced to a very extreme level.) We sincerely ho

These developer forums are no suitable to discuss user level issues with other apps. If you are the developer for an affected app with this issue, please send details of notifications that you have sent that has not been delivered. Please share the following details of a notification that has encountered the described problem on iOS 26. Please share a new example in the last couple of days. exact time and date (including time zone) of the push request sent exact time and date (including time zone) of the notification being received the method of determining the delay (user anecdote, logging from app, logging from your servers, etc.) the public IPv4 address of the server used to send the push the apns-id If you can't provide the apns-id, we'll need some of the following info your push topic (apns-topic header value) your app’s Bundle ID the device token full contents of the headers and the payload any logging you have from the server side that shows the interaction with it and APNs. If you are not comfortable

Filed as FB20409458 with a test project that demonstrates the problem. Thanks.

Hello Have you filled a feedback issue for this issue yet? There were no audio-related changes in SpriteKit this year, so we will need to investigate if something changed in the lower-level audio interfaces that SpriteKit uses. A feedback issue with a sample project, or at least the problematic audio file, would be helpful.

Having dug into this some more, I now think it's nothing to do with my code. The games with working sound effects have two-channel effects (stereo). The ones that don't have single-channel effects (mono). It appears that the ability to play back single channel (mono) audio files has been broken in SpriteKit on Tahoe. Hopefully this helps someone else. In the meanwhile I'll prepare a round of updates with stereo sound effects to work around the problem.

We've finally found a way to bypass the iPhone's loading crash issue. We split the culprit CSS file into multiple files, leaving only the minimal CSS links needed to display the splash screen, and lazy-loaded the rest within the framework after the page's onLoad event. This allowed the pages to load without crashing, and it worked for all three sites mentioned in this article. However, this issue isn't resolved. It's simply unacceptable that a DOS-era 360KB memory limit exists in 2025. This issue still needs to be addressed, and until it is, it will remain a blemish on the iPhone. In that spirit, we'll keep the three separate sites mentioned in the reply above available for reproduction, and we'll await Apple's official response in this thread. If anyone reading this thread agrees with this, please give it a boost.

@Kim Ju Young Thanks for your comment, if that's a known issue, would you mind create a bug so we can track it? Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.

I think it's worth noting that there are a number of other posts. Please consider filing bug reports as well and posting the bug numbers here. Duplicates matter and help engineering quantify how many developers are affected by an issue. Bug Reporting: How and Why? has tips on creating your bug report.

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

Do you have a suggestion on how to achieve the same workflow style as the native camera? One where it is possible to pinch to zoom smoothly between lenses and still capture a higher resolution raw file.

I'm trying to write to a file How!? By way of fileExporter(isPresented:document:contentType:defaultFilename:onCompletion:) ? If you use fileExporter and gets a permission error, that's most likely because you are not using the security-scoped bookmark.