file uri scheme

Hi @vision_pro_developer2000 Thanks for bringing this to our attention. While I investigate, I'd appreciate it if you can do some or all of the following: Delete the app, reinstall it, then run it and tell me if the app prompts you for permission to access the main camera. Add some print statements to the app to isolate the point of failure. Tell me how far you get. Specifically, in CameraSessionManager.runCameraFrameProvider determine if the provider starts. In CameraSessionManager.observeCameraFrameUpdates determine if the code reaches leftCameraFeed.update. File a bug report using Feedback Assistant, attach a sysdiagnose, and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating your bug report.

We noticed that com.fidelisendpoint.fidelisevents has an auth_value of 0 and an auth_reason of 5. On any system that has the daemon working, the auth_value is 2 and the auth_reason is 4. Is this to be expected because the toggle isn't working? Yes, that's expected. Laying out the values: auth_value: 0-> Denied 2-> Allowed auth_reason: 4-> the system set this (this was probably because it was done with authorization) 5-> the service’s default policy (I think) Those machines that allow the toggle to stay on do not see this error. Could this be the problem that is causing the toggle to not stay on? Not on its own, but that seems like an odd error. A few points: Have you confirmed that you're NOT seeing this on the system machine where everything works? The error looks concerning, but lots of errors that look bad are actually just noise. When you find an error like this, the thing to look at is what was logged before and after that point, both to see how the system reacted and to look for an underlyin

Thanks for the post. The workflow adheres to the documentation. If the confirmation does not display the correct information, such as: Confirm that the system displays “Notification Triggered” with the message “A notification will be sent to the developer server soon.” To effectively report a bug, it is recommended to submit a screenshot that clearly illustrates the alert and the text you are seeing. Additionally, if you can create a simple, focused project that demonstrates how you are utilizing the API, it would be beneficial. 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.

Could you please file a bug report, include a test project and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating

Thank you for the post and providing a description of the issue encountered when downloading AASA files. Could you kindly provide some examples of these files via a link or multiple links? Then go ahead and file the bug: 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.

Thanks for the post and the idea. You may want to submit an enhancement request to Apple Maps? I would also recommend to read this first: Please review Apple's Unsolicited Idea Submission Policy. Then, you are welcome to submit your idea: 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? Albert Pascual
  Worldwide Developer Relations.

Thank you for your post. When you do not provide your file to play, and you provide the default sound with sound: AlertConfiguration.AlertSound = .default, the sound will now be the default sound.he sound looping until you stop at what time? https://developer.apple.com/documentation/alarmkit/alarmmanager/alarmconfiguration/timer(duration:attributes:stopintent:secondaryintent:sound:) Do you have the time in a focused project with the sound file you are using to share it for people to give you ideas? If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.

Hello @SteveTalkowski ! Thank you for your question. The root cause of your issue is a bit technical so I hope you'll bear with me. You're seeing an issue related to the different ways USD can be rendered on your system. Different renderers support different feature sets of the USD spec and unfortunately RealityKit's USD renderer does not support vertex animation. In some contexts, macOS will display USD files using a renderer called Storm (you can search online for Hydra Storm), and this is not the same renderer used by Xcode or your app, which uses RealityKit to render USD. Because Storm supports vertex animation while RealityKit does not, you'll see your animation playing in some contexts and not others, and you won't be able to use this particular type of animation in a RealityKit app. This is confusing, but hopefully the link above helps explain everything. You've authored your asset correctly! Unfortunately, RealityKit does not support this particular type of animation. I recommend sending us f

Please file a bug report and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating your bug report.

The code was compiled and run on MacOS 15.6.1 The two files are Swift, I had to append a txt to the file name to get them uploaded. NOTE: The example uses NavigationLink for a destination view that takes two (2) arguments. If you have no arguments or one (1) argument, the first time you use the link will not usually exhibit the behavior. You usually need use the back button and navigate again to trigger the behavior. However, with two (2) arguments, the overlay behavior is usually observed on the first try. ContentView.swift.txt BackButtonOverlayApp.swift.txt

This sounds like a regression. Have you tried verifying if the identifiers are still valid when you try to use them again? You can do this by retrieving the assets using the identifier with the fetchAssets(withLocalIdentifiers:options:) method. See the article on Fetching Assets for more details. If the identifiers are valid and you’re still encountering the issue, please file a bug report. Include a minimal reproducible sample code and share the Feedback ID here so I can pass it on to the appropriate engineering team.

Thanks for the post. I believe might be a known bug or at least has been reported and is currently under investigation. Would you be able to assist us by creating a concise and focused project that demonstrates the issue and illustrates how you utilize that API? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Following the utilization of the provided sample, could you kindly submit a bug report and include the specific focused sample in question? 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.