After upgrading my iPhone 5 to iOS 7 beta, it seems I have to re-connect it to Testflight.
Unfortunately, I can't install the provisioning profile:
After selecting 'Reconnect Device', 'Install Profile', 'Install Now', the alert is 'Profile Installation Failed. You iPhone is not activated'
I tried to remove the previous profiles, clear Safari cache and reboot, but no success...
Short answer - Go to TestFlight directly on Mobile Safari and use the TestFlight CocoaPod.
We got TestFlight working on the latest iOS 7 build. The TestFlight "app" that installs doesn't work, but manually visiting the TestFlight site in Mobile Safari allows you to install the profile and load the app. Nothing special needed. It sometimes takes a few tries loading the profile to get it to actually load.
Also, loading our apps into TestFlight wasn't working, so we started using the TestFlight CocoaPod and it works great.
I got it working on an iPad mini running iOS 7 beta 5, that was previously used with testflight while running iOS 6. It seems that it will work under some circumstances. What I did:
Unregistered the device from its connected testflight user account (actually this step might be irrelevant)
Launched testflightapp.com from Safari, not from any icon placed on home screen. It has to be from Safari where the url bar is shown. From here I could install betas. However the device itself is not listed under any user and it is not activated. While trying to activate it, testflight app says the registering works OK, however it really fails.
So, it MIGHT work but it's clear that the people at testflight has some work to do.
More: I am unable to get it working with an iPhone 4 iOS 7 beta 5 at all. The iPhone has not previously been used with testflight and seems to require an activation through that profile (at testflight or Apple, not sure) but the activation fails and there's no app list coming up in Safari, just the activation sequence. The key here might be that the device must have been used with testflight before, while on iOS previous to 7.
It seems that using testflight with iOS 7 beta does not work and/or is not supported at the moment.
Not sure what happened here but I was using testflight with an iPad mini that had iOS6. When I just upgraded it to iOS 7, the testflight site loads on the device, however installs never process.
I found the answer of Lysann Schlegel most useful. After some experimenting, I found out that simply opening TestFlight from Safari works fine. Don't use TestFlight app icon.
I had the same problem. In my case after i connect my iphone with the xcode/ organizer beta it let me install again the apps.
Check in Settings if you have the Developer options.
I'm sorry to say that this is currently untested and is a only workaround, but try downloading the ipa file from the TestFlightApp "Share this build" link and use xcode to install it.
This link is normally provided to allow pre iOS4 users to install using testflightapp.com
Even if this works this workaround is probably unacceptable for a vast majority of beta testers.
I'd say also use the "iphone configuration utility" but I suspect that the current release does not support the iOS beta.
If this does fix the issue for people then it's some confirmation that it's mainly the OTA profile that's at issue.
I did a fresh install of iOS 7 beta 6 (it did not have any provisioning profiles before) and was able to load an app from TestFlight. Installing the provisioning profile failed from the web, but I was able to get the correct one onto the device through XCode's Organizer. Then I downloaded the app from TestFlight in Safari (not the little portal TestFlight app). It loaded up just fine.
Related
I have noticed on iOS 15, when I install an app from TestFlight, my app icon is not appearing on the device. Only placeholder for app icon appears on physical device.
All app icon assets for every resolution are correctly added to Assets. The app icon appears in the test flight app and in appstoreconnect everywhere including TestFlight and builds.
The only place it doesn't appear is on the device. It appears normally on the simulator.
The only fix I found was to add a version of the app to add a build where you submit for review and save it. No need to submit. Then install from TestFlight and reboot device. The problem is as soon as I uploaded a new build to TestFlight it stopped showing icon and had to go through this silly process again.
I have never had this issue with past apps and wondering what the issue is and how to resolve it.
I encountered the same issue with testflight on iOS 15. I found this from apple developer forum that might of help:
https://developer.apple.com/forums/thread/682648
According to the accepted answer by #vladweinstein, a temporary solution is to restart the device after installing the app.
This works for me too.
We are still having the same issue with TestFlight apps (iOS 14.7 and iOS 15+)
The only solution we found is to restart the device as Raphael Rex mentioned.
Environment:
Visual Studio 2015 on PC
Visual Studio (Xamarin) on Mac
iPad is connected to Mac
My setup used to work fine. From PC, I would be able to debug iOS apps running on the iPad.
Yesterday, I updated the Mac OS as well as my iPad iOS. I may have updated a few other things too. However, now I am running into problems deploying Xamarin iOS apps on the iPad.
I can create an iOS app in xcode and deploy it successfully. However, when I try to build my Xamarin app, I get the error "No installed profiles match the installed iOS signing identities."
There are a few posts on the forum that talk about a similar problem. I have gone through all these posts. I have also downloaded (once again) my iOS certificate from Apple developer portal and added it to my keychain store.
I still don't understand why I get the error. Would appreciate if someone can tell me how I can get the list of installed iOS signing identities and compare them against the list of provisioning profiles.
Also, when I look at my plist.info file, I see that, for key CfBundleIdentifier, the value is replace_bundle_id. I am wondering how I can tie this bundle id back to my provisioning profile. On Apple's portal, I see a bunch of provisioning profiles (I am part of an enterprise team). There is no field called bundle-id on these profiles. All each of them have is an app-id. Where do I related the bundle-id to the provisioning profile? Regards.
Provisioning profiles are all inside the directory: /Users/m.piccotti/Library/MobileDevice/Provisioning Profiles
Usually when I have these kind of problems and no time to understand what's wrong, I simply delete everything inside that directory and I download again all the profiles from Xcode. Naturally you can try this only if you are sure that you'll be able again to download all the provisioning profiles you need.
Or it could be that you have to set the right provisioning profile for the project:
This info is saved into iOS.csproj, the element CodesignProvision.
When you go to Apple Developer portal and check App IDs, you see the Name and ID of your app. The ID is your bundle ID. That you need to enter in your plist.
Based on that Xamarin will find your profiles.
Here is what I did to make it work. This is based on the feedback I received from the other two replies.
From the Apple developer portal, I looked at the ID of my app. This was in the form com.mycompany.myproduct. In my Xamarin iOS app's plist.info, the id was replace_bundle_id. I changed it to match the one from the portal.
Next, I cleaned the "Provisioning Profiles" directory on Mac and used xcode to create a test project and change the bundle id (from project options) to match the one on the portal. xcode automatically created a new profile.
This made the whole thing work. Now I am able to deploy and debug from my PC to iPad via Mac.
Our project was generated by Xamarin wizard a long time ago and used to work just fine until recently. I still do not know why replace_bundle_id worked in the past and stopped working all of a sudden. The only change I had made was that I upgraded the OSes on the Mac as well as my iPad.
im trying do develop my app on my watchos3.1 and i getting every time this error.
no symbols for paired Apple watch
Xcode doesn't download the latest symbols for my watchOS 3.1. In my folde
Library->Developer->Xcode->watchOS DeviceSupport->
i only find a file with "watch1,2 3.0"
how can i download the file with 3.1 ?
Just ran into this issue with Xcode 9 and watchOS 4. It turned out that I was not logged in anymore to my Apple ID in Xcode. Go to Xcode > Preferences > Accounts and log into your account. Then disconnect and reconnect the iPhone with the paired watch and Xcode should now be able to download the symbol files.
In my case this happened because there was a new license agreement pending in my account. After I had accepted the new agreement, Xcode was able to download necessary symbols
I had a similar problem and ended up deleting the app from my phone and watch, closing Xcode, and trying to install it again. After a few attempts this ended up working. I would also double check that you're running the latest version of XCode. Hope you get it resolved!
I managed to get my watch app working by installing the app to my phone first (without the watch component), and then installing the watchOS app directly from my phone's Watch app.
This is a bit of a work-around, but I too could not find the 3.1 file anywhere.
my app crashes in the simulator.
Just installed OSX Mavericks with XCode 5.
Developed the app using Corona SDK.
I deleted my old provisioning profiles and created new ones.
my Bundle ID is something like com.company.appname
I get the following error message in the console log from the simulator:
killed testapp[pid xxxx] because its use of the keychain-access-groups entitlement is not allowed (error code -67030)
I already deleted all old project screenshots / files. Don't know what to do.
The compiled app runs fine on my iphone 3gs with iOS 6.1 though.
any help highly appreciated
roman
Corona's engineering team is looking into this. Please add your information to this post on the Corona SDK Forums
http://forums.coronalabs.com/topic/40706-app-crashes-in-xcode-simulator-ios-7-sdk/page-2
Using Xcode 4.5.2 and building for iOS4 or newer, I get this message when building for my device (iOS 6.0.1 on 4s). I dismiss the dialog then relaunch the app on my device which seems to work. I am newer to iOS development, so I aplogize in advance if this is a silly question.
Thank you in advance for your help.
My issue was using Distribution provisioning profile for signing the app, once I made a development provisioning profile, the app installed and ran on iPhone just fine.
The answer seems to be "you need to fix your provisioning profile", but can happen for several reasons, as indicated by other answers on here.
In my case, I hadn't added a new device to an existing developer provisioning profile, so I just re-created the profile with the new device, and it worked!
In my case happens all time I add a new device ID then update the provision profile, download and "install it on Xcode 5".
To fix this:
Go to Xcode>Preferences>Account Tab>Select Apple ID>View
Details>Refresh Button (Bottom left corner).
Reinitiate Xcode.
Start again the app, you will be able to test the app in the device.
Here's what my situation was and how I solved the problem:
I had been running the app from Xcode to my phone and all was fine
I switched to a different code signing identity (I had to change the bundle name also to match)
I ran the app to my phone and got the error. The app would install, but not open.
Did a bunch of stuff like Clean, close n open Xcode; delete the app from the phone. All to no good effect.
SOLUTION: turned the phone off n on.
Coincidence? I think not. :-)
XCode 6:
Just create provisioning profile for development and assing it to Project -> Build settings -> Provisioning profile
For upload you have to change provisioning profile for Distribution profile.