A WARNING (for developers)

If you develop x-platform projects with AudioUnits (AUv3) we want to warn you, updating to Sonoma 14.5 !!!

You will no longer be able to debug and test your apps on the Mac directly, as Apple has broken AudioUnit registration. ( A similar problem still consists on the Apple Vision Pro simulator since appearance, not registering AudioUnits at all – making testing compatibility for this case even impossible. ) The units do not get registered on the machine and will fail to load therefore.

We currently do not know how this will affect users and distributed files via the AppStore. But one just cannot test the Mac compatibility locally anymore.

You have to debug on the real iOS devices explicitly, which complicates everything. It is also not sure, whether this breaks iOS AUv3 units on the Mac in general. We think : PROBABLY YES. And usually such problems do not get fixed by Apple.

( There are some rumours from users, that there are several annoying (extremely delayed) loading problems with some AUv3 ( designed for the iOS platform ) after update, now suddenly not loading correctly anymore. or needing ages to load… )

This problem also applies to all Mac Catalyst apps with embedded audio units, so even specifically compiled apps for the macOS.

Apple promised to run iOS apps seamlessly on the Apple Silicon Macs, which now is no longer the case ( if you even managed to get that working at all due to several inconsistencies with ‘auval’ validation ), especially if you distribute apps with embedded audio units this most likely will result in diverse problems.

Be careful with promises, that the iOS apps and embedded audio units will run on Apple Silicon Macs or that the audio units will be usable with any supporting macOS host application. If the system does not register the components ( technically app extensions ) correctly, no host ever would be able load these AUv3 units, as these are sandboxed and registration is a private system process, out of the focus of a 3rd party developer.

If such extreme problems with Apple platforms continue, we seriously have to think about stopping all development for it, as it consumes endlessly giantly (wasted) time and everything, possibly years of active developments, may be broken the day, Apple releases an update.

Note: At first we thought it is the latest Xcode compiler update (15.4) causing this issue. But this is not the case. I checked twice and it took several hours of research. It is definitively the latest macOS update (14.5), making everything worse, tracing the development efforts with AudioUnits AUv3 to the extreme now.

Fortunately we have updated merely one Mac with this shitload from Apple. So we can continue developing on another machine.

Leave a Reply

Your email address will not be published. Required fields are marked *