dsym file

Hi! Claude Agent in Xcode uses a specific config.json file, different from a global json file you might have been using with a previous Claude Code installation. For Claude Agent, this would be located in this directory: ~/Library/Developer/Xcode/CodingAssistant/ClaudeAgentConfig You can find more information on our documentation Let me know if this works!

When I tried to create the bug in new project, I found the solution.. First, I added .windowStyle(.hiddenTitleBar) to the WindowGroup in my main app file. It prepares the window to be borderless before the system even draws it. Standard applicationDidFinishLaunching logic was running too early for me. The OS was still setting up its default gray style and overwriting my code. I used a tiny timer to force my settings once the window is actually alive. func applicationDidFinishLaunching(_ notification: Notification) { // I used a 0.1s timer to catch the window AFTER the OS finishes its default setup Timer.scheduledTimer(withTimeInterval: 0.1, repeats: true) { timer in if let window = NSApplication.shared.windows.first { self.setupWindow(window) timer.invalidate() } } } Then re-apply the transparency and separator settings in the windowDidBecomeKey delegate method to stop the focus pop. func windowDidBecomeKey(_ notification: Notification) { guard let window = notification.object as? NSWindow else { ret

Thanks for the post and thanks for the patience. Thank you for providing your app details and suggesting an efficient way to reproduce the issue. Using your existing App Store build is a great approach since all entitlements and deep linking configurations are already configured. Please include the APP ID in the bug. What I want from the team is an answer if AASA files allow none unicode URLs and with your code showing what you are trying to do will help get across to all the teams involved. In the focused sample, ddd your team’s App ID to your App Association File (AASA) so we can build and run your app directly. Looking forward to get to a resolution on this issue. Albert Pascual
  Worldwide Developer Relations.

Please file a Feedback report using Feedback Assistant, then post the Feedback ID here.

Thank you for your post. If you disagree with the outcome of the review, we recommend submitting an appeal to the App Review Board. When filing your appeal, make sure to: Provide specific reasons why you believe your app complies with the App Review Guidelines. Submit only one appeal per rejection. Respond to any requests for additional information when submitting an appeal. Once you have submitted the appeal we can escalate it to the App Review Board for review. The App Review Board will contact you directly as soon as they've completed their investigation.

Hi Travis, I’ve filed a Feedback Assistant report with a focused test project attached that reproduces the issue. Feedback ID: FB21893762 https://feedbackassistant.apple.com/feedback/21893762 Thanks again for taking a look. Best regards, Yassin

Hello patatrouf, Thank you for all of the additional investigation. If you'd like to be automatically notified via Feedback Assistant, you can always file a bug report and I'll make sure it issues you updates accordingly. Hello Moff, Thanks for filing your bug report! I've made sure to route it to the right team. Glad to be working together, Richard Yeh  Developer Technical Support

I believe you filed a bug asking about this earlier, and I have my own bug on this (r.169737319). It fell off my radar for a bit, but I've asked the team for some guidance on the right way to handle this today. Following up on myself after talking with the team, here is how I would suggest handling this: In the first call to UserProcessBundledParallelTasks, you should: Store the OSAction you receive into your DEXTs own ivars. Intentionally retain() that OSAction. This retain will NOT be balanced, so you're intentionally over-retaining the OSAction (it will be destroyed when your DEXT is). You can actually retain it a few times if you want. On all future calls to UserProcessBundledParallelTasks, assert that the OSAction you receive is the same as the action you received in #1, intentionally crashing if it changes. Note that the point of #3 is NOT to detect a valid state you should anticipate or handle. It's purely there as an overall safety check that will either never trigger or will trigger years fr

Hello @stopthatnoise Can you share that new project with me to investigate? 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. If this is a bug, you can file a bug report here and attach the project there, and I will escalate as needed. Feel free to file now and reply with the FB number in this thread, so we can get a head start on the investigation.  Travis Trotto - DTS Engineer

Hello @yassinfromcolombes Are you able to create a focused test project that runs and demonstrates the issue? If possible, I would like you to file a bug report and attach the test project as an attachment. Reply with the FB number and I will be able to investigate with the relevant engineering team accordingly. If you're not familiar with preparing a test project, take a look at Creating a test project. Thanks!  Travis Trotto - DTS Engineer

Even in Xcode 26.3 (Xcode 26.3 Release Candidate Apple silicon.xip) from 2026/Feb/03 the DDI Files for ios 26.x are still missing. No one can work for weeks now. Well done.