“Popping Sound”

It sounds like you’re making great progress. [quote='879776022, jblum2000, /thread/817268?answerId=879776022#879776022, /profile/jblum2000'] The surprise here is simply that the app worked [/quote] Such is the nature of the Mac. On iOS the trusted execution system would simply block your code from running in this case. That’s much easier to debug. The Mac, with its legacy stretching back 40+ years, has to be more flexible. That has its pros and cons, and you’ve just hit one of the cons )-: [quote='879776022, jblum2000, /thread/817268?answerId=879776022#879776022, /profile/jblum2000'] once I hear back from the employee running this on Sequoia … [/quote] *cross fingers* Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It’s quite hard to read your post. Quinn’s Top Ten DevForums Tips has a bunch of suggestions on how to use the forums effectively, and particularly tip 5. Anyway, it sounds like you are trying to notarise your Mac software and your requests are stuck in the In Progress state. If so, the most likely cause is that it’s been held for “in-depth analysis”. I’ve included my standard explanation of that at the end of this email (although I know you’ve seen it before because of the other threads your pinged about this). In the vast majority of cases this state clears by itself, usually within a couple of days. If you’re still stuck in this state after a week, reply back here with the request UUID and creation date of your oldest stuck request. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. A

Hello, I apologize for the issues you're hitting with Voice Control, these definitely sound like real bugs. When you get a chance, could you please paste the Feedback Report IDs for the bugs you've filed? We are already aware of some of the bugs you've mentioned, but if you can forward the report IDs here, I can ensure we track those as well, so that you are notified when the bugs are fixed in a future release! Thank you for taking the time to report these issues!

What's the best way of being careful about this, or do you just mean by using the item replacement directory where possible? As far as I know, there are only two ways of getting a temp directory: Everything you've described sounds like you're on the right track. The big thing is just not making assumption about the relationship between directories (/tmp/ and home are on the same volume) or capabilities (home directories are ALWAYS on volumes that support cloning). The killer here is the long tail, as there are just SO many different edge cases. LibZip is much faster on a volume that supports cloning Interesting. Are you primarily editing the contents of the zip file (so you end up modifying the data inside, but don't really change it's overall size or structure)? Cloning is a huge help if you can clone the contents and then modify but if your modifications end up changing the fundamental contents, then I wouldn't expect the difference to be nearly as large. At large scale, this eventually devolves to

removing the script didn't fix for me. the script had been holding it together till now, but something changed recently. Ok — since this sounds like a recent change, it would be helpful for us to get a bug report from you so we can look into this further. It would be helpful if you could detail the exact configuration you've set for this build environment (macOS version and Xcode versions), and a link to a specific build. Once that's filed, please post the FB number here so I can locate your report. — Ed Ford,  DTS Engineer

[quote='879236022, ADietz, /thread/817792?answerId=879236022#879236022, /profile/ADietz'] each needs some level of code modification of the app under test? [/quote] No, and yes. The first approach doesn’t require you to modify the app under test because the actual local networking ends up being done by your Mac. However, it’s a lot trickier to set up because it requires you to bring up a non-local server. The second approach is easier to set up but it does require support within the app under test. Hmmm, and that suggests a third approach, which is a variant of the second one but with the proxy running in a completely different app on the test device. For this to work you’d have to ensure that this proxy app runs indefinitely in the background. That’s tricky to do in production — see iOS Background Execution Limits — but you can probably make it work in this just-for-testing scenario. So, something like this: Create an ‘audio streaming’ app that continuously plays silent audio and implements

I am afraid I don't follow your long, winding story. The In-App Purchases and Subscriptions section will appear whenever you create a new software update, provided that you have a subscription group that has not been submitted to review. It sounds to me that you just need to create a new group with different product identifiers. I don't know anything about RevenueCat, though. I don't know why they use it. I would consider making the story concise if I were you.

If I display CallKit immediately after receiving the callback, and then the function returns, but the call ends within 7 seconds, will the second check be considered a misuse? No. The second check is actually validating whether a call has been reported, not whether it's still active. I'll also say that both of the checks here are designed to be more generous than the API contract specifically requires, just to minimize the possibility of any incorrect termination. There were a small number of issues [1] with this code several years ago, but I haven't seen any problems with it since. [1] All of the issues tended to involve fairly odd edge cases/circumstances. For example, there was an issue (fixed in iOS 14) with the exact timing of the secondary check where JUST the right timing between an incoming push and reporting/ending your call could cause the app to crash. Triggering this bug required continually repeating the push -> report call -> end call cycle at a cadence of ~7s for several hours. The bug wa

[quote='818269021, anonymousdev332299, /thread/818269, /profile/anonymousdev332299'] is both a Developer ID certificate and Apple notarization required on current macOS versions? [/quote] Yes. Developer ID signing has been required for a long time (10.8?). Notarisation for apps has been required since 10.14. [quote='818269021, anonymousdev332299, /thread/818269, /profile/anonymousdev332299'] Is [ditto] necessary to properly preserve the app bundle structure and extended attributes? [/quote] Yes and no. If you compress with the Finder then extended attributes get sequestered, which is not good. See Extended Attributes and Zip Archives. The ditto tool doesn’t do that by default. However, in an ideal world this wouldn’t matter because your code signature should not depend on extended attributes. If you find that it does, that suggests your have a bundle structure problem. We talk about this more in TN3126 Inside Code Signing: Hashes and Placing content in a bundle. As to what’s actually happening here, it’s hard

Thanks for chiming in here as well as on the other thread, Kevin! I appreciate the precision and promptness. I believe the only way to do this at the moment is to stream the incoming video like any other video feed while using a PlayAndRecord audio session to capture audio from the user. This is exactly what we switched to trying after I posted. Hats off to the AI bots for being able to help us prototype this approach quickly. Our preliminary results indicate that we will still be able to use some LCK call signaling with this approach, which is nice since we want users to have a native-feeling experience. Once we finalize our approach here I might take you up on submitting a feedback (although tbh I think the watchOS team is getting sick of us submitting demanding Feedbacks).

Unfortunately, on watchOS, the system doesn't seem to treat a video call any differently from an audio call and won't dismiss the system UI once it's answered. Basically... yes, that's what it does. watchOS VoIP support has a very narrow focus, which basically locks the screen into the CallUI in exactly the way you're describing. If you'd like this support to be expanded, please file a bug and post the bug number back here. We would like for our platform to be able to display visual content on the watch's screen during the call – in other words, we would like to be able to treat this as a video call. I believe the only way to do this at the moment is to stream the incoming video like any other video feed while using a PlayAndRecord audio session to capture audio from the user. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

My questions are: What exactly counts as “timely”? You must call reportNewIncomingCall before you return from the PushKit delegate handler. Does CallKit need to be reported within the same run loop, or within a specific time window (for example, within 1 second)? Strictly speaking, what's actually happening is that PKPushRegistry is checking a flag that CallKit sets (basically did report call) as soon as you return from the delegate handler. If that flag isn't set, then it throws an exception, crashing your app. More experienced developers might realize that this is not in fact a secure enforcement mechanism since, with enough work, it seems like it would be possible for an app to disrupt that mechanism. That is in fact true and, in fact, with enough digging, you can actually find the mechanism CallKit uses to notify PushKit of the call. I won't describe the details, but it isn't particularly difficult to spoof that mechanism. That's because the role of this particular crash isn't to formally enforce the requ

Honestly, I’m not sure what’s going on here. None of this sounds at all familiar. I’d like to get a copy of your installer package so that I can poke at it myself. Can you share a link to a download site here? [1] If not, you can file a bug and attach it to your bug report, and then post the bug number here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Posty your link in the clear; see tip 14 in Quinn’s Top Ten DevForums Tips.