I can install the watch app on my iPhone using Xcode fine. But, I get the following error when I (or my beta testers) try to install the watch app using TestFlight.
I found this message on the console. The provisioning profiles are handled by Xcode automatically.
Previous build of this app had no problem with the Watch app installation via TestFlight, but now even previous builds in TestFlight refuse to install the watch app.
The problem was with TestFlight and Apple has fixed the problem. I can confirm that the watch app installs using TestFlight now. I did not change anything on my side.
Related
I'm trying to install my app from TestFlight.
When I press INSTALL, the download indicator runs for a sec and then stops.
I can see the app on my phone, clicking on the app raises
Unable to install the app, please try again later.
It's very weird, since I run the app on a physical device using Xcode, and everything was just fine. Also, older versions of the app are downloaded from TestFlight without any problem.
The app passed through all checks before uploading to the store.
How is it possible that I cannot install the app from TestFight?
What can I do in order to debug this issue?
This can be happen with number of reasons as given below:
Might be you are using the developer profile instead of Adhoc profile
OR using an app identifier that is different from the one that belongs to your profile
OR might be an issue in enable/disable of iCloud and Gamecenter
What you can do is you can connect the device to PC/Mac. Open the iPhone Configuration Utility and see the logs after you press install from the build in TestFlight. It will helps you to dig it.
And last hope is this issue can be at apple side as many developer are facing as given below: https://developer.apple.com/forums/thread/26759
It's not the correct answer.
In case you are in a rash, and your project was already uploaded from another Mac to the store, a temporary solution will be to import the project to a well-configured Xcode from another computer and send it configured back to your computer. Make sure you have all necessary certificates, Build, and upload to the store. Then I was able to run the app on TestFlight and upload new updates without problems.
IMO, Apple did a really bad job connecting and configuring Xcode projects to the store. As a Flutter developer, I upload apps for both App Store and Play Store, and working with Apple is frustrating. There were no logs or indications about this issue, and it's almost impossible to track the mistake.
Have noticed a weird forced upgrade issue with TestFlight. Opening the app and it shows the Welcome to TestFlight intro screen, and pressing Continue shows an alert with the message:
TestFlight Unavailable
We've release a new version of
TestFlight. Download the update in the
App Store to continue testing.
However, opening the App Store, the latest version appears to be already installed (shows the Open button).
This is on iOS 10.3.3
I've run into this before, looks like TestFlight isn't auto updating from the app store. Was able to get it working again by uninstalling and re-installing TestFlight from the app store.
Hope this helps
I met a strange problem for iOS app, created in VS with Xamarin. When I created mobile provision in Apple developer account for testing app on real devices (AdHoc type, like Xamarin tutorial shows), I tried to install app to devices, added to provision. Installation was successful. After that I tried to install app to devices not added to provision. Installation was fault. But when I deleted all devices except 1 from provision and updated provision on my Mac nothing changed. I still can install app to devices, was in provision before.
Can anybody help with this problem?
I am working on a watch app. The watch Version is 3.1.3. and the iPhone version is 10.2(14c92). This app works properly on both simulator's (Mobile/ Watch).
Now I try to test the app on the real device but the problem is I am not able to install the watch app manually or automatically. I have checked the multiple links of installing the app manually or automatically and I'm sure I do same as suggested by tutorials.
The problem is when I choose my app from My watch Apps List and turn on the switch to show the app on watch, it shows the installing status for few seconds and then the switch turned off automatically. And this happens multiple time.Please suggest me what can I do to install the watch app.Thanks in advance.
After efforts of lots of hours I resolved the issue. Actually I forgot to add the UDID of watch in the provisioning profile. Just add the UDID in both provisioning profiles for watchkit extension and for watchkit app, it resolve the issue.
I built an iOS app with a companion Apple Watch app and recently submitted it to the App Store. This morning, it was rejected for failing to install. Here are the steps to reproduce:
Install the app on iPhone
Launch the companion app
Toggle the "Show App on Apple Watch" switch
The app attempts to install on the Apple Watch
Error message is displayed on Apple Watch and app in not installed.
Toggle switch in the companion app is set to "off"
Obviously, I don't have an Apple Watch to test this with, but it works fine in the simulator (and installs fine on the Apple Watch simulator). Perhaps it has something to do with how I'm signing before submission? Has anyone run into this same issue?
Here is the error message reported on the Apple Watch (given to me by Apple's Review Team):
App Verification Failed
Have you ever opened the project in Xcode 6.3? If so, it likely set your deployment target to iOS 8.3, which will cause this error.
The problem is that if you opened your project in Xcode 6.3 at some point, it updates your deployment target to iOS 8.3. This however isn't reflected in the project's UI, you have to right click your project file and show contents, then open up your project.pbxroj and search for deployment target and change it to 8.2
I had exactly the same error.
Went to the Apple developer portal website and to the devices section.
Then I had to go through the 'device reset' procedure.
The reason being that I had entered a new developer programme year. It seems that it had refused to provision the device until I went through that reset - not that it told me!
Once I had done this, I popped into the Window->Devices (from xCode) and I would see the watch.
From that point on it worked fine.
(I checked back in the device list on the developer Portal and there it was).
Also, if it does not turn on automatically, that Window->Devices shows the UDID that you can use to manually add your device.
Hope that might be of some help :)