“file uri scheme”

Hi, Thank you for the follow-up and for confirming the AASA multi-App ID support, that is a useful detail. Just to make sure we fully understand the recommendation: are you suggesting we add the testing platform's Team ID + Bundle ID to our AASA file so that their re-signed build is also a trusted app for our domain? If so, we want to understand the security implications of listing a third-party signing identity in our AASA file before going down that path. Regarding TestFlight, we are already using it for manual pre-release testing and it works well for that purpose. Our challenge is specifically with automated UI testing in a cloud device farm, where TestFlight distribution is not part of the workflow. We also wanted to ask about a hybrid distribution approach we are considering, and whether it is permitted under Apple's terms: Use the Apple Developer Enterprise Program to distribute the app internally to our cloud-based testing infrastructure, allowing their re-signing process to work und

Since I have already ruled out SwiftUI lifecycle interference and simulator limitations, are there specific logging categories in Console.app or internal ExternalAccessory states you recommend I monitor to diagnose why the connection is failing? There isn't a lot that can go wrong from the app side, assuming your app is properly configured and functional. As one more confirmation test, I would suggest testing with the old EADemo sample. The code is fairly old, but you should still be able to get it working without too much effort. If that's failing, then that's pretty strong evidence that it's either a bug in the system or a problem with the accessory. Has your accessory passed certification? And have you ever been able to work with the ExternalAccessory framework/app? Finally, have you filed a bug on this and, if so, what's the bug number? __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Thanks so much for the reply and the detailed information. Yes, looks like the resigning will cause the issue you have described. I still recommend you to test against your devices to make sure the AASA file get downloaded and works well before sending the build to the App Store. You are correct that we do not offer a native provisioning flag to bypass AASA validation. Apple’s AASA file specification fully supports listing multiple App IDs (Team ID + Bundle ID) for a single domain. You can also use TestFlight to distribute your app to test devices. Wish you luck. Looking forward to your app. Albert Pascual
  Worldwide Developer Relations.

If you end up filing a bug please post the FB number here for our records. Bug Reporting: How and Why? has tips on creating your bug report. Albert Pascual
  Worldwide Developer Relations.

Could you also file a feedback assistant bug report with a sudo sysdiagnose, and xcrun simctl diagnose to help our analysis? thank you!

Thanks for the detailed response! To answer your questions: OAuth - I don't see a pattern other than time. It seems to lose the OAuth token 2 or 3 times per day. It also doesn't seem to depend on idle time. I can be in the middle of working and it will lose the token. Yes, especially since thinking can go off the rails or go into a nearly-endless loop, this serves as a way to monitor and guide agent progress. I did file a feedback on all the issues, btw! (FB22310171 on the whole set of issues, and I also just filed FB22316631 per your request on this specific one.) Next time this occurs, I will attach it to the Feedback report. No, I have never downloaded or setup Codex. I especially want to highlight the additional bug I reported in my Feedback report but did not post here -- the agent will take action even if I specifically tell it to ask for approval before proceding. This is concerning because there is now some internal state where the agent believes it has gotten permission even though

Thanks for filing the feedback report (FB22310365). It seems to be a known issue that is under the investigation of the SwiftData folks. Best, —— Ziqiao Chen  Worldwide Developer Relations.

First, thank you for taking the time to post these. We really love hearing from our developers because this helps us make the tools better. Re: OAuth — hmm, OK we're investigating. Is there any pattern to this? Do you see this after a certain amount of time? Re: Thinking — interesting, this is good feedback about how you're using thinking as progress tracking. We know about the issue where you can't open the popover until the thinking is done. But, sounds like you really want a don't put thinking in a bubble entirely because that's part of your tracking of the agent progress. Makes sense. It'd be great if you could file a feedback request specifically for this. Re: Slowness to start — yeah, I agree that sounds weird. The only way we have to debug this at the moment is if you attach the contents of your conversation via the Bug button at the bottom of the transcript. Re: Codex & Claude showing — Have you downloaded both agents using the Intelligence settings even if you haven't logged in? We suppo

Thanks for your post. This is interesting. 🧐 Do you mind filing a report using Feedback Assistant that I can share with the relevant engineering team? Share as much details as you can about affected platforms and versions. I would love to know if this started happening with a specific update or has always been there. As for workarounds, you can try handling the animation directly instead of letting it be handled implicitly or under the hood. For example, you can disable the animation entirely with .animation(.none, value: sectionExpanded) or create your own custom Section with a dropdown and animating content. You can also build the sidebar content in AppKit and display it with SwiftUI using NSViewControllerRepresentable Once complete, reply with the FB number below. Thank you.  Travis

@sleeper-luke Thanks for the link to this thread. As previously please file a 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.

Apple folks can't comment future plans based on the company's policy. I'd say that your ask is best handled as a feedback report for HealthKit. Do you have a feedback report yet? If not, I’d suggest that you file one and share your report ID here. Thanks. Best, —— Ziqiao Chen  Worldwide Developer Relations.

@frmoraess App Store Crash? This is new to me. But that should be handled by the App Store team. I would recommend you to open a bug for the App Store team to take a look at: 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. I don’t think you have provided much information to be able to help you. Can you provide a focused sample of how you use App Clips? Are you using Xcode, can you create a new sample project that reproduces the issue using the steps below? App Clips are built as a separate target within your existing iOS app project. Open your project in Xcode. Go to File > New > Target. Select App Clip under the iOS tab. Name your App Clip and ensure it is embedded in your main application target. App Clips rely heavily on Universal Links to securely verify the relationship between your website and your app. Add the Associated Domains capability to both your main app target and your App Clip target. Add your domain using the appclips: prefix. Example: appclips:example.com Update the apple-app-site-association (AASA) file on your web server to include an appclips dictionary. { appclips: { apps: [..Clip] } } Please follow this great documentation: https://developer.apple.com/design/hu

Finally I found the problem. In the entitlements file, I had 2 entries iCloud Container Identifier iCloud Services with an empty array of values. These must have been left over from previous edits. After removing the above entries, building completes without any error. 😉

I've filed FB22313288.