dsym file

Thank for the post, I’m not int that team at all nor I have inside information, Im just looking at the eligibility rules. According to the requirements, the project must run on either Swift Playgrounds 4.6 or Xcode 26, or later. Since Swift Playgrounds looks like doesn’t support building .metal shader files the same way Xcode does, it seems like you could technically meet the requirements by only running the project in Xcode. From: https://developer.apple.com/swift-student-challenge/eligibility/ “Your app playground must be built with and run on Swift Playground 4.6 or Xcode 26” OR is the key word here. Hope this helps, you can also sent that question to that team as they have an email address on their page. Albert Pascual
  Worldwide Developer Relations.

Hi, Sorry to hear you are having trouble using previews. A few things you could try: Run xcrun simctl --set previews list to see the list of previews sims. Perhaps you'll see the UUID list there Similarly if you wanted to delete all the previews sims run xcrun simctl --set previews delete all If you are still seeing issues we'd suggest filing a feedback report We will need the diagnostics Xcode Previews generates in order to help us understand the error the previews system is encountering. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an erro

I ran the following commands in Terminal: cp /System/Library/CoreServices/Finder.app/Contents/Resources/Invitation.aiff ~/Downloads/Invitation.aiff xattr ~/Downloads/Invitation.aiff chflags -v 0 ~/Downloads/Invitation.aiff xattr ~/Downloads/Invitation.aiff but the output of each of these commands was empty, so again it seems that even with the chflags -v 0 Invitation.aiff command no extended attributes are revealed on that file. I tried copying the same System/Library/CoreServices/Finder.app/Contents/Resources/Invitation.aiff file to a FAT volume connected via SMB, and the results are the same. I'm afraid we'll never know how that file (and hundreds others) got to the SMB volume. The user told me they're currently unable to reproduce the issue and are tired of running experiments, so I guess that's it for now... until I'll hear from the next user having the same issue. I have lost count of how many users have already contacted me about the exact same issue and how many days I've alr

Hello, Richard! Here are the files you asked for: Screenshot Files Also, please, remove the post with the files as there is a sensitive information inside one of them. With regards, Illia

[quote='874764022, TotalPhase, /thread/814226?answerId=874764022#874764022, /profile/TotalPhase'] We haven't setup a VM yet. [/quote] I strongly recommend that you do. It has some key benefits: It strictly constrains the problem space. For example, if you have a bug with identifying the correct broadcast interface [1], such a problem will go away in a VM because there’s only one interface. So, if the local network alert always shows up in a VM but fails on real hardware, it’s likely that this isn’t an issue with local network privacy per se, but something in your code. It makes it much easier to run tests in isolation. You can quickly iterate on your tests, creating a new clone of your ‘clean’ VM each time. It allows you to test across OS releases. If you think something broke in, say, macOS 26.2, you can easily test 26.1, 26.2, and 26.3 beta, all in parallel. Debugging these problems on real hardware just makes things harder. [quote='874764022, TotalPhase, /thread/814226?answerId=874764022#874764022, /profil

[quote='874797022, Xunreal75, /thread/814501?answerId=874797022#874797022, /profile/Xunreal75'] I find this termination behavior too aggressive [/quote] My role here on the forums is to help developers create products for Apple platforms as they currently stand. If you’d like to see things change in this space, you are free to file a bug report [1] describing what you’d like to see change. See my Bug Reporting: How and Why? post for more details about that process. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Or enhancement request. In cases like this the distinction is one of perspective.

Well, that’s bad. In general, removing an app should remove all the bits associated with the app, and if that’s not happening then it’s clearly a bug, and I recommend that you file it as such 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

Oh - one other possible factor: the files are Locked in the Finder, to prevent edits. They've been on a disk for over a year, unchanged, as far as I know.

Sorry for late response. Thanks for your comment and I have 1 additional inquiry. Related to the topic which I posted, I have a question regarding the behavior of Numbers.app, which is provided by Apple. In Numbers.app, it will track the file which opened previously has moved to another location and open it. And also when that file has been deleted, it will close along with the following message. [Spreadsheet Deleted. This spreadsheet was deleted in another location] Questions: 1.How Numbers.app achiveing these behaviors? 2.Can a 3rd party like our company be able to achieve this kind of behavior?

Hello fdika24, UITabBarItem's title and image not applying the same tint color sounds like an issue worth filing a Bug Report for. Please take your example code and put it in a small runnable Xcode project that replicates this issue. 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? Thank you for your patience, Richard Yeh  Developer Technical Support

Hello sarveshb, Thanks for the screenshots documenting this issue, and the sample code. This issue may be related to scroll edge effect. Can you please file a bug report so we can have a relevant engineering team further investigate this? 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? Thank you for your patience, Richard Yeh  Developer Technical Support

Hello, To further investigate this, please file a bug report using Feedback Assistant. It is crucial that you securely attach screenshots of the purchase dialog showing the incorrect email, as well as screenshots from your device's Settings > App Store screen showing both the Media & Purchases and the Sandbox Account sections. Additionally, you can follow the instructions on the Bug Reporting - Profiles and Logs page to capture and attach a sysdiagnose log immediately after reproducing the issue. Once submitted, please share the Feedback ID (e.g., FB12345678) here to track the report.

Thank you for the detailed information. To investigate this behavior thoroughly, could you please file a report using Feedback Assistant and include a sysdiagnose log? Part 1 How to File the Feedback Report Navigate to Feedback Assistant and log in with your Apple Developer account. Choose iOS & iPadOS for the product. For the report details, please include the detailed description and steps to reproduce from your post as well as the sysdiagnose. Part 2 Capture and Attach sysdiagnose Go to the Bug Reporting - Profiles and Logs page. Follow the instructions to install the necessary profiles for App Store issues. Once the profiles are installed, reproduce the purchase issue in your app and capture the sysdiagnose. Attach the resulting log file to your Feedback Assistant ticket. Part 3 Share the Feedback ID After you submit the report, please share the Feedback ID here to find your report and track its progress.