Q: GPS data not available to apps after iOS 8.3 update

Update to iOS 8.3 stopped my iPad 4 (WiFi only) connecting to my Garmin Glo. I updated my Garmin Glo software to version 2.7  from Garmin website, and this fixed the problem for connecting it via Bluetooth. Point to note doing this, after update a is that it did not connect right away (box coming up saying 'unable to locate device'). However, wait a few minutes and then you should get a box come up and asking if you want to pair the GLO with the iPad. Clicked 'Pair' and all sorted.

Yes, same thing with iPad 2 XGPS from DUAL on Foreflight and Air Nav Pro and other Navionics software: As of advice from this forum updated the firmware, which was a pain...... because needs a recent Wndows OS which I have not installed on my Mac.............

Result: nothing works, just as before seems to be an IOS 8.3 problem and that cannot be solved by any of us. We cannot even "downdate" to 8.2 which worked just fineGGRR

Who saus if I buy a top ntch receiver for 1000$ which might work with IOS 8.3 this might not happen with the nex IOS "improvement"

Dual Customer Service advised that they are unable to fix Apple's problem and that we will just have to wait for 8.3.1 or 8.4.0 when Apple finally gets around to releasing the repairs.That's 38 days and counting . . .

I Wonder if Apple would be liable if this causes an aviation accident? Maybe they would prioritize the fix if they knew how much risk this problem, is causing?

Considering lots of people fly without iPads your lawsuit would go nowhere.

While the success of a lawsuit might be doubtful, it is hardly good PR.

The marketers of GPS devices that depend on Apple not releasing defective software have suffered an actual financial injury and will continue to suffer for some time to come. But, they could never take on a behemoth the size and power of Apple.

lets just hop Apple have learned something from this and amended their checking processes.

meanwhile we all continue to suffer and 9th April will remain in our memory for a long time to come. I will never forget this betrayal nor the excessive time it is taking to be fixed. They have turned me from a committed fan to an angry dissenter over the last 6 weeks of frustration.

Then vote with your wallet. My understanding is there are devices available from some of the vendors listed in this thread that do not require an iPad. Buy one of those devices and cut out the middleman. That will also send a message to Apple but if EVERY general aviation pilot who is using an iPad did that what percentage of iPads do you think that would be?

Have you signed up for the public beta for iOS 8.4? You can test yourself whether it is fixed and then sign up for 8.5, etc. to be sure this doesn't happen in the future. But I also would question why none of the vendors of these products are included in beta testing.

Have you signed up for the public beta for iOS 8.4? You can test yourself whether it is fixed and then sign up for 8.5, etc. to be sure this doesn't happen in the future. But I also would question why none of the vendors of these products are included in beta testing.

Maybe they did.  Results are proprietary, aren't they.

The simple thing would be to let users select what version of ios they want to use.  It's laziness on Apples parts.  I know of lots of manufactures who have forced the latest and greatest on the customers.  Some have relented and to great appreciation to the users. The bad showing of 8.x would have been a minor annoyance.

What do you think Cook's pilot is using?  Apple let 8.2 available for a long time.  Maybe until Cook's pilot got a chance to downgrade.

Robert

Following me around Robert?

It was a rhetorical question. If you have read through this entire thread you would know that PilotDon was the one who posted the link that included the information that one of the builds of 8.4 resolved this bug. As far as the hardware makers after 8.3 was released if the change that caused the problem was included after the last build (or even during it) they would not be precluded from stating this.

No, it isn't near as simple as you make it. Not signing and supporting previous versions is all part and parcel of Apples security system for iOS, along with sandboxing, no accessible filing system, etc. If you do not agree with the way approaches this (and they are not going to change it) Android does provide some of the means you prefer so I guess you should go that route.

If Mr. Cook used private aircraft I'm certain that a pilot of a Gulfstream would not be relying on an iPad and a GPS unit to fly with. Maybe for Jeppesen charts like airline pilots do but certainly not for navigation. And as far as I know the iPad version of 8.2 is still signed.

8.4 beta 1 & 2 were full of problems and Beta 3 is not available to the public. looks like we have to wait for the release of 8.4 said to be on June 8th. why Apple didn't do a quick fix 8.3.1 is hard to understand.

I Can't remember the last time I had a problem with a windows update.

if mr cook needed a bug fix so he could go flying chances are it would happen. My new aircraft from The Airplane Factory will have Garmin glass and the iPad will drop back to being first reserve, probably. **** of an expensive way to get around a stupid mistake by Apple OpSys developers.

I'm kinda on the Pilot's side here, being a frequent flyer and not being able to see inside the cockpit. But I do think it is a matter of the GPS producers working more closely with Apple re their updates and working these out through the development betas. My favourite part of flying is landing, and preferably at my selected destination!!

Cheers

Pete

I'm on his side too, others have posted here blaming the firmware of the GPS devices but this was definitely an Apple error. But Apple really isn't a part of this market (and this is for General Aviation, not the commercial flights you are taking) which is vertical and extremely small. If it was an error that affected 10% of users Apple might have gone for an 8.3.1 update but as you well know updates can be disruptive and end up with new problems. Or some people thinking they have a new problem. But I would guess this percentage to be less than .01% of all iPad users.

Dumb analogy but to play along is Mr. Cook had a pilot flying his small aircraft, or he was a pilot, he would either have them roll back to 8.2 or use the beta. Did you actually use the Beta 2?

Good idea with the Garmin glass and in the future I would check with your GPS manufacturer before updating your iPad. Let them discover the bug which they should have done in this case.

keep in mind, this bug affects ALL Bluetooth GPS users. Air, land, and sea. This is not just a "general aviation " issue.