dsym file

Our app attempts to install a PDF workflow in ~/Library/PDF Services, but on a clean install of newer macOS versions, that directory no longer exists. Please file a bug on this and then post the bug number back here. It won't change anything about your immediate situation[1], but the nature of the sandbox environment means that we should probably be more aware of the broader consequences this kind of directory removal can have. Attempting to create the folder requires prompting for user permission to access the ~/Library directory and then prompting the user to access the newly created ~/Library/PDF Services directory. This is annoying and awkward. ... We would like to create both directories in one step. So, in terms of direct creation, I can see a few options that should work. If you present a save panel that targets ~/Library/PDF Services, then you should be able to directly create the folder in one pass. That flow is a little weird/awkward since you'll need to force the user to approve that exact

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to this thread. Bug Reporting: How and Why? has tips on creating your bug report.

I won't believe this is an intentional change. Do you have a feedback report yet? If not, would you mind to file one and share your report ID here? Thanks. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Hello jaysack, Sorry for not following up on the additional info provided. The inconsistent behavior across two identical iPhones that @Regadas reported does sound like a bug. If you're seeing this issue as well, please file a bug report so our engineering team can investigate it in full. Do include device model, iOS version, and if possible, a focused test sample app that reproduces the issue. Once you open the bug report, please post the FB number here for our reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Filing a bug report will allow Feedback Assistant to notify you if and when the bug gets fixed. That is the case even if it is a duplicate of an existing known issue. If anyone else in this thread is experiencing this USSD dialer issue, please don't hesitate to file a report as well. Once again, we apologize for not replying sooner to this thread. For future reference, it's generally advisable to post replies r

I need to clarify a bunch of things, but before I do that I want to point you at Quinn’s Top Ten DevForums Tips, and specifically: Tip 5 — This explains how to format your post to make it easier to read. Tip 7 — This helps head off follow-up questions (like the ones below). So, my questions: This is macOS, right? Is this a regression? Or are you seeing this problem on a wide range of macOS versions? Have you tried it on the most recent macOS 26.3 beta seed? How reproducible is this? Once it occurs, how long does it persist? Does it go away if the provider exits? Or if you start and stop it? Or if you restart the machine? If this is a regression, have you file a bug about it already? If so, what was the bug number? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hello, Richard! Thank you for your attention for this problem. I attached the screenshot of the launch screen (the brightest rectangle is covering the logo), the LaunchScreen.storyboard file and the template used to generate. Please, tell me if you need anything else. With regards, Illia [files removed at poster's request]

Hi Kevin, As per our tester, he explicitly ensured that the app was force-closed at the end of the day. However, as you correctly pointed out, the logs indicate that the app was never actually terminated by the system—it was moved to the background and then resumed the next morning. The challenge we are facing is that certain functionality does not behave correctly when the app resumes the next day without a normal cold start. The primary issue is with the SLM (Sound Level Meter) framework, which relies on audio sessions. In these resumed states, the audio session is not always reinitialized cleanly, causing our calibration process to fail and leading to the core issue we observed. To address this, we implemented a controlled, app-initiated exit in such scenarios to ensure the app always starts in a clean state. This approach resolved the issue successfully. More recently, we encountered a case where we did not even receive the applicationDidEnterBackground callback. We extended the same force-exit handling t

Thanks for the updated posts. [quote='873386022, Leo_Nagano, /thread/812857?answerId=873386022#873386022, /profile/Leo_Nagano'] legacy dns-proxy entitlement [value] [/quote] To be clear, this isn’t a legacy value. This value is used for App Store distribution, both on iOS and macOS. It’s also used for development. The -systemextension suffix is used for direct distribution using Developer ID signing. Neither value is more legacy than the other. As to what’s going wrong, you’ve tried a lot of different things and it’s hard to be sure what’s what at this state. However, this is problematic: NSExtensionPointIdentifier com.apple.system_extension.network_extension And it suggests that you could do with some high-level guidance. The best place to get that is Xcode. Consider this sequence: In Xcode 26.2, create a new project from macOS > App template. In my case I named it “Test812857”. Then create a new target within that project, using the macOS > System Extension > Network Extension template. In my case

Sorry to hear the issue, which seems to me a regression in 26.2. Do you have a feedback report yet? If not, would you mind to file one and share the report ID? To make the feedback report more actionable, please install the CoreDevice logging profile to your Mac, iPhone, and Apple Watch, and also the sysdiagnose profile for watchOS to your Apple Watch, then follow the instructions at the latter link to capture the co-sysdiagnose, and attach it to your feedback report. Thanks! Best, —— Ziqiao Chen  Worldwide Developer Relations.

Hello Allen, Thanks for filing the crash report with the full crash log. Just to confirm, are you overriding viewWillTransitionToSize:withTransitionCoordinator:, and if so, can you please provide the relevant code in the method? Thank you for your patience, Richard Yeh  Developer Technical Support

Hello a.mclaughlin, As far as I know, AVAssetDownloadURLSession is the only available API to cache HLS playback- as per the AVURLAsset .assetCache property, The value of this property is nil if you haven’t configured the asset to store or access media data from disk. - meaning HLS video is not cached by default. One hacky workaround you can try is to set AVPlayer.actionAtItemEnd to .pause, then automatically seek back to 0 when it reaches the end. Have you tried any other video formats to see if they support soft subtitles in iOS? Do your HLS video subtitles use the AVMediaSelectionGroup and AVMediaSelectionOption classes covered in the Selecting subtitles and alternative audio tracks guide? Some subtitle formats AVFoundation supports include WebVTT, iTT (iTunes Timed Text), and others, in .mov and .mp4 files. Thank you for your patience, Richard Yeh  Developer Technical Support

If your project is affected by any of the issues described above, please consider filing a bug report. Duplicate bug reports are useful in the sense that it allows engineering to understand how many people's projects are affected by a problem. So, don't worry about filing duplicate bug reports. If you file a bug report, please reference this thread in the bug report and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to this thread. Bug Reporting: How and Why? has tips on creating your bug report.

If this behavior is still observed in the latest iOS or iPadOS version 26.2 please file a bug report about this. Bug Reporting: How and Why? has tips on creating a successful bug report.

Thanks for the post, love you selected emoji! This a great post for developers to provide their opinion on how they will handle that situation. In my modest opinion I would make sure the framework is build for external use and reference in the project as an external framework, if the code is part of the project, you can just include the file you want instead of using it as a framework. Otherwise just build the framework and use it as you would be using an external framework. Ensure that the framework search path includes the directory containing your framework bundle. You typically want to point to the or directory inside . Alternatively, use which automatically points to the correct build directory depending on the scheme (Debug/Release). If your framework is custom and part of the same project, ensure it's added to the Link Binary With Libraries phase of your app target. Consider copying the framework into the app bundle if needed by setting up a Copy Files build phase. If your framework a