AU plugins on iOs
Ok so heres a bit of a generalised q...
Do need to do anything special to my AU plug-in to it works on the iPad? - apart from all the Ui changes to make sure it works "nice" with touch based ifaces I mean...
Has anyone done much of this - any gotchas? any thing I should do/avoid?
d.healey last edited by
@Lindon I assume an app certificate thingy is required from Apple.
@d-healey oh yeah all that malarky....
Christoph Hart last edited by
Yeah, developing on iOS is the worst.
My top 5 problems:
- Can't load AU plugins that use more than 350MB in total (so three instances with 150MB each blow up the iPad). This restriction was lifted with iOS 12 fortunately, but back when I did serious iOS development, it was a real killer for any sample-based stuff.
- Can't create .ipa archives for testing with sizes > 4GB. Doesn't complain, doesn't say what's wrong, just doesn't work.
- Can't test the InApp purchases without actually making a contract and supplying a valid bank account - again, no error reporting, just returns
falsewithout any indication
- Sometimes the metadata in image files prevent compilation. You need to add a pre-build step that strips the metadata (sometimes, but then it works again)
And there's many more, so if you're not super fluent in iOS development and Apple's company policy of being as annoying as possible, then you'll need plenty of patience...
@Christoph-Hart wow this so doesnt sound like me.....