Main Reason Why not to write iOS apps is because Apple Developer’s App Signing Design is a nightmare

December 2nd, 2016

Having been an Apple App Developer for the last 6 months, I have to say the convoluted system that Apple has designed for the signing of Apps is a nightmare.

We constantly get errors like:-

app install failed could not be verified

and after that we are supposed to reboot Xcode, delete “derived data” (which requires command line action) and a number of ridiculous things.

It takes us more time trying to troubleshoot why an app cannot be installed or signed than writing the code.

Even after we have successfully published an App which in Xcode is called “Archive” – yet another counter-intuitive label for something that is better described as “output an IPA” we had troubles installing on our devices through this great App distributor called Installrapp.com.

The whole business of “Provisioning Profiles”, “App IDs”, “Bundle IDs”, Certificate Signing, Ad Hoc Certificates is a nightmare.

To the Apple Development team – Can you please for godsake simplify the whole process of App Signing, Installation on testing devices, publishing, etc? ¬†We have encountered so many problems and we are almost using as much time trying to work out why we can’t install as we are coding. We are using Xcode 7.3.1