Hi Gary / All,
As reported previously, I did have a connectivity problem with my iPad mini 5 on Saturday evening.
After updating my pad to iPadOS14, I tried it with my spare Rosetta - newly updated to PAW 20200906 - and with the latest SD Beta 3.14.3.258, which I had received from SkyDemon via Apple TestFlight last Wednesday.
The iPad connected to the PAW WiFi straight away and all the PAW Screens (including PAW Radar and METARs) were available via 192.168.1.1. I then checked the SD Third Part Device Settings - Set to PilotAware only. Clicked on ‘Go Flying - Use PilotAware’ and SD just hung on ‘Connecting to Device’.
After leaving it for quite a while, I ‘Stopped Navigation’ and went back to check my PAW ‘Device Connect’ setting - which was set to ‘All’.
Back to SD Third Party Devices again and added ‘FLARM with Air Connect’ (without removing the PilotAware option). This brought up the Air Connect Key ‘1234’, which traditionally always had to be ‘reset’ to ‘6000’ for PAW, but I decided to leave it at ‘1234’ to ‘see what happens’. I then selected ‘Go Flying - Use FLARM with Air Connect’ - SD immediately showed a new Banner (at least new to me) - ‘Authenticating’ then ‘Seeking GPS Satellites’ then went to its normal display screen with my Ownship, local Ground Station (now shown as a mast) and local ADSB Traffic displayed.
On Sunday morning, I decided to retry using the PAW setting only, which surprisingly now worked as normal. I then re-added the Third Party Device Options for ‘FLARM with Air Connect’, ‘uAvionix SkyEcho2’ (which I don’t have) and ‘GDL90 Compatible Device’ and found that all of these also connected to PilotAware and displayed traffic.
I have since had a direct e-mail exchange with Tim Dawson (under my ‘SD Testflight’ hat), which confirmed that SD Beta 3.14.3.258 - which I had been using up to Saturday Night, was subsequently released as the new 3.14.3 Public Release (with the same version number), though in light of my experience outlined above, I find it difficult to believe that nothing has changed between my receiving the Beta last Wednesday and the final Public Release over the weekend - especially as the ‘fix’ to deal with iOS 14’s new ‘local network permissions’ was reportedly incorporated in the previous SD Beta 3.14.3.257 issued on 8th September. If that was so, why did I still experience the connectivity issue on Saturday Evening running the final beta for the upcoming 3.14.3.258 Public Release?
For the avoidance of doubt, I have tried it again today, with only the PilotAware option set in SD Third Party Devices and SD connected straight away as intended.
There is, however, obviously still something weird going on, as most of you were previously reporting that SD 3.14.2 was connecting fine to iPhones on iOS 13.7 even when your iPads weren’t - and now, since the update to iOS 14 / iPadOS 14, the opposite seems to be the case!
Hopefully SD will get to the bottom of it soon, but I suggest keep reporting specific occurrences to them on the SD Forum. There is a specific ‘iOS 14’ thread in forums.skydemon.aero/Topic32191-2.aspx
Regards
Peter