file uri scheme

Sorry I didn’t reply sooner; older versions of DevForums had a bug that meant that I didn’t see updates on this thread (that’s fixed now, so yay!). [quote='785947022, Najjii, /thread/675290?answerId=785947022#785947022, /profile/Najjii'] edit the trust settings to be able to use it normally. [/quote] Monkeying with trust settings on a code-signing certificate is a bad idea. It can trigger the dreaded errSecInternalComponent. I talk more about this in Fixing an untrusted code signing certificate. [quote='794668022, olvrwn, /thread/675290?answerId=794668022#794668022, /profile/olvrwn'] Is there any information why this does not work with iCloud Keychain? [/quote] Not really. Keychain Access is very much on the way out as a user-level feature. Witness, for example, its recent move from Applications > Utilities to /System/Library/CoreServices/Applications. Given that, it’s easy to see why big picture issues like this aren’t being addressed. Having said that, the file-based keychain is also on its way

We can’t really help you with Wi-Fi level issues here on the forums. My advice here is that you file a bug so that our Wi-Fi engineering team can investigate. Make sure to include: Wi-Fi debugging information Your analysis so far Regarding the former, see the Wi-Fi for iOS/iPadOS instructions on our Bug Reporting > Profiles and Logs page. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Sorry for the delay, but I’ve filed a bug report as well. The ID is FB21167471. Posting it here for reference.

Mountain peaks don't correspond to a point of interest category you can filter for. You can see the category for a selected map item and look at the value of the pointOfInterestCategory property, which can be nil, such as for mountain peaks like Mount Whitney or Mauna Loa in the United States. Please file an enhancement request for mountain peaks to become a point of interest API, and post the FB number here for the record. — Ed Ford,  DTS Engineer

Hi @zaalup There are two parts to this: the broadcast extension code and the passthrough-in-screen-capture entitlement. First, verify your broadcast extension is working: Can you get the extension to capture video when you haven't configured the passthrough-in-screen-capture entitlement? You should be able to record the screen without this entitlement, the difference is that the captured video will show your Vision Pro's content over a black background instead of passthrough. This will help isolate whether the issue is with your extension setup or specifically with the enterprise license. Next, troubleshoot the entitlement/license setup: Do you have multiple apps from your developer account installed on your Apple Vision Pro? If so, check that none of them have expired licenses. I've seen instances where an app with an expired license can cause other apps from the same developer to behave as if their licenses are also expired. Additionally, use VisionEntitlementServices to verify your license is set up correc

Hello skywind, Thanks for your question. The replacement for modalInPopover is modalInPresentation, as can be seen under the property declaration in the UIPopoverSupport.h header file. For additional context, please refer to WWDC 2019 presentation Modernizing Your UI for iOS 13, specifically at the timestamp. Thank you for your patience, Richard Yeh ||  Developer Technical Support

Thanks for your post. It seems like you have everything working. So you do not see the autofill behavior after following this documentation? https://developer.apple.com/documentation/security/password-autofill Can you provide me a link to your AASA file showing how you have defined the web credentials for the app? https://developer.apple.com/documentation/Xcode/supporting-associated-domains Example: webcredentials: { apps: [ ABCDE12345.com.example.app ] }, Looking forward to your reply. Albert Pascual
  Worldwide Developer Relations.

Hi @davidcwps, Are you still seeing this issue with nearby sharing? If so, can you provide some code showing where you start observing for active sessions and how that method is implemented? if you don't feel comfortable posting that or would like to include more code, feel free to file a feedback report at https://feedbackassistant.apple.com with any attachments and add the FB number here, so I can see it. Another good test would be to create a small project with the smallest amount of code possible just to set up the session and test it with nearby and see if that works.

Hi @MadGM, This sounds like a bug to me. I also tried and can reproduce the same issue. Can you file a feedback report at https://feedbackassistant.apple.com with a sample project and respond here with the FB number? Interestingly, I did notice that the resizability is available with the automatic window style, although the image is obscured. I did not find a workaround, but if I do I will respond back here.

Hi @BrianMcDonald Does the name of the folder containing your environment resource texture end in .skybox? As the Create a skybox folder section of the EnvironmentResource documentation describes, you must place your environment resource texture into a folder with a name that ends in .skybox. That documentation also confirms that .hdr files are supported. Let me know if you're still running into issues loading the environment resource after following those steps, and I can investigate further!

I agree that we need to handle scenarios such as force quit or unexpected termination, and we are improving those cases. However, I would still like to clarify the behavior specifically during app updates. On macOS 15, the app terminates cleanly, but on macOS 26, it is immediately killed without entering any shutdown flow. We would like to understand whether this change aligns with the AppleEvent-based quit model you mentioned. Specifically: What is AppleEvent? AppleEvents are one of the mechanisms the system uses to deliver actions into your app. As a concrete example, take this sequence: Right-click on an app’s dock icon. A menu appears. Select Quit. App quits. The menu presented in #2 is part of the Dock, NOT your app, which means your app didn't have any direct involvement with presenting that menu. The way it found out it was supposed to Quit was that it received the quit AppleEvent. The event system itself isn't all that well documented because most apps don't actually interact with it all that much. Fo

Hi @BrianMcDonald Are you building for visionOS? RealityKit attachments are only available in visionOS, and you will encounter the above error if you try building for a non-supported platform, such as iOS or macOS. If you'd like us to consider adding the necessary functionality, please file an enhancement request using Feedback Assistant and post the FB number here. Thanks!

Thanks for the post. Thank you for providing a screen recording and a focused sample of the bug filed. Your assistance is greatly appreciated. I believe this could be a bug, but please provide the engineering team with the opportunity to review your submission. They will communicate with you through the feedback assistant application. For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.