/article/2011/04/27/154625-whereto_ios5_crash_500.jpg?lossy)
iPhone developer FutureTap today noted today that it has received its first crash report from a device running iOS 5.0, suggesting that Apple is testing the operating system with third-party applications.
Just received the first iOS 5.0 crash report. MKUserLocationBreadCrumb sounds interesting.
Future Tap also posted a screenshot of the crash report.
As noted by 9 to 5 Mac, the "MKUserLocationBreadCrumb" API is unsurprisingly related to mapping and location functions, a primary component of FutureTap's Where To? application.
FutureTap and Apple have a bit of an interesting history, with some controversy having arisen last year when an Apple patent application containing a figure that was essentially an uncredited duplication of the Where To? interface surfaced. Apple later clarified that it was not seeking to patent anything related to Where To? and that the figure was for illustrative purposes only, but noted that it would investigate updating the patent application with proper attribution.
Top Rated Comments
(View all)Wouldn't you assume that they are under a NDA for this kind of thing?
No? It's a crash report sent to the developer from an iPhone running iOS 5. They don't actually have the device. I think you misunderstand what actually happened.
Real multitasking without time limits (ala iSSH) would be awesome.
Sorry, but you're not going to get it. I think the way Apple does multi-tasking on mobile devices is great as it saves on battery and RAM requirements. Instead, expect more capabilities for the limited multi-tasking that already exists.
Wouldn't you assume that they are under a NDA for this kind of thing? Seems pretty silly to risk your business to post something like this, or to even take a chance that it could create a problem.
As long as they're not officially on the record saying that they have played around with or seen it in person, I don't see what the problem is.
With all due respect Piggie, your post above demonstrates that you don't understand how iOS multi tasks. In your analogy, it would be more like ...If you employed people, and when you stopped looking at one person they froze in their tracks with whatever they were doing at the time, and only started moving again, when you were looking at them again, you would not call them multitasking :D
But I'm fine with what the iPad does, I just don't like the lies from Apple trying to redefine the accepted meaning of multitasking and them people accepting this new meaning of the term.
If you employed somebody and when you stopped looking at them, they continued to finish the task they were doing, they reported on progress, you could still hear them even though they were out of your field of view and you could look right back at them when you wanted to, and they continued to monitor a source for new instructions... That's multi tasking.
I have no real issue about how it handles task switching, however, as you say the way it handles multitasking is, in effect by not multitasking.
The end result is multi tasking. Apps do not "freeze" completely. Only unnecessary portions of the app freeze. You don't need the app rendering graphics if it's not visible. On the other hand, if an app can play streaming radio in the background while you browse Safari, while at the same time a chat app is sending you push notifications of new messages and a sports app is notifying you of scores in an ongoing game... That is Multitasking.We can argue all day, but apart from the Apple code, and a few bits here and there, the iPad does not multi task, it freezes a program.
That's not multitasking.