I have an apple developer ID. I have my developer certificate, my cert in my keychain, I have installed the last version of iOS (5.1.1 (9B206)) in my device (an iPad), I got my profile, I'm on a development team, I told Xcode that I want to use the device for testing. In the build settings, I have set the architectures to armv6 and armv7, both in "target" and "project" as well. Got the provisioning profile.
Still, when I try to run the app on the iPad, I receive an "Xcode cannot run using the selected device." saying that I need to install a newer iOS version (as I said, I installed the most recent on the device).
Anyone have faced this issue before?
You will need to update the version of Xcode to 4.3.2
Related
I have an iPad with an app on it and the provisional profile has expired...do I have have to rebuild my app in Xcode ? and re-deploy it to the iPad or do I simply have to update the provisional profile ? I have created two iOS certificates (development and distribution) but how do I transfer these to the iPad ????? My iPad is running iOS 6.0 and I am concerned if I update the OSon the iPad the app will no longer work ???
do I need to install an earlier version of Xcode that is compatible with iOS 6.0 (on the iPad as the target device) ???
thanks
According to the answer to this very related question, you simply need to renew your Apple Developer account ($99 in the US). Assuming this is the same Apple Developer account you built the original app with you, you can renew and download a brand new provisioning profile and install it on your phone and the app will continue to run with no issues (and no need to rebuild).
If you do choose to rebuild, make sure you set the "minimum deployment version" in your Xcode project to be iOS 6.0, although I suspect there will be plenty of errors and issues that come up with whatever modern version of Xcode you're using. iOS 6.0 dates from 2012, which feels like an eon ago.
I am trying to deploy my Xamarin iOS app to iPhone. But it fails to deploy into iPhone devices where as it works fine in Simulators. I verified that Bundle Identifier and Provisioning Profiles are matching. Also I deployed another test app into iPhone devices using XCode using the same provisioning profiles. It is getting deployed successfully. Also approved the Developer as trusted in iPhone.
The Exception I see Visual Studio as below
error MT1006: Could not install the application
'/Users/VarunRaja/Library/Caches/Xamarin/mtbs/builds/WK.TAA.Mfa.OTPAuthenticator.iOS/116dd0bfdd565dd44e1837c2280a6d94/bin/iPhoneSimulator/Debug/WK.TAA.Mfa.OTPAuthenticator.iOS.app'
on the device 'Raja’s iPhone': AMDeviceSecureInstallApplicationBundle
returned: 0xe8000067 (kAMDAPIInternalError).
I see this is coming from my Mac Agent. Visual Studio says the App is terminated.
As mentioned here by Tim Wheeler, it is an indication that your device is not in your provisioning profile, or your provisioning profile is invalid.
Why?
Basically, iOS will not let you build the app on to the device for security purposes, unless you have registered the device to THAT particular app in the Apple Developer Portal. They have no issues with you installing it on a simulator, so that you can't distribute apps without using the App Store.
Fix
In order to fix this, you need to have Access to the Apple Developer Portal of the company under which the app is registered and then go to the Certificates, Identifiers and Profiles.
Go to the "Devices" tab and make sure your device is in the list. Then go to "Profiles" tab, and you might see an "Invalid" status under the Expiration column of the Provisioning Profile. Fix it, tap on your app's profile, ensure it includes your iPhone, downloaded the new one to the mac and install it.
Not fixed yet?
If that was not the issue, it could be because you have multiple provisioning profiles installed. Visual Studio is usually set to Automatically determine the appropriate provisioning profile, and it could be using the wrong one if you have a few installed. You could delete the unneeded ones, or you can go to your iOS project settings, set the bundle signing to "Manual", then choose the valid profile.
Try to change Linker Behavior to Link SDK assemblies only
Go to the iOS properties => iOS Build and set "Linker Behavior" to "Link Framework SDKs Only" and "Supported Architectures" to "ARMv7 + ARM64"
Create blank project on your build mac host, or mac, xcode. Set bundle id to xamarin bundle id. Build and deploy from xcode, close and try again with xamarin.
I'm sending my app to testers with Beta from Crashlytics which is an amazing tool to do app testing.
I had every new tester's device UDID registered in my developer account and then distribute a new build.
My testers got email invitation and accessed app's installation which could not be completed on their device.
They kept seeing an alert showing up with message:
Unable to download app - MyApp could not be installed at this time -
Done / Retry
Testers' testing status are "installed" in my Crashlytics dashboard but they're actually not able to finish installation.
Please help me find any possible factor causing this problem.
Perhaps the provisioning profile embedded in the build has been invalidated. Use Xcode to create a new archive, then use Fabric to upload a new build with that archive.
Discussion:
In my case, I had deleted the provisioning profile in the Apple Developer Member Center that had been embedded in each of my Fabric Beta builds. This caused the app testers had previously installed to immediately crash when they tried to launch it (embarrassing). It also caused the "Unable to download app - MyApp could not be installed at this time - Done / Retry" issue when testers tried to (re)install the app via Fabric Beta. Uploading a new build with my new provisioning profile embedded fixed the issue (each tester had to install the new build).
I've run into this problem back on iOS8 and just recently saw it again for iOS9, the only thing that solved the install issue was for my users to delete any previous version that they had downloaded, restart their phone, and try again.
You can also verify with them if Crashlytics properly installed on their iDevice, I've seen more than once where the configuration profile caused the issue, it's worth removing that (Settings -> General -> Configuration Profile (towards the bottom)) and retrying the install.
This is usually caused by one of two problems:
Incorrect provisioning profile/code signing settings. Double- and triple-check that the following settings are the same for the project and the provisioning profile: bundle identifier, development vs. distribution, adhoc.
Caching - sometimes, even when you've done everything correctly, things still just go awry. In such cases, you can try: deleting the previous version of the app from your phone, cleaning your project, deleting and re-downloading provisioning profiles, and building the app again.
RubyMotion Solution
For me, it was because I was using a development distribution profile, but with the wrong entitlements. Well, entitlement, singular.
I still had the 'beta-report-active' entitlement enabled, which was not included with the development distribution profile I am using. It is instead included with the production distribution profile (which is needed to distribute to TestFlight). However, I just wanted to deploy to my local phone, and not air my dirty app laundry to my entire internal test group, so this is where I found myself.
In any case, removing the 'beta-report-active' entitlement fixed my issue.
I tried the normal route of checking for proper certs and also deleting the app and provisioning profile along with rebooting device. In my case it was installing on device A and not device B. Device A was older iPhone 5c running iOS 9 and device B was newer iPhone 8 running iOS 11.x. When I archived the app for distribution I was selecting device A during the archive. Once I selected "Generic Device" it worked. But I'm sure I've built in the past selecting a specific device instead of generic and it worked. I was using Xcode 8.2, but I don't believe the Xcode version matters.
I have a problem installing an ipa via diawi.com. It says that it is unable to install it.
It was working fine before, until one morning when Xcode said that it cannot find the provisioning profile on my mac.
So I generated another ad hoc distribution profile (with the same app id, and included the device UDID).
I installed it manually in Xcode and set the Code Signing Identity and Provisioning Profile fields in the BuildSettings->CodeSigning in both PROJECT and TARGETS.
I even tried sync-ing the apple account profiles with Xcode and i get the same result.
Also, old uploaded ipa-s on diawi still work (so it's not something they changed).
Using Xcode 5.1 (58130a)
Trying to install it on an iPhone 4S with iOS 7.0.
The Deployment Target and iOS SDK fields in Build Settings are set to iOS 7.1
Weird error is occurring to me, I followed the guide from apple, to provisioning portal to test the project on a real device, create a certificate, add a device an appID and then the provision file.
Edited all the code signing identity settings to the new iphone developer provision file, and tried to run on my device.
The base of my SDK is 4.2,my device is 4.2 as well, but when i click the run button, its compile all the files, give me the build succeded message but even install on my device, its like none device was connected....
If your device is appearing here:(In the place of "iPhone 5.0 Simulator") Then your device is correctly connected.
And if your device says "Finished Running" When it hasn't even started running then as 'AlexeyVMP' said there are a few more steps to get your app to run on an ARMV6 device (usually the only reason anyone is still on iOS 4.2 these days)
Basically you have to add armv6 to the architectures in the project pane and remove armv7 from the required devices capabilities in the info.plist of your project.
You can see screenshots of these steps at this stackoverflow question in my answer.