Doesnt all this issue - and the basic fact that Apple has dragged its heels for over a decade about properly supporting AudioUnits on iOS - suggest that it really might be worth ROLI reconsidering its position of only supporting Apple official API’s in the JUCE Framework?
AudioBus - clearly even now - is way in front of what AUv3 can deliver. And there’s the non-apple API Ableton-Link as well - firmly established in the iOS music-making world - and elsewhere too.
So surely - bearing in mind JUCE is intended for AUDIO software developers - surely - it makes sense - and helps us developers - if ROLI’s JUCE team put work into supporting both AudioBus3 and Ableton-Link now ?
Better to support the leading-edge of what is now possible on the leading platforms instead of Apple’s trailing-edge - reminiscent of the “Please sir” scene in Oliver Twist!