Are you planning to travel internationally and want to unlock your iPhone? This post explains steps related to unlocking an iPhone 4S using the United States carrier, Verizon. It may also work for Android phones on the service, but my experience is with the iPhone. The process takes between 10 and 20 minutes to complete. Be sure to read the “Once you arrive” steps so you are able to finish the process.
Before you get started
You should be aware of restrictions Verizon puts on device unlocks. Some but not all of this was covered in a Venturebeat article.
- Your account must be in good standing. i.e. you can not owe them money.
- They say that your account must have been in good standing for at least 6 months, but I do not believe they enforce this rule.
- You may only unlock one device per phone number every 10 months.
Unlock your iPhone with Verizon
- While still in the United States, dial *611 from your iPhone. Continue reading Unlocking a Verizon iPhone 4S for International Travel
As I build upon my understanding of Objective-C, I’ve been working to better understand the concept of a delegate and when they should be used. In searching for clarity, I came upon an explanation by Mark Hernandez the administrator of iPhoneDevForums.com.
For posterity, I’ve copied Mark’s explanation here. For his full explanation and his code example, follow the link above.
My favorite way to explain how delegates work involves animals.
Let’s say you are going to create a particular bird. You start with a predefined class definition of a bird (provided in the existing framework as, say, CFBird). The existing framework class assumes all birds have certain things in common — they hatch and grow the same, poop the same, fly the same, and lay eggs the same way, etc. (tee hee, I said poop. ) But different birds look different, are different sizes, chirp differently, eat different things, and may mate differently. Continue reading iOS / Objective-C App Delegates Explained Using Birds
I’ve been experimenting with a multiview iPhone / iOS app with a tab-based navigation and came across an error and solution for “unrecognized selector sent to instance.”
In one of the tab’s views I had a standard button with a Touch Up Inside event that I had connected to a buttonClicked method in the view’s controller. For some reason, when I tapped that button the app would crash. This was not happening when I built the same stuff in a single view app.
I went searching and was happy to find that the problem was well described and solved in the developer forums of MacNN. It turns out that when you have have multiple view controllers for separate .xib files being controlled by a Tab Bar Controller you need to take an extra step of setting the Class Identity for that particular view. Here’s how: Continue reading Fix for Terminating App Due to Uncaught Exception 'NSInvalidArgumentException'