Oops, or Why iOS Releases Can Bite the Occasional Weekend iOS Developer.

This is on me, it really is. I don’t install the betas to make sure the few enterprise apps I’ve made don’t break like I should. Hopefully blogging this stuff will make it go a little easier.

During lunch at the real job I decided to download iOS7 on both my iPhone 5 and iPad Retina 4G and test one of the enterprise apps I’ve developed to make sure it still works. After a few annoying “unable to verify” pop-ups due to the shear number of people doing the exact same thing I was doing I finally had the new iOS installed on both devices. Yay.

After messing around on the phone for a bit, because it finished installing first, I turn my attention to the iPad and scroll to the screen that consists of apps I’ve developed as part of various tutorials and for actual pay. I find the icon that looks garish among the minimalism of the iOS apps and touch it.

It launches. Then crashes. Shoot. I reach out to the client to let them know that the little elevator pitch app that I developed is crashing on the operating system that their sales reps are probably downloading right now. I let them know that the first thing I’ll do when I get home is check my crash logs and see what’s what.

I ride the bus home. I try to use another app (not mine) to draw some class diagrams and data model stuff for the app I’m actually going to dev blog. That app crashes. I launch again and use it for the rest of the ride with no issues. I realize that I need to download and install the new xCode too.

Pet the dogs, drop the bag, grab cable and iPad, head to office.

Download xCode, install xCode. Check logs - nothing. Delete app on iPad, rebuild and deploy. No provisioning profile. Odd. Dev Center, make sure all profiles and certs are current. Build again, provisioning profile. Check project and target, that’s weird provisioning profiles are empty but signing identities are still filled in correctly. Update profile entries, build, launches on iPad, crashes with unable to add to process.

Quick stack overflow check, tells me to clean, I clean. Command - r again, iPad asking me if I trust the computer and associated profiles, weird but makes sense. App launches, navigates fine. Try to launch PDF, crash, process id error, that’s weird. A few obsolescence warnings in the logs for a class Note to self: refactor this app.

Try to launch app on iPad, not xCode, works as expected, no errors in log file. Build for archiving, throw it up on local server in old location, delete it off iPad, click link. Installs. Launches. Displays PDFs. Rotates. Let client know immediate issues are solved. Still need to run instruments.

Next up is Spring MVC 3 backend work for new app. Yay.

Previous
Previous

Tomorrow the fun really begins, it'll be Day 0.

Next
Next

Development Blog?