“Popping Sound”

I had the same issue. I managed to workaround this by enabling background audio in the app's capability settings. See also: https://developer.apple.com/forums/thread/799104

I had the same issue. I managed to workaround this by enabling background audio in the app's capability settings.

It sounds like you tested it on iOS. I understand that some developers refresh Transaction.currentEntitlements when the iOS app switches to the foreground. Yes, I do handle Transaction.unfinished and it is not related to my issue. Have you seen this post by @saxmanbob? He had a similar issue to mine, but he resolved it due to some “Objective-C machinery”. I don’t use Objective-C in my app, although it may exist within some Swift packages. Please try the following and let me know if you get the same result. Download the CotEditor Xcode project, copy and paste the InAppPurchaseManager code somewhere appropriate and launch it in applicationDidFinishLaunching(_:). Locate the CotEditor.storekit file and change the Subscription Renewal Rate to Any Renewal Every 10 Seconds or Any Renewal Every 2 Seconds. Run the app and observe the console. You will see that it does not behave as expected. You could also try this in a fresh AppKit Xcode project. You don’t need to build the UI and you will see that it works

Thanks Ed for the reply! I guess the reason for the question is that it seems a little strange to have some intents as AppIntents and others in the (older) SiriKit / IntentExtension framework, as opposed to having them all as AppIntents. Ideally I'd like to get rid of the IntentsExtension if possible, but it sounds like that's something that's intentional from Apple's perspective. Is that true, or are there plans to bring them all over as AppIntents at some point in the future?

You're looking in the right place with WWDC24 videos, but you may have missed Bring your app to Siri, which is where we go into this. For functionality that fits with the SiriKit domains, you should continue to use those SiriKit intents within the domains for calling and messaging. For any other intents you may have outside of those domains, you can migrate those to App Intents, which it sounds like you've done, so it sounds like you're completely on the right path. I hope that helps! — Ed Ford,  DTS Engineer

@brian-bcny your script works great for clicking the pop-ups. However, when I try and run it, even as a LaunchAgent, I am faced with another pop-up to allow osascript access to System Events. How are you getting around this?

Hello JoshyMW, This sounds like a serious enough issue to merit a bug report via Feedback Assistant. Can you please open one, and attach your code snippet in the form of a test project, plus any screenshots or documentation you may have? 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? Thanks for letting us know, Richard Yeh  Developer Technical Support

Dear s_petrovskiy2, Just for clarification, can you please answer: By mirroring, you mean that the external device would be displaying identical content to what is on your iPhone, correct? Are you using storyboards, and defining your scenes in your Info.plist? If so, then you would not need to handle scene:willConnectToSession:options: for the default configuration of your root view controller main device screen. (If you are loading it programmatically, you would need to, as seen in Tech Note TN3187: Migrating to the UIKit scene-based life cycle; but since your window has already been created, it sounds like you are using the Info.plist method. In which UIWindowSceneDelegate delegate method are you seeing a second scene created? When does it take place during your app's operation? After connecting to the AirPlay receiver (your MacBook)? How are you initiating an AirPlay connection with your app- are you using the built-in Screen Mirroring button in iOS? Please let me know, Richard Yeh  Developer Tec

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

[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.

It sounds like you’re trying to use Developer ID signing for day-to-day development. That’s something I recommend you avoid. Rather, use an Apple Development signing identity for development. For background on this, The Care and Feeding of Developer ID. Having said that, I can help you debug this specific problem. I recommend that you start out by isolating this from Xcode. If you run these commands, what do you see: % cp /usr/bin/true MyTrue % codesign -s Developer ID Application -f MyTrue Run these from Terminal, logged into the same GUI login session as you’re using for Xcode. If that prints a no identity found message, what do you see when you run this command: % security find-identity -p codesigning Policy: Code Signing Matching identities … 11) ADC03B244F4C1018384DCAFFC920F26136F6B59B Developer ID Application: Quinn Quinn (SKMME9E2Y8) (CSSMERR_TP_CERT_EXPIRED) 12) 3F8BE319780F84EB2E94ABDFA24E8045A0572A7B Developer ID Application: Quinn Quinn (SKMME9E2Y8) 12 identities found Valid identities onl