DTiPhoneSimulatorErrorDomain Code 2

How are you cloning these VMs? Specifically, are you calling Virtualization framework from your own code? Or is your infrastructure relying on VM infrastructure provided by another third party? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='811013021, pjfloyd, /thread/811013, /profile/pjfloyd'] On macOS I see an extra mutex. [/quote] That doesn’t surprise me, but that’s probably the result of my not understanding your setup properly. When I run your cond_timedwait_test.c code natively and set a breakpoint on pthread_mutex_lock, I hit that breakpoint a lot inside the dynamic linker and various loaded-by-default libraries. But I suspect that you’re doing stuff to avoid that, like statically linking the executable [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Not something we support in general but tools like this often have to stray from the supported path.

The general model for apply(_:completionHandler:), as explained in the docs, involves three steps: Apply the Wi-Fi configuration. Join the network. Bring up the TCP/IP stack on that interface. Problems with step 1 are delivered to your app via the method’s completion handler. Problems with step 2 are communicated to the user via an alert. Problems with step 3 can result in a variety of different behaviours. If you’re seeing a case where the devices fails to join the network and that’s not reported to the app or the user, that’s something we should investigate via a bug report. See this post for my advice on filing Wi-Fi bugs. If you do file any bugs about this, 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

My general advice here is to avoid Multipeer Connectivity, and instead focus your efforts on Network framework. TN3151 Choosing the right networking API talks about this more, and I have specific guidance in Moving from Multipeer Connectivity to Network Framework. [quote='869271022, PellePepper, /thread/11964?answerId=869271022#869271022, /profile/PellePepper'] Connection is lost or cannot be established again. [/quote] One key issue with Multipeer Connectivity is that it’s tricky to separate link-layer issues — that is, problems with peer-to-peer Wi-Fi — from transport layer issues. That makes investigating problems like this a lot harder than it is with Network framework, which makes a clear distinction between the two. [quote='869271022, PellePepper, /thread/11964?answerId=869271022#869271022, /profile/PellePepper'] Is there a possibility to connect two iOS-Devices via cable-connection to improve stability? [/quote] Yep, just use Ethernet, along with two USB Ethernet dongles, whi

I agree with red_menace that you don’t want to be using a custom icon for this. That’s super brittle. If you using Script Editor to save a new application, it has already set up all the bits you need: % plutil -p Test811273.app/Contents/Info.plist { … CFBundleIconFile => applet CFBundleIconName => applet … } % file Test811273.app/Contents/Resources/applet.icns Test811273.app/Contents/Resources/applet.icns: Mac OS X icon… % file Test811273.app/Contents/Resources/Assets.car Test811273.app/Contents/Resources/Assets.car: Mac OS X bill of materials (BOM) file To get the right icon, replace applet.icns with your own: % cp /Applications/Pages.app/Contents/Resources/AppIcon.icns Test811273.app/Contents/Resources/applet.icns % rm Test811273.app/Contents/Resources/Assets.car After doing this, zip and unzip the app so that the Finder refreshes. Now, in this case I nixed the Assets.car entirely, so that macOS falls back to applet.icns. A better way to do it would be to use Xcode to build a dummy app with the right

There are two ways you could interpret that error: Focus on the “valid Developer ID certificate” part. Focus on the “The binary is not signed” part. My experience is that the latter interpretation is more helpful. That is, there’s nothing wrong with your Developer ID certificate but rather there’s something wrong with your packaging that’s preventing the notary service from verifying its code signature. Having said that, this is a strange: [quote='811481021, AbsurdFish, /thread/811481, /profile/AbsurdFish'] Re-tested with minimal test package - same error persists [/quote] How are you creating this minimal test? With Xcode? Here’s the diagnostic test I recommend: Create a new test project in Xcode, using the macOS > App template. Choose Product > Archive. In the Xcode organiser, click Distribute App and follow the Custom > Direct Distribution > Export path. That produces a folder containing your app binary. Use ditto to create a zip archive from that, as explained in Packaging Ma

What ssmith_c said plus… com.apple.developer.system-extension.install is a restricted entitlement, that is, one that must be authorised by a provisioning profile. If you were using Xcode, it would take care of this for you. Given that you’re not, you have to do this by hand. There are a bunch of resources to help you with this: Creating distribution-signed code for macOS has general info about that. TN3125 Inside Code Signing: Provisioning Profiles has background on how provisioning profiles work. Resolving Trusted Execution Problems has a ‘child’ post that explains how to debug issues like this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Sadly, I can’t read Chinese, so I’m answering based on a machine translation. The code you posted assumes that a specific interface type will have a specific interface name. That’s not a valid assumption. BSD interface names are not considered API on Apple platforms. I have a lot more information about this in the various posts referenced by Extra-ordinary Networking. Please read them through. If you have follow-up questions, I’d be happy to answer them here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='810499021, ArcticSentinel, /thread/810499, /profile/ArcticSentinel'] My goal would be to create a content filtering app for all users [/quote] On what platform? I initially thought you were talking about iOS, but the fact that you mentioned “all users” suggests that you might be targeting macOS. As TN3134 Network Extension provider deployment explains, the rules here are very different between the two. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='810133021, anilaygun, /thread/810133, /profile/anilaygun'] Is this a problem? [/quote] I suspect that your confused by the various identifies in play here. Specifically, your Team ID, your User ID, your Team Member ID, and your app’s App ID prefix are all identifiers with the 10-character format, but they’re all different things. So, for example, your Team ID is not supposed to match your User ID. For more on this stuff, see Code Signing Identifiers Explained. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I have had an app on review since December 26th, it never went into Review. I ended up removing the build and resubmitting. I am on a couple days again with no Review. Prior, one of my apps had two approved updates within a day. Maybe they are still back logged or I am lost in the system :/

[quote='810603021, AamirNezam, /thread/810603, /profile/AamirNezam'] we are facing an issue with the certificate validation [/quote] Can you provide more context here? Certificate validation is used in a lot of different places — Safair, networking APIs, code signing, push notifications, and so on — and so it’s not clear where I should route your question here on the Apple Developer Forums (or, indeed, whether it’d be better routed elsewhere, like Apple Support Community, run by Apple Support). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I have a bunch of info about how to investigate such problems in Resolving Trusted Execution Problems. The two most useful in your case are: syspolicy_check Dangling load command paths I recommend that you start there and, if that doesn’t help, start at the top. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com