That feeling when building and testing on android device takes you 5 mins and then you spend 2 days dealing with Apple's bullshit.

Sexy devices and pretty interfaces but they just looove making devs jump through hoops.

It's to keep the eco system safer. I know it's a pain in the hoop but I actually moved my trust from android to apple after signing up as an apple developer.

I love the way apple still release new iOS versions for older devices so I can test on the latest iOS on my iPad Air. Android/Samsung doesn't particularly have more than one major is update per flagship device

@philcr I know it's worth it in the end, but the whole process is so painful :(

Wait until you need to automate the build with scripts.... xcodebuild is a pain to get working properly.

Good luck, it gets better once you understand certificates, app identifier, device ID and provisioning profil, and how they work together.

Basically, certificate is your identity, you need one for development, and one for distribution. You need it installed on KeyChain for signing to work.

Device IDs are the obvious, the UDID of devices you want to test on.

App identifier identify the app, and its permission (in-app, push notifs ...)

Then, the most import, provisionning profile allow to sign an app with specified certificates, on specified device (or Store if it's distribution) for a specific app identifier ! You need that configured in your app.