How to get iOS auv3 to macosx via catalyst

MacOSX and iOS
1

I have a nicely working auv3 plugin/standalone on iOS.
I want to study the possibility of making it a shared app between iOS & macos. My app is not specifically designed for touch, it just as well works with touchpad/mouse
-In Xcode, I have added the destination “Mac ( designed for ipad)”
-In appstore connect I have enabled “Test iPhone and iPad Apps on Apple Silicon Macs” for internal testing.

Now the app is downloaded fine in macos Testflight, Standalone works fine.
the plugin wont work in Logic, AUval fails with;
FATAL ERROR: OpenAComponent: result: 4097,0x1001

Any hint is welcome!

2

Also: locally with Xcode you can test the iOS auv3 straight in to Catalyst. But it doesnt work either. No readable errors, no hints.
Is there somewhere a list of what you need to set for auv3’s to be compatible for macos catalyst?

3

this is the closest issue/fix I could find, however having trouble finding the things mentioned
https://developer.apple.com/forums/thread/682736

4

Hi Paul, did you finally manage to get it working? I have the same problem. My standalone runs fine, but the plugin version doesn’t open and is not accepted by auval. Martin

5

Don’t know if this is a different approach worth considering, but instead of using Catalyst, why not do a dedicated macOS build instead, and make your app a universal purchase?

That way, you can validate your archive prior to uploading for distribution, and your app will also run on Intel as well as Silicon Macs.

FWIW, that’s what I do with all my iOS / macOS plugins and it works great. There’s a bit of futzing around to do if you’re using Projucer to get the archive through validation, but pretty sure I found all that info right here in the forum.

For me, there were 3 specific issues I had to fix relating to iOS splash screen images, valid icons and dSYM files. The latter also applies to iOS so I guess you know about that one.

The icons that Projucer generates for a macOS app fail the App Store validation, so you need to make those manually - I think so anyway. Happy to be corrected on that.

Also, if you have an image for an iOS launch screen (pretty typical) as an Xcode asset in your Projucer project, you need to manually remove that from your macOS project prior to archiving.

Anyhoo, maybe something worth considering?

Cheers, -Rob (Jackson)

1 Like
6

Hi Rob, thank you very much for sharing your insights!
Currently, we don’t plan to release our iOS apps for Mac.
To record some demos, it would have been easier to use Logic Pro on a Mac. That’s why I had hoped to be able to use it right away via TestFlight and Catalyst.
I will definitely try to make it work natively on Mac in the future and then get back to your hints.