GPS data not available to apps after iOS 8.3 update

Unfortunately no such update exists for BadElf or Dual GPS Receivers.

Quite true.

Apple may have made the initial blunder but I do wonder where the auxiliary GPS suppliers were when it was time to test the Beta and thereby compounding Apple's initial mistake. However, when the Betas for 8.4, 8.5 etc hit the deck I bet somebody at the auxiliary GPS suppliers will be having a close look.

I am disappointed with Apple though, for some reason I believed they were better at this stuff than their competitors but it looks like they've been dragged back to the field by their own corner cutting.

Unfortunately no such update exists for [the]Dual GPS Receiver[].

Not yet, anyway. However, we are still early in the finger-pointing stage, and it has yet to be determined where the blame lies. If, as Bad Elf has indicated, Apple has confessed it is an Apple problem which it will correct, I can understand why Bad Elf and Dual are not frantically writing and releasing a firmware update that may have a shelf-life of less than the time it takes to write and distribute it. This is especially true since there are a whole lot of people who think "firmware" has something to do with "male enhancement," and could really brick their units with a botched firmware upgrade. Still, it's funny that Dual has a page which purports to have a link to the latest firmware for the XGPS170, but doesn't.

OTOH, if as others have suggested, the problem is that external GPS makers ignored long-ago published API specs from Apple, shame on them.

Apple may have made the initial blunder but I do wonder where the auxiliary GPS suppliers were when it was time to test the Beta and thereby compounding Apple's initial mistake. However, when the Betas for 8.4, 8.5 etc hit the deck I bet somebody at the auxiliary GPS suppliers will be having a close look.

And if they don't, their users will.

I am disappointed with Apple though, for some reason I believed they were better at this stuff than their competitors but it looks like they've been dragged back to the field by their own corner cutting.

It's still too early in the finger-pointing phase to assess blame. It's a Charlie Foxtrot regardless. However, I share your disappointment with Apple's handling of this issue. No public announcement. No apology. The great stone face. I don't know who their CR counsel is, but s/he ***** had the job.

I also liked how Apple took down a couple of my posts trying to provide guidance for self-help. When it does it sends you and e-mail from noreply@apple and the footer instructs that any e-mail you dare to send to The Wizard in reply will be immediately deleted by a column of cleansing fire. Apparently Apple is a little testy at the suggestion that it may not be infallible, and that it's Apple Community is the only place on the Internet where it's name may be uttered. Of course, there is no one behind the curtain -- it's all done with bots and algorithms. Still, like you, I expected better from Apple.

There is plenty of blame to go around and I have no doubt that this issue will eventually be resolve. But as a consumer who purchased an Apple product, there is a quick short term fix that would solve all of my problems, roll back to iOS 8.2. Unfortunately Apple has taken that option away from me, so as far as I am concerned it's mainly on them.

I am sorry I must have missed something, but what exactly is this simple fix? It can't be reloading a previous version of the iOS since Apple discontinue signing versions older then 8.3 and as of 13:59 est today Carlos Moniz from Dual reported that they are still waiting on Apple for a fix to the bug.

I am sorry I must have missed something, but what exactly is this simple fix?

Download and install the latest device software for:
the XGPS150 and the XGPS160.

There is no question that the initial problem was created by Apple and that the proper fix will come from them in 8.4

Apple delete posts that say that so this one may not last too long. The reason given for the deletion was that I was quoting Apple from the developers forum.

The fix being suggested at the moment is a classic band-aid and not the long term proper fix. Still, any port in a storm, I guess.

I'lol have a look at the Dual site and see what they recommend.

thanks for the tip.

Went flying yesterday and tested various external GPS devices with Skydemon:

Bad Elf Pro + worked fine (Bluetooth).

Bad Elf iPad Plug-in worked fine.

Garmin GLO: Immediate Bluetooth connection but took a while to show a location; thereafter, however, it worked fine. The software version for this was their latest (2.7). It was also working fine with the earlier GLO software ............ until I installed IOS8.3 uplift, after which it simply refused to show location data. However, now that I have updated the software (thank you again to the poster who suggested that I use a VERY short USB lead when my PC refused to "see" my GLO when connected via the Garmin-supplied USB lead; thereafter the software download was easy).

RESULT:

Bad Elf Pro + (Bluetooth) software worked fine without any updates, although the Bad Elf Pro + is very new and should therefore already have the latest software release.

Bad Elf Plug In - doesn't use Bluetooth so no problems.

Garmin GLO (Bluetooth): Updating to the latest Garmin software version cured the problem introduced by IOS8.3.

CONCLUSION

Not a laboratory test, but there are the facts to make of what you will. For myself, I cannot help but conclude that, whilst Apple may have inadvertently caused the problem, device manufactures can resolve it via a software update.

Thanks AeroSteve.

Unfortunately, none of the suggestions above has helped get my XGPS160 working with my iPad and OzRunways.

There is still nothing on the Dual site and when I check the firmware it says it is Ver 1.3.5 and when I ask to check for update it instantly reports that it is "up to date".

Apple admits to bug in GPS for iOS 8.3. Scroll down to "notes and known issues" under MFI GPS.

https://developer.apple.com/library/prerelease/ios/releasenotes/General/RN-iOSSD K-8.4/index.html

Many thanks AeroSteve for doing the research. I updated my Garmin Glo to version 2.7 as suggested and this fixed the problem for connecting to iPad 4 via Bluetooth. Point to note for others trying this 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.

For all readers, update to iOS 8.3 stopped my iPad 4 (non-WiFi), 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 and switching back on, 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!

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.