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.
Комментариев нет:
Отправить комментарий