Mark,
There are two situations of which MTH is aware.
First, there's a bug in the Premium DCS App that will cause an import of a DCS Remote backup file to fail on an iOS device (iPhone, iPad, etc.) if the DCS Remote contained Z4K Tracks. Making a DCS Remote backup after deleting the Z4K Tracks allows the backup file to be imported successfully. I discovered and reported this during beta testing. It should be corrected to strip out the Z4K Tracks upon import in a later release of the DCS App.
There's also a situation where having a backup created from a DCS Remote's whose contents have been corrupted will also yield a backup file that cannot be successfully imported into an iOS device. Further, if this backup file isf imported into an Android device, the app may experience issues. MTH is aware of this, as well, however, the safest solution may of necessity be to fail the import.
I can attest that the DCS Remote import process works extremely well on an iOS device, if the file is uncorrupted and Z4K Tracks are not present.
| This and a whole lot more about DCS WiFi is all in “The DCS WiFi Companion 1st Edition!"
This book is available as an eBook at MTH's web store! |