“file uri scheme”

Is there any supported way for a sandboxed macOS app to read an MDM-delivered preference plist under /Library/Managed Preferences/? Any guidance on the correct and Apple‑supported method would be appreciated. There are basically two ways to make this work: Have the user select the file or directory using an open panel (or drag and drop). Use an entitlement that gives you access to the target directory. In this particular case, that means using one of the File Access Temporary Exceptions to hard-code access to /Library/Managed Preferences/. A few notes on that: The documentation suggests using Shared Preference Domain Temporary Exceptions. I would certainly try that; however, I suspect it won't work as Managed Preferences may not be part of the standard preference system. While there's always an inherent risk in using a temporary entitlement, I generally consider this particular entitlement set to be relatively safe. The entitlement’s role is clear and straightforward (it gives access to the

After additional testing, this appears to be an orphaned MobileAsset cleanup issue rather than a normal simulator uninstall problem. The runtime payload remains on disk under /System/Library/AssetsV2, but in some cases Xcode no longer exposes it in Components/Platforms and simctl does not have a usable reference to remove it cleanly. In other words, the asset still occupies space, but the supported management tools have effectively lost authoritative control over it. At that point the problem becomes structural: the remaining files are in a SIP-protected system location. So even if the exact asset folder can be identified, it cannot be manually removed through normal user-space means while SIP is enabled. That leaves no supported path to reclaim the space once the asset has fallen out of Xcode/simctl management. Technically, the remaining workaround is to disable SIP and remove the orphaned asset manually, but that is not a reasonable solution for routine simulator runtime cleanup. SIP exists specifi

@JorisVD We are working on understanding the problem and looking for a fix. We could use as many incidents with detailed logs as possible to help with finding a root cause. If you can, please file a bug report with Bluetooth debug logs as well as described in the above message: https://developer.apple.com/forums/thread/806999?answerId=865783022#865783022 Please @mention me with the Feedback ID once done.

When did you install the TestNet Profile and are you sure it's still valid? The previous profile expired in early February, so you'll need to have updated it recently. Note that you need to install the profile on all the devices involved and that a mixed configuration where the iOS device has the current profile but the HomeHub does not will very likely generate behavior similar to what you're seeing. Here is exactly what is happening: Our device successfully sends a QueryImage command to the HomePod. The HomePod receives it, but immediately fires back a QueryImageResponse that essentially means UpdateNotAvailable, forcing the device into an 86400-second sleep timeout. Chapter 4 of the Apple Matter OTA - User Guide (r6) outlines a number of specific recommendations and guidelines. Are you following all those guidelines, particularly around MinApplicableSoftwareVersion and MaxApplicableSoftwareVersion? Many of our recommendations in these specifications are best understood as requirements, not suggestions. Als

The Apple Developer Forums are for questions about APIs and features intended specifically for developers. Since it sounds like you went to the Apple Support Community already and were sent here because you are running a beta, then you should file a bug report in Feedback Assistant.

Any developer who is adversely affected by the lack of options in UIScene.ConnectionOptions should file a Bug Report about this for consideration. Bug Reporting: How and Why? has tips on creating a successful bug report.

@michelbechelani-aya Yes, if you distribute the app using the Apple Developer Enterprise Program or TestFlight there is no need to resign the app, therefore everything will work on the app. Now the most robust way to handle OAuth/Sign-in flows in automated cloud testing does not need Universal Links entirely for your test builds. Create a specific build configuration for your cloud tests. In this build, configure your app to use a Custom URL scheme for its callback. Configure your staging/testing Auth Server to accept and redirect to this Custom URL scheme instead of the Universal Link (https://...). When the test runner triggers the login, the browser will redirect to myapp-test://, which the OS will route back to your app, regardless of who signed it. Not trying to side track you. Follow your architecture, but I want to make sure to show there are other options. Albert Pascual
  Worldwide Developer Relations.

Hey @Kunal07, Thank you for filing your Bug Report (FB22290781) and including a sample project and a video, however, I'm unable to reproduce this bug. Whenever I was in the immersive space the red cube was there. I tried running the app in the Release and Debug configurations. In the video I see the following: at 00:10, you lock the window and the cube does not disappear. at 00:18, you close the immersive space and the cube disappears with the immersive space. at 00:27, you reopen the immersive space and the cube appears. Your sample app provides a fully immersive space. You are in the immersive space when you no longer see passthrough. It might be more clear if you replace the static Open Immersive Space button with ToggleImmersiveSpaceButton(). Can you do this and reproduce the issue with a video? If you're able to reproduce this, a video and a visionOS Sysdiagnose would be very helpful. Thanks, Michael

@shenbj Thanks for this great post! I think the Claude Agent for Xcode requires an active internet connection to communicate with Anthropic's servers and is not designed for native offline operations at this time. However I think you should file an enhancement request for this. If you'd like us to consider adding the necessary functionality, please file an enhancement request using Feedback Assistant. Once you file the request, please post the FB number here. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why? Resources: https://developer.apple.com/documentation/Xcode/setting-up-coding-intelligence Albert Pascual
  Worldwide Developer Relations.

@eabnelson If my workaround mention above does not work, please do file a bug so the team can fix it for you. 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? Thanks, Albert Pascual
  Worldwide Developer Relations.

Please file a feedback assistant ticket with screen recording and a sysdiagnose log. Thank you How to File Feedback assistant ticket? https://feedbackassistant.apple.com/ Login with your developer account, Choose iOS & iPadOS” Choose AppStore “Incorrect & Unexpected behavior Input the issue description and title. Upload attachements Click “Submit” Copy the Ticket ID “FBxxxxxxx” and let us know. To capture a system diagnose log. https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios

Please file a feedback assistant ticket with screen recording and a sysdiagnose log. Thank you How to File Feedback assistant ticket? https://feedbackassistant.apple.com/ Login with your developer account, Choose iOS & iPadOS” Choose AppStore “Incorrect & Unexpected behavior Input the issue description and title. Upload attachements Click “Submit” Copy the Ticket ID “FBxxxxxxx” and let us know. To capture a system diagnose log. https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios

[quote='881252022, alexfs123, /thread/819160?answerId=881252022#881252022, /profile/alexfs123'] I got a couple of kernel panics while developing a new plugin. [/quote] Kernel panics are always bugworthy. See Bug Reporting: How and Why? for my advice on how to file effective bug reports. And please post your bug number, just for the record. Honestly, I’d be surprised if these kernel panics were caused by FSKit. My experience is that kernel panics are usually caused by other subsystems within the kernel. However, the only way to know for sure is to get a bug on file. As to the behaviour of PassthroughFileSystem, keep in mind that it’s sample code, not a production file system. If you encounter weird problems, it’s worth investigating whether those issues are caused by FSKit or by the sample. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I'm in the middle of the same nightmare. Multiple rejections with no helpful information - very vague. No specifics that would allow me to make the required changes and resubmit. Filed an appeal, which was rejected. Set up a call, was told 3-5 business days, then on business day 4 was told another 3-5 business days. So disappointed in Apple. Can anyone tell me exactly what I need to do to pass review so I can do it and get on with my life?

[quote='881073022, chkpnt, /thread/748447?answerId=881073022#881073022, /profile/chkpnt'] Is this a bug or intentional? [/quote] I’d call it a bug, by my opinion doesn’t matter (-: If this is causing your product significant grief then it’s worth filing a bug about, even if it’s intentional. [quote='881095022, chkpnt, /thread/748447?answerId=881095022#881095022, /profile/chkpnt'] I've filed FB22313288. [/quote] Thanks. It’s been marked as a duplicate of a bug that was filed internally, one that’s definitely with the right folks. I don’t have any info to share beyond that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com