...and who's to say that they didn't report back to Apple?
Again, there is no information saying that they haven't or won't do that. I simply stated that, with the official launch of iOS6 and the iPhone 5, that they probably have had their hands full. Time will tell either way.
I'm not saying they didn't, I'm asking where it's noted if they did. Did they made their users aware of the known issue and their being aware of it and thus to expect issues until either Apple addresses some concern or they the 3P company make arrangements ot deal with another mapping company such as Google.
I would think they would notify you somehow, otherwise you and others using their apps are left in the dark. Based on the replies and information thus far, they have not done that and instead continue to keep their users in the dark and their app for sale knowing it won't work properly, in which case, that's just as bad as what you claim Apple has done. Perhaps you cut them a break for having their hands full. I'm sure Apple has their hands full too yet no breaks for them eh? What's funny is Run Keeper still shows images of their product integrated with Google Maps.
That you want to remove focus from Apple, who have already admitted they have crappy maps, and place it on the developers who had fully functioning apps before hand and were promised the same or better maps, is laughable.
It's not laughable. They had access to the developers kit and iOS6. IF they base their product on the same talk and marketing users did in that it's the same or better vs the actual usage and development working with the product, that's what's laughable. There's every bit the reason to point to a 3P developer for being responsible that your stuff purchased from them isn't working. Again, didn't they test the final product or work with the new maps at all?
For them, it's only been released for a few weeks and, even if they had a few months warning, major modifications and the following testing can take time. Apple has had years to buy, build and develop and they still dropped the ball.
I'm sure they've had the development kit for more than a few weeks or at the very least knew of the changes and concerns from no doubt at lease June. I say June only because that's when the concerns started popping up here on this board. I'm sure they knew even earlier. Regardless for them them not to post in their release notes that such issues were to be expected, then shame on them just the same as Apple for not telling you.
I didn't say all the threads, I pointed out this one. You're "in before" comment is what started (yet another) debate which could be found in numerous other threads and once again shows that you're here looking for an argument, nothing more.
My in before comment was very accurate as this topic comes up in every related thread you're in brought up by you. I just happen to get here first. It's not me looking for an argument, again, this is very relevant information. If you can blame Apple, it's also very fair the 3P companies you keep implying are victims be exposed just the same. It's called bringing out other aspects not yet mentioned. If you want to call that an argument, that's up to you.
Last edited: