4 ms·

Almost all my mobile development experience(of which there isnt much to start with) has been acquired via PhoneGap, meaning i only did native if absolutely nece

Almost all my mobile development experience(of which there isnt much to start with) has been acquired via PhoneGap, meaning i only did native if absolutely necessary. The biggest issue and something that has gotten me into a state of white-hot rage has been Apples certificate/provisioning profile nonsense. I don't think I've ever gotten a profile to work from the get go, even just for development(a requirement thats positively ludicrous). That's why I generally develop/test on Android first. Seriously, I've managed to require a whole week just because of some certificate snafu.

mathieuh 13y ago
I just keep trying some combination of deleting and adding new certificates until it starts working. Most of the time I'm unable to tell the difference between what wasn't working and what for seem reason has begun working.
eddieroger 13y ago
I agree that the certificate and profile thing is confusing when you are getting going, but I think a lot of that was exacerbated by not using the native toolset. Xcode handles a lot of it for you (with more and better support coming in Xcode 5), and point you in the right direction for things you have to do alone. Plus, there is loads of help on the 'net about doing this stuff in Xcode because everyone has to, whereas PhoneGap's user base is lower, so less out there. I wouldn't say it's overly complex, but it is by no means simple.
matwood 13y ago
Using XCode will probably fix all your issues for development. For a build server look around for a ruby script that can pull down the provisioning profiles on every build. Very useful.
bennyg 13y ago
This is my certificate/profiling debugging workflow - most of which Xcode does for you, btw: 1. Is your certificate expired? Yes - renew it obviously. 2. Is your provisioning profile a wildcard (com.company.*) or specific to an identifier (com.company.id)? If it's specific to an id, and your app isn't using that id change it to use it or use the wildcard provisioning profile (really just do this anyways). 3. Does the provisioning profile list your Certificate under Teams? If not, make a new provisioning profile that is wildcard and lists the dev certificate under Teams. 4. Does your provisioning profile have the device you're trying to build to listed under it? If no move on. 4a. Is your device added to the Portal? Do this through Xcode's Organizer, there's a little plus button to add to the provisioning portal. If yes, move on. 4b. Edit the provisioning profile to also account for your device (use the checkboxes), download the new version of the profile and add it back to Xcode. Voila! You should be free to build to your device.

mathieuh 13y ago

I just keep trying some combination of deleting and adding new certificates until it starts working. Most of the time I'm unable to tell the difference between what wasn't working and what for seem reason has begun working.

eddieroger 13y ago

I agree that the certificate and profile thing is confusing when you are getting going, but I think a lot of that was exacerbated by not using the native toolset. Xcode handles a lot of it for you (with more and better support coming in Xcode 5), and point you in the right direction for things you have to do alone. Plus, there is loads of help on the 'net about doing this stuff in Xcode because everyone has to, whereas PhoneGap's user base is lower, so less out there. I wouldn't say it's overly complex, but it is by no means simple.

matwood 13y ago

Using XCode will probably fix all your issues for development. For a build server look around for a ruby script that can pull down the provisioning profiles on every build. Very useful.

bennyg 13y ago

This is my certificate/profiling debugging workflow - most of which Xcode does for you, btw: 1. Is your certificate expired? Yes - renew it obviously. 2. Is your provisioning profile a wildcard (com.company.*) or specific to an identifier (com.company.id)? If it's specific to an id, and your app isn't using that id change it to use it or use the wildcard provisioning profile (really just do this anyways). 3. Does the provisioning profile list your Certificate under Teams? If not, make a new provisioning profile that is wildcard and lists the dev certificate under Teams. 4. Does your provisioning profile have the device you're trying to build to listed under it? If no move on. 4a. Is your device added to the Portal? Do this through Xcode's Organizer, there's a little plus button to add to the provisioning portal. If yes, move on. 4b. Edit the provisioning profile to also account for your device (use the checkboxes), download the new version of the profile and add it back to Xcode. Voila! You should be free to build to your device.