First things first: I have a Mac. I can use it to actually do the testing on the devices. But, it's gotten fairly slow, and is such a pain to use as a result, that I would rather develop the bulk of my application on my Linux desktop.
пятница, 10 февраля 2012 г.
четверг, 19 января 2012 г.
Finding iOS 5 bugs: Where do we even start?
What could be causing the problem? Where do we begin to diagnose an iOS 5 bug?
First, don’t even bother reading through your code to look for anything suspicious. You won’t find anything. After all, you verified that the problem doesn’t occur on an older version of iOS. Under certain circumstances, you can say, “This code works.” There isn’t anything obviously wrong. So what’s going on?
Remember that we’re writing against an elaborate framework, relying on iOS to invoke our methods. With each new release of iOS, Apple isn’t just adding features; they’re also trying to improve battery life. If they find any call sequences they can eliminate, they’ll do it. But sometimes, this means an inefficiency you used to rely on may have been removed, causing one of your methods to no longer be invoked, or invoked in a slightly different order.
First, don’t even bother reading through your code to look for anything suspicious. You won’t find anything. After all, you verified that the problem doesn’t occur on an older version of iOS. Under certain circumstances, you can say, “This code works.” There isn’t anything obviously wrong. So what’s going on?
Remember that we’re writing against an elaborate framework, relying on iOS to invoke our methods. With each new release of iOS, Apple isn’t just adding features; they’re also trying to improve battery life. If they find any call sequences they can eliminate, they’ll do it. But sometimes, this means an inefficiency you used to rely on may have been removed, causing one of your methods to no longer be invoked, or invoked in a slightly different order.
iOS 5 Bug! How to Track It Down
A bug report is filed. It has these ominous words: iOS 5 bug. Dun-dun-duuun. What do you do?
Twice now, this has happened to me at work. Here’s a technique I’ve used to find and fix the problems. It’s served me well!
First, fire up Xcode 4 and see if you can reproduce the iOS 5 bug in the iPhone 5.0 Simulator (or the iPad 5.0 Simulator, depending on your app). If you can get it to happen in the simulator, it makes life that much easier, because we’ll be switching back-and-forth between iOS versions.
Now rerun the scenario in the iOS 4.3 Simulator. Can you verify that the bug doesn’t occur there? Then we’re in business. You have a genuine iOS 5 bug!
Twice now, this has happened to me at work. Here’s a technique I’ve used to find and fix the problems. It’s served me well!
First, fire up Xcode 4 and see if you can reproduce the iOS 5 bug in the iPhone 5.0 Simulator (or the iPad 5.0 Simulator, depending on your app). If you can get it to happen in the simulator, it makes life that much easier, because we’ll be switching back-and-forth between iOS versions.
Now rerun the scenario in the iOS 4.3 Simulator. Can you verify that the bug doesn’t occur there? Then we’re in business. You have a genuine iOS 5 bug!
Sandox broken
Here are some news about the current work on the A5 research.
@planetbeing escaped from the sandbox with the help of @saurik. Thanks to their awesome work, there should be nothing left blocking for the A5 jailbreak.
Now it should be a matter of days. Still no precise ETA of course.
We all want this to be finished ASAP, we're getting tired!
@planetbeing escaped from the sandbox with the help of @saurik. Thanks to their awesome work, there should be nothing left blocking for the A5 jailbreak.
Now it should be a matter of days. Still no precise ETA of course.
We all want this to be finished ASAP, we're getting tired!
Target audience
Developers working with mobile technology. There will be talks targeted at a specific platform and talks of a more platform independent nature. We welcome independent developers, freelancers and developers working for a company – It doesn’t matter who you are or where you work, if you work with mobile technology you’ll enjoy this conference.
Deadline information
Competition closes March 3rd 2012 at 00:00 GMT, The winner will be notified within 24hours of the closing date and time via twitter.
Enjoyed this post?
Then why not subscribe to our RSS feed, follow us on twitter or use the buttons below to share with your friends and colleagues in one simple click.
Deadline information
Competition closes March 3rd 2012 at 00:00 GMT, The winner will be notified within 24hours of the closing date and time via twitter.
Enjoyed this post?
Then why not subscribe to our RSS feed, follow us on twitter or use the buttons below to share with your friends and colleagues in one simple click.
Win a ticket to MDevCon on March 10, 2012 (Amsterdam)
About the event
The conference is by mobile developers, for mobile developers. It’s 2 tracks, designed in such a way that whether you’re an android, ios or other mobile platform developer, there’s always at least one session that should be of interest.
There will be speakers such as Mike Lee, Graham Lee, Jeff LaMarche and Matt Gemmell. The venue is epic, it’s the 1920?s classic Tuschinski Theater in Amsterdam. By there is more info on the site, but the schedule will only be revealed once they have processed the Call for Papers.
The conference is by mobile developers, for mobile developers. It’s 2 tracks, designed in such a way that whether you’re an android, ios or other mobile platform developer, there’s always at least one session that should be of interest.
There will be speakers such as Mike Lee, Graham Lee, Jeff LaMarche and Matt Gemmell. The venue is epic, it’s the 1920?s classic Tuschinski Theater in Amsterdam. By there is more info on the site, but the schedule will only be revealed once they have processed the Call for Papers.
Подписаться на:
Комментарии (Atom)