dsym file

Is this expected AirPrint behavior for image jobs, or could this be a bug in how iOS constructs the IPP request for photos? Based on your description, it sounds like a bug. Have you filed a bug and, if so, what's the bug number? __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Thanks for the post, this is very interesting, can you provide a little more context about how Xcode marks the string as stale? Screenshots or a way to reproduce it quickly? This is the key you ad adding into your Info.plist? https://developer.apple.com/documentation/BundleResources/Information-Property-List/NSAlarmKitUsageDescription Ensure there are no hidden characters or encoding issues in your InfoPlist.xcstrings file that might confuse Xcode. What happens when you keep it only in the Info.plist? Do you get the same results with just the relevant code in a small test project? 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. Thanks, Albert Pascual
  Worldwide Developer Relations.

[quote='875671022, DTS Engineer, /thread/815033?answerId=875671022#875671022'] Given that you can reproduce this so easily, I recommend that you file a bug about it now. When doing that: Make sure to enable additional VPN logging, per the VPN (Network Extension) instructions on our Bug Reporting > Profiles and Logs page. After reproducing the problem, grab a sysdiagnose and attach it to your bug report. Once you’re done, post your bug number here. My plan is then to grab the crash report from your sysdiagnose log and dig a bit deeper. [/quote] Sounds good, thank you! Filed report: FB21933607 In addition to the sysdiagnose with the VPN logging profile enabled, I also attached a Minimum Failing Example similar to the code sample in the first message.

My app is a Mac app that uses the AppKit framework. It is not a SwiftUI app, nor is it an iOS app. It uses SwiftUI for some views. The sample project code is similar to my code snippet but is built using the SwiftUI design pattern. I want Transaction.updates and Product.SubscriptionInfo.Status.updates to work, but they are not detecting the changes I make when I make purchases, nor are they detecting purchases when using the Xcode Transaction Manager. Also, I use subscriptionStatusTask(for:priority:action:) modifier where I use ProductView and it doesn't work. It is supposed to react in real time. It works if I reload the view by switching to another view and then back. I believe it is less to do with the code and is something else. Maybe the Xcode project file settings is messed up or I am missing something. I tried restarting the Mac and clearing the derived data. Likewise, as I mentioned, it works perfectly in a fresh Xcode project with a minimal setup, but it doesn’t work in my project. Why?

Thanks. I will file multiple feedback assistant tickets as getting documentations and fixing the issues seem to be 2 different topics.

[quote='815274021, ameydalvi_sophos, /thread/815274, /profile/ameydalvi_sophos'] I wanted to know if this is expected behavior. [/quote] Honestly, I’m not sure that matters. What you’re doing is a reasonable composition of existing APIs, and it should work. Given that, I recommend that you file a bug about this. Make sure to include a sysdiagnose log, one taken shortly after reproducing the problem on a Mac with extra NE logging enabled. See VPN (Network Extension) on our Bug Reporting > Profiles and Logs page. 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

Apple’s relationship to ECN is nuanced, largely due to compatibility concerns. If you want to be traumatised, check out the xnu/blob/main/bsd/netinet/tcp_cache.c file in Darwin and the various callsites for that subsystem. So, my answer here depends on where you’re coming from. As a developer, you have APIs that allow you to opt out and opt in to ECN. For Network framework that is the ecnDisabled(_:) modifier [1]. For BSD Sockets there is the TCP_ENABLE_ECN socket option. The system will honour your request to specifically disable ECN, but there’s no guarantee that it will honour a request to enable it. It’s allowed to take other factors into account. That’s why ecnDisabled(_:) is named as it is. Note The name of the socket option doesn’t convey that subtlety. Notably, if you rummage around in Darwin you’ll find a related non-public socket option that better captures this nuance. Both APIs do have a way to determine whether ECN was actually used. For Network framework that’s the ecn property in the T

It looks like your goal here is to file a bug. If so, DevForums isn’t the right place for that. See Bug Reporting: How and Why? for lots of info about Apple’s bug reporting process. If you do file a bug, please post the bug number here, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I certainly don't mean to imply that the causal arrow points from launchd to power state; the opposite, actually! I'm just working to better understand Mac sleep. (And yep, pmset -g is a fun little corner!) The reason I am interested in the precise details of when StartCalendarInterval ends up running a job is that the available resources and limits of a Mac are different in these different power states. I have to code with that in mind. Re:my scheduled job I fear it will cause you fine and patient Apple folk to bristle, as its purpose is to work around Time Machine, uh, changes I have encountered. To wit: Time Machine did not finish backing up because some files were unavailable. Backups will resume when your Mac is unlocked. can be avoided by keeping the Mac awake and unlocked (caffeinate -d) during backup. Time Machine *.sparsebundle disk not ejected properly errors can be prevented by using a script-assisted backup that verifies unmounting prior to sleep. And I can speculate all day about changes

Thanks for the post, I would recommend you to send an enhancement request for that form. 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? Cheers, Albert Pascual
  Worldwide Developer Relations.