Our app relies on the secure enclave to store keys needed to authenticate itself with the server.However a few customers have used the "Quick Start" feature to restore the app onto a new device, and of course, it doesn't work as the secure enclave keys are not present. Specifically, the app starts up, notices the app-data that indicates the user has already registered, but is unable to authenticate. If the app-data wasn't present, it would assume it was a first-time install and present a registration screen.How can we prevent the app being backed-up/restored in this manner?(NB we could just change the app to assume that if the secure enclave keys are not present then the app has not been correctly installed and just show the registration screen again. However in at least a couple of cases this we were getting random errors trying to read from the secure enclave and just rebooting the device fixed it, though it seems that's since been addressed).

We're trying to get our app to successfully upload to AppStore/TestFlight after upgrading to Xcode 10.1 and enabling Bitcode throughout. We keep getting lots of errors, but the main problem is that it takes up to a full hour AND A HALF to build the entire app, upload to app store then to wait for it to get out of "processing" state to confirm whether or not it was successful. The version I just uploaded has been in processing state at least 20 minutes with no indication as to what's going on. The information that comes in the email when it fails validation often is not very helpful (e.g. missing dylibs but no info as to which ones). Is there anything that can be done to speed up this process, as it will potentially take us weeks to get a successful upload at the current rate?ThanksDylan