After a lot of trials and errors I unlocked a very different situation which in turn unlocked this very specific one.

As of today, it now works by adding the Audio Unit extension to a Swift project. There’s a new hurdle to clear every day.

And then, he came back from the future with the solution: enabled hardened runtime set to FALSE in the build settings. Funnily this setting was set to TRUE by default on a new Audio Unit Extension project using the official Xcode template. Life throws you curveballs.

To any Apple Dev out there, it seems that I miss some bridge somewhere so that the AppIcon reaches the extension. Maybe in the bundle? Maybe in the build settings? Do I have to include the xassets file as well in the extension? Thank you in advance for your help!

In case someone is looking for an answer I created a small Swift project to list all Auv3 Plugins + icons. But basically once loaded you can get the icon using something like: component.icon A little contribution to the community because sometimes easy things can become soooo hard... CC @Clevername47

On my side I could not even reach that point. I can't get any icon to show in an AUv3 host app.

Any news?

It seems I can get the icon to show in Xcode by adding this to the .pbxproj under the extension config: ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon; However the icon still does not show on any host. I guess I have some missing parameters in the Build Settings of the extension. What asset related entries should I have in the extension build settings for the icon?

From the doc: In iOS, a custom Action extension uses a template image version of its containing app’s icon, which you must provide. iOS Share extensions automatically employ the containing app’s icon. If you provide a separate icon in your Share extension target, Xcode ignores it. For all other app extension types, you must provide an icon that matches the containing app’s icon. I'm using the AppIcon from my .xcassets file in my containing app. So why doesn't it show in the extension?

In the end he decided not to use the official AUv3 template and went another way, digging knowledge from various places on The Internet. He remembered that the journey is more important than the destination before starting yet another project in XCode.

Checking the iPad logs, I can find the cert problem: error 13:14:40.593566+0200 filecoordinationd sandboxing denied subscription to progress on category (bundle id (null), ) error 13:14:40.776767+0200 trustd SecKeyVerifySignature failed: Error Domain=NSOSStatusErrorDomain Code=-50 "rsa_pub_crypt failed, ccerr=-7" UserInfo={numberOfErrorsDeep=0, NSDescription=rsa_pub_crypt failed, ccerr=-7} error 13:14:40.819992+0200 lsd Installation failed for error 13:14:40.827517+0200 atc LaunchServices observer: Apps Failed be installed:

Just tried on another iPad: same problem.

I started a simple swift project and it's working fine. No problem to export to iPad. So I guess there's some problem with some setting somewhere in the AUv3 template

I started another project using the AUv3 template and in fact I get the exact same problem: I can build and install the extension however I can build the host app but can't install on the iPad with the same error.