file uri scheme

Will you please file an incident report with Apple using feedbackassistant.apple.com ? Please include a sample of the code you're using to capture from the camera. 48 MP capture doesn't happen without specific opt in at the AVCapture API level.

Thanks for reporting the issue. Do you have a feedback report yet? If not, would you mind to file a feedback report and share your report ID here? Be sure to mention that the issue only happens on iOS 26.x. Thanks! Best, —— Ziqiao Chen  Worldwide Developer Relations.

Thanks Albert. I’ve filed FB20714325

The github explains the format fairly well. I've added info from my eBook content after saving the Pages version as plain text. I created the train.json file by breaking the text file into lines an added '{text: My text info}' around each line My text info. I fudged the valid.json file by including a small part of the train.json. The biggest problem was finding special characters in my original that weren't json compatible (e.g. tab character). This was just for adding 'text' content to the model using LoRa.

Thank you for sharing the post and providing all the necessary information. I greatly appreciate your efforts. Let us proceed with filing a bug report for the sample and its description. Once you open the bug report, please post the FB number here for my reference as I am very interested in this issue. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Looking forward to get to the bottom of this. Albert Pascual
  Worldwide Developer Relations.

fileVerA not existing on device B explains why currentVersionOfItem returns fileVerB. But as you've pointed out and the documentation mentions , presentedItemDidGain(_:) is supposed to be called after a new version was added, which does seem to conflict with your observation. I’d hence suggest that you file a feedback report – If you do so, please share your report ID here. In presentedItemDidGain I check if the URL passed in is in a conflict state by using 'newVersionURL.isConflict', and it returns true, and then I run the merge. Is this the right way to check for a pending conflict? Yes, the above flow sounds right, assuming presentedItemDidGain is called at the documented timing. Best, —— Ziqiao Chen  Worldwide Developer Relations.

If you're able to reproduce this issue, could you please file a but report, using the steps here: https://developer.apple.com/services-account/download?path=/iOS/iOS_Logs/CoreMedia_Logging_Instructions.pdf

I experienced this problem in XCode 26.0.1. My app has a single target configured with iOS and macOS destinations. For macOS, my app requires the sandbox entitlement for calendar data access. I fixed the error by: Removing the com.apple.application-identifier, com.apple.security.app-sandbox, and com.apple.security.personal-information.calendars entries from the app's AppName.entitlements file. Adding the sandbox and calendar entitlements back by adding the corresponding capabilities in the app target Signing & Capabilities settings. Toggling off and back on Automatically manage signing. I believe this worked because sandbox capability entitlements are only injected for macOS, while entitlement file entitlements were injected for all destinations. Hopefully this helps others with similar dual-destination setups.

Thank you for your assistance and providing me with this information. May I ask you to submit a bug report against TestFlight. 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? Please post the FB numbers here! Thanks again for your help on this one. Albert Pascual
  Worldwide Developer Relations.

This is not a bug in the provisioning profile generation service, and the issue is indeed a misconfiguration on your side. The App Attest Environment Key in the provisioning profile is the correct one, and the one you have included does not exist. The provisioning profile and your project entitlements must match, and a provisioning profile will not include an otherwise non-existent entitlement entry. The key com.apple.developer.app-attest.environment is not a valid entitlement - it does not exist. So you can't add it to your provisioning profile. You need to remove that from your entitlements file. I don't know which resource you found this in, but whatever they have recommended is completely wrong. You will want to read the proper documentation to understand how this all works, and what entries you need to setup in your project.

I notice the exception is on: NativeSet.insertNew(_:at:isUnique:) + 376 (/:0) Looking at this thread: https://forums.swift.org/t/substring-violates-hashables-requirements-stdlib-compiler-bug/58046/7 I wonder if the compiler is not confused and considering you try to insert a substring. To make sure, could you try: let sub = self[index...] // a substring let theStr = String(sub) return if index == endIndex || basePath == / { theStr // String(self[index...]) // for sure, a String } else if let index = self[index...].range(of: /, options: .anchored)?.upperBound { theStr // String(self[index...]) } else { nil } If that works, you should file a bug report.

There are a number of Bluetooth related fixes in iOS 26.1 on iPhone 17. Please test with the current 26.1 beta 3, and see if the issue continues for your app/device. If it does not seem to be fixed, then we'd need specific information about the issue. We need a specific diagnostic log. Please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Bluetooth for iOS to install a logging profile on your device. Then reproduce the issue, and follow the instructions at the above link to create a sysdiagnose. In that case, please open a bug report, include the sysdiagnose from above step, any other logs you might have, and sample code or models that reproduce the issue, and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating a successful bug report. Important: For feedback related to a specific framework or API, select Developer Technologies & SDKs as your Topic, then select the specific technology and relevant OS. For feedback relate

Also, I learnt that apple-app-site-association (AASA) file structure has also changed. { applinks: { details: [ { appIDs: [MYTEAMID.com.example.myApp], components: [ { /: /* } ] } ] }, appclips: { apps: [ MYTEAMID.com.example.myApp.Clip ] } } i.e with respect to my previous AASA file, I had to do the following: instead of paths we need to add components as above. in the applinks we should add the main app bundle id (not the clip's bundle id) removed apps: [], from the applinks section. Hope this will help someone.