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.

Reacting to Apple’s AppStore Review Terror !

Recently ALL of my releases and updates are REJECTED by the AppStore Review categorically and with questionable (copy&paste reasons). It is a total war and takes over 50 percent of our daily working time, time that is missing for new developments and updates and it is actually quite demotivating.

Here are published some of my responses to the review teams and appeals, as this must be published now because reaching an unacceptable extreme extent already :

( This isn’t just a rant, it’s a desperate attempt at remedial action. )

Ladies and Gentlemen,
I now finally want an answer to my questions.

All of my new apps in the AppStore (including updates), of whatever kind, are categorically rejected for fictitious and untrue reasons.

The requested information material was already attached to the initial transmission. I have been developing Apple software for over 6 years now…

How can that be?

I want an answer to my questions, that this is existential for me and my precious time. Do I pay around 100 euros a year to finance sadistic rejection orgies here?

I am now forced to submit complaints directly to Apple because my appeals are apparently not being heard here and the rejections of the apps are obviously for reasons other than those stated. 

To the concrete subject now. The material on the objectionable points is already in the original transmission:

  • A complete operation manual was attached.
  • A video was attached to demonstrate the software on a real device.
  • (The software does not create connections to any hardware but is an app extension (Apple AudiuoUnit AUv3) So there is nothing to demonstrate in this specific regard.)
  • The workflow has been demonstrated with the transmitted video and corresponds to the descriptions in the manual and the app descriptions.

The reviewer apparently didn’t even bother to review this material.

Since this has now happened several times repeatedly, I will file complaints and pass them on to the Developer Relations Center and possibly all other instances too.

Furthermore I will publish tall those informations now to my customers, as they want an answer why my releases are continuously delayed or rejected.

Jens Güll,
Developer

Ladies and Gentlemen,

One more question: Did you prefer to use anyhow mentally retarded people for the Review processing? ( Excuse me for phrasing it like that, but obviously that’s exactly how I’m being treated by you. ) It is inexplicable to me how such overly stupid questions like this can arise:

  • Who is the target audience? Please be specific
  • How is your app works ?
  • What is the purpose of the app?
  • Is the app for internal use?
  • If users create an account to use your app, are there fees involved?
  • Is this app meant for use in one company or for many client companies?

The material on the objectionable points is already in the original transmission to an excessive extent:

  • A complete operation manual was attached.
  • A video was attached to demonstrate the software on a real device.
  • The kind of app and usage  (app extension Apple AudioUnit AUv3) has been explained to excessive extent.
  • The workflow has been demonstrated with the transmitted video and corresponds to the descriptions in the manual and the product description
  • Our customers (we have over 50 apps of exactly this kind already in the AppStore) do actually KNOW, how to use these app extensions.

The reviewer apparently didn’t even bother to review all this material!

We are apparently being branded here with (hidden?) notices in our account because we always defend ourselves, as this kind of unspecific rejections is happening continuously in the AppStore Review. Otherwise we cannot explain to ourself, how such massive boycott is even possible. And we are obviously being actively prevented from doing our work and releasing new apps in the AppStore. To this to an extent, that can be seen as actively damaging our business and promoting demotivation.

Jens Güll,
Developer