I am trying to install an ad hoc build for the iPad and it won't install. It does install on my iPad with iOS 5.0, so I know that it isn't a certificate problem. I just can't seem to figure why it wouldn't install on a device from ad hoc install via Safari
I have had this happen as I use many different machines to build multiple projects and multiple devices to test.
You have said that your iPad is running iOS 5.0 but you are building an adhoc build for base SDK 5.1. The XCode tools dont allow your test device not to match exactly the base SDK you are developing for.
You either need to update your iPad to 5.1 or downgrade your base SDK to 5.0. I would recommend simply upgrading your iPad!!!
I figured out the solution. I needed to go to Edit scheme->archive then set Build Configuration to Release
Related
I have an ipad device with 5.1 OS and am trying to run a 5.0 base SDK app on this device.
here's my error:
thanks for any help.
I believe from your screenshot that you are running Xcode 4.2 with the iOS 5.0 SDK, in order to deploy to devices running iOS 5.1 you will need to upgrade to the latest version of Xcode (4.3.2) which has the iOS 5.1 SDK and will allow you to deploy your build to a 5.1 device. This upgrade will require OS X 10.7 Lion. Even though you are targeting a version of iOS supported by your version of Xcode, you can not deploy to devices running a newer version of iOS than your SDK supports.
(Lion upgrade alternative https://stackoverflow.com/a/9621226/716216)
Your device UDID is not added in the developer profile you are currently using.
Go to the developer portal, add the device to your account, add it to your development profile, download the profile again, install it and use the new profile to test the build with.
i thnk you have selected the device as target, and your ipad is not properly attatched to it. if it attched, xcode will show ipad's name
more over. make sure device is added to provisioning profile u'r using
We have made many Distribution Builds, so we are familiar with the daunting iPhone provisioning process.
We have entered all the devices into the Provision Portal, we have downloaded all certificates, and when we distribute our BETA build, it is only working for users on iOS 4.x. This is strange behavior because it wasn't doing this before.
Our iOS Deployment Target is set to: iOS 3.0
Base SDK is: iOS Device 4.1
Don't you think if we had a reference to a Base 4 SDK method, that it would at least install, but then crash? We are getting the infamous:
"The executable was signed with invalid entitlements"
This seems like an odd error when other all other devices that are on iOS 4 are working and all the iOS 3 devices are getting this?
We are stumped, thanks!
Are you doing a build and archive? You might want to try building it and manually zipping it along with the provision and sending that to your beta testers. I had this same problem with iOS 3 devices and zipping it manually seemed to work.
Versions of iOS prior to 3.2 cannot take advantage of an embedded provision file (included in the zip). For those devices, you have to install the .mobileprovision file separately by dragging it into the library in iTunes.
I am a registered Apple dev with the certificates, and mobileprofiles that i need. I have made several apps in xCode that I would like to test on my 3GS, I have registered my 3GS as one of my allowed devices but it still will not install giving the install prohibited error. The Xcode is set to same profile as my iphone has. Just dont kmow what to do. well i guess i =ll download sdk 4.1
You will get this exact message if Restrictions are enabled on the device, specifically the restriction on installing Apps.
You need to upgrade your SDK to 4.0.1 to use it with iOS 4.0.1 devices.
Is the iPhone OS Deployment Target in your Build Settings (either for the project or for the target) set for an OS version higher than the one on your 3GS?
i have xcode 3.1.3 and xcode 3.2.1 installed
For sure now I use 3.2.1 with Sdk 4 to develop new apps.
But what if I like to test a App compiled with sdk 4 on a
simulated iphone that would just have 3.0??
As BaseSDk i use 4.0 and as target 3.0
In xcode 3.1.3 i could select a simulator down to 2.x but with sdk 4.0
i only have the option 4.0 iphone or 3.2 ipad
Example> i know iAd is not supported before 4.0 so I set the
framework to weak. But just to be sure all works fine I really
would like to test my app in a simulator that simulates an iphone with 3.0
thx
chris
The new simulator does not seem to be able to run the old simulator OSs (3.2 being the oldest it'll run). I tried moving them over from old SDK installs and several variations and "no go".
You can check that you aren't using methods defined in the new SDK, when you set the base SDK to 4.0 but set the Deployment to to 3.1.3, for example. For a blog post on how to do this see this blog post, and note my comment on an easier way to do the last two steps (no need to edit the project file as a text file).
inside the iphone sdk dmg file, there should be a folder called packages. in it, you'll find packages like iPhoneSDK3_0 and iPhoneSimulator3_0. Install them to be able to use them in xcode.
Correct me if I'm wrong, but I think a device with 3.0 installed can't even run apps compiled with 3.2 or 4.0. Furthermore, Apple now only accepts iPhone apps (including updates of existing apps) linked against the 4.0 libraries, which won't run on OS version 3.0 devices.
So why do you want to test your app on a 3.0 device?
Try setting the architecture you want to build for in the Xcode project preferences and rebuilding.
If this doesn't work, completely uninstall Xcode and downgrade. You have to completely uninstall because your system must have updated the frameworks for 4.0.
Hope this helps
If I install SDK 4.0 of the iPhone OS will I still be able to create a non 4.0 iPad app?
I would ideally like to submit a iPad app in the next month but am also hoping to develop a 4.0 iPhone app is it possible to use the 4.0 SDK to create 3.0 iPad apps or am I going to need to computers?
You do not need two computers. You will have to install the two SDKs in two different directories. So far, it's always been the way that beta releases of the SDK were not meant (and not allowed) to generate apps for distribution.
But in the installer, just select another new directory and then install the second SDK there. That's all there is to it.
So far Apple has always provided a way to create Applications compatible to older versions of iPhone/iPad OS. The SDK installer will install the SDK in a version specific subdirectory. Additionally there is a "Current" directory hardlinking against the newest version. The old versions will still be available.
XCode will let you select an iPhone OS Version in the build settings and automatically figure out the correct SDK version/directory, so there's no need to fumble with paths or include directories.
Build against the latest SDK and set your "deployment target" to a lower version.
If you use new API calls (available in the SDK but not in the deployment version) check at runtime before calling them.