Hey MrTVR;
I know this doesn't answer your question directly, but I have a lot of experience with iPads, Autopilot, Map Pilot and DJI (Go, Go 4 and GS Pro apps). I use Autopilot for automated video missions for construction clients, and I use Map Pilot for mapping missions, so I feel obligated to give some advice.
The thing I absolutely can't stand about iPads, DJI, Autopilot and Map Pilot is that NONE of these products offer any form of exit strategy. They deploy "updates" and (god forbid) "upgrades" without fully fully testing them, leaving you, the user, to do their bidding for them. So my work flow is pretty simple; Don't upgrade/update ANYTHING unless you have to. This includes iPads (I still use my Air 1), iOS, apps, firmware and on and on. I use legacy firmware and software until they become unusable...OR unless a feature is released that I deem worth the risk of an upgrade. For example...
As you're probably well aware, Map Pilot just started supporting inside polygons in v4.0.5. THIS was a carrot for me. Until a week ago, I was running v2.9.2 with no complaints. But, as me and my business partner often need inside polygons, v4.0.5 was a carrot. So I allowed v4.0.5 to install on my iPad. Sure enough, it is now possible to build inside polygons! Awesome! However, what the nice folks at Map Pilot FAILED to mention in their release notes was that they REMOVED the ability to save the Flights.plist file. For me, this was a HUGE inconvenience. A deal breaker. Often times I can have a dozen or so missions for any given job. With v2.9.2 I can save ALL these missions as a single file which can be either imported INTO or exported OUT OF Map Pilot. In v4.0.5, not so much. With v2.9.2 I can literally reload a dozen missions into any iPad in the field in seconds.
Well, apparently the developers of Map Pilot don't consider this to be a very useful feature, and have thereby REMOVED access to the Flights.plist file. So my work-around is to build inside polygons in v4.0.5, then AirDrop the missions to my other iPad running v2.9.2, and then save the Flights.plist file to my Google Drive, which then propagates out to all 5 of my computers, including my field laptop. If anything should happen to my iPads, it takes literally seconds to upload the missions to my partner's iPads and we're good to go.
This is just one of DOZENS of examples of DJI, Map Pilot, Autopilot, and/or Apple pulling the rug out from under me. The cure is to HACK everything. I save .ipa files so that I can roll back ANY of my apps.
To facilitate this, I have to run a legacy version of iTunes on all my computers:
Unfortunately, legacy iTunes only works up to iOS v12.1.xx. So for my new Gen 3 iPad running iOS v12.3.1, I use a program called iMazing, which facilitates access to the file structure.
But because I'm running MP v4.0.5, the Flights.plist file does nothing in the above photo. I imported it into MP v4.0.5 just to see if it would populate the missions, but it does not. If I want to repopulate the Gen 3 iPad with missions, I have to do it via Air Drop one mission at a time (in the field). At home I can do a massive export/import of .mme files, but this isn't by design. This is a hack.
I've discussed this HUGE shortcoming with the support staff at Map Pilot. According to them, I'm the only mapper on the planet who deems the ability to export, save and import the Flights.plist files "useful." His defense is that the .mme files can be saved, which is fine for jobs with 5 missions. But a PITA for large jobs with 2, 3 or 4 dozen missions.
At any rate, I think you get the idea of what I'm saying here. If it ain't broke, don't fix it. DJI, Apple, Map Pilot and Autopilot will NOT be forthcoming in their release notes. They will remove vital features and functions without so much as a hint to the end user. They will dangle feature carrots in front of the user's face with their right hand while they stick it to you with their left.
To make things worse, your average schlub has no exit strategy. So he/she is STUCK with whatever bugs and/or shortcomings Apple, DJI or Map Pilot force down their throat.
And don't bother asking Map Pilot support for legacy .ipa files. They'll all but deny that they even exist, citing that "Apple doesn't approve..." blah, blah, blah. It's like, get your head out of Apple arse, will ya? Don't get me started.
I have already found bugs in v4.0.5, so I'm going to install v4.0.7 to see if they addressed these bugs. If not, I will use v4.0.X to BUILD missions, but will ultimately FLY them with tried and true v2.9.2. This work flow is untested as of this writing, but will be tested by the end of today.
Anyway, good luck to you! I hope this helps you.
D