We have tested both EasyVFR 3 and 4 on the latest iOS 14 beta version, and running these apps we haven't found any problems at this time. However, when you are using an external device to receive traffic, GPS, routes, weather or data from a flight simulator, a new type of privacy permission is now required. Below you will find the workaround.
For the rest, EasyVFR runs fine on iOS 14 as far as we can now tell, though there may still be changes in the final (Golden Master) version.

If you rely on your iPhone and/or iPad for flight planning and navigation with EasyVFR, it might be a good idea to disable automatic updating of iOS on those devices temporarily, so to prevent nasty surprises just before take-off.

If you find any other issues using one of our products with iOS 14, please contact us so we can investigate and fix it for you.
Our email address is [email protected] or leave a message via the button "Need a hand?" at the right bottom corner on this page.

Blue skies,
The EasyVFR 4 Team


Turn automatic iOS updates off.

Turning that automatic update off, for now, is quite easy to do. Tap Settings, General and on the right-hand side tap Software Update. At the bottom of the page there's an option which allows you to turn automatic updates off. You can always switch it back on in the same way.


Set permission to connect to a device via a local network.

This is required reading for everyone who connects to external devices using wifi, e.g. to receive Traffic data, GPS, Routes and Weather such as SkyEcho 2, Stratus, Dynon SkyView,  FLARM, or xConn, XMapsy and so on.

While testing EasyVFR 3 and 4 combined with iOS 14 beta we discovered that iOS 14 does not automatically display the "Find and connect to devices on your local network" pop-up. Obviously, we will release an updated version of EasyVFR so that question will pop-up automatically. Until then, we have found a workaround so you can trigger the permission yourself.

When an app listens over the UDP protocol nothing happens. But as soon as you let it listen over the TCP protocol, iOS 14 shows the "Find and connect to devices on your local network" pop-up where the user can give his permission. In EasyVFR we can use this as a workaround to trigger that permission pop-up.

Workaround for EasyVFR 4.

  1. Connect the device that runs EasyVFR 4 to the local wifi network of your external data sending device.
  2. Go to EasyVFR 4 menu -> System -> Electronic Conspicuity Settings -> FLARM ButterFly/AirConnect.
  3. Enable "Monitor for FLARM equipment".
  4. Tap [Yes] in the first pop-up. Tap [OK] in the second pop-up.
  5. Disable "Monitor for FLARM equipment" again.
  6. Done! Now you can receive data via a local network.

Once the permission is given, the apps should be listed in the iOS local network settings: iOS/ macOS Settings > Privacy > Local Network.


Workaround for EasyVFR 3.

  1. Find the IP address of the device that is the host of the local network, typically a router. Most of the time it is the local wifi network's IP address ending in a 1, something like : 192.168.xxx.1
  2. With EasyVFR 3 go to Menu > Nav Tools -> Settings -> FLARM Settings.
  3. Enable "Use FLARM" and enable "FLARM GPS as EasyVFR GPS".
  4. At "WiFly IP Address:" set the IP address from step one.
  5. Make sure that "Used protocol" is set to "TCP".
  6. Tap [GO]. Then tap [Back].
  7. Tap in the pop-up at [OK].
  8. Now you can disable the "FLARM settings" again.

Once the permission is given, the apps should be listed in the iOS local network settings: iOS/ macOS Settings > Privacy > Local Network.