iPhone distribution provisioning problem - iphone

I'm trying to distribute my iPhone application and doing everything like in apple's manuals. And finally, there is no embedded.mobileprovision in MyApp.app. And also there is nothing about it in Built results. I followed all the recommendations (like clean all targets, clear CodeSign identity, remove all build directories and launch xCode again) and still have no progress.
What am i doing wrong?
There is one more thing i'd like to ask about. In Distribution configuration I've added Entitlements.plist, but builder shows me a warning:
CodeSign warning: entitlements are not applicable for product type 'Application' in SDK 'Device - iPhone OS 3.1.2'; ignoring...
May be these two things are connected with each other?

For distribution on the AppStore, you need not to have an Entitlements file.

Related

AdHoc build install fails via both testflight & iTunes

I am getting this error - http://help.testflightapp.com/customer/portal/articles/829652
I tried this (but did not fix the problem) - http://help.testflightapp.com/customer/portal/articles/867631
I tried installing the adhoc build via iTunes (still no luck) - http://www.youtube.com/watch?v=OF7bstiw_9o
I am using the AdHoc provisioning profile(with my phone listed in it) and distribution certificate. I also went ahead and deleted/created a new adhoc distribution profile, just to see if that fixes the problem.
Also if it counts, I am building for iOS 7.0. I can see the adhoc provisioning profile installed on my iphone via the iPhone Configuration Utility.
Anyone know where I could be going wrong?
One of the potential causes listed in the link you posted is 'Architecture settings of the build and the device are incompatible ( can sometimes happen when "Build Active Architecture Only" is on when building).'
One possible reason for this is that you had the device connected to the computer when you did the build. The build may have been optimised for the architecture of the attached device and the device you are trying to install to may have a different architecture

iPhone Build Error (Entitlements)

I'm getting this error when trying to build:
The entitlements specified in your application’s Code Signing Entitlements file do not match those specified in your provisioning profile.
(0xE8008016).
This is not my first time building apps. This will be my sixth app, so this thing is tripping. I'm making an AppStore distribution build, so I dont need entitlements. I dont have any entitlement files specified in my code signing entitlement. ITS BLANK. For the project info pane and the target info pane, there is absolutely nothing in my code signing entitlements, which is how its supposed to be. Yet I still get this dumb error. Remember, this is NOT an adhoc build, rather it is an AppStore build. What can be the problem??
Do you have multiple versions of Xcode installed (such as one of the betas)? Did you change the install directory after installing your current stable version of Xcode? Xcode installs things for code signing that can break if you either install a new version of Xcode simultaneously, or you rename your /Developer directory.
Also, try checking the console for related error messages.

iPhone CodeSign failed

So - I am a registered iPhone developer (Having paid my $99/year). I have followed all the steps provided by Apple to get the provisioning and code-signing files. However, when I click 'build', it says:
"Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)"
I have re-downloaded all of the certificates and profiles repeatedly, and it still won't work. However, if I click 'build' (and it says codesign failed), but then drag the product .app file to my device in the organizer or click "Run", it will run on my device. Any suggestions?
Since you are able to run the .app on your device, your problem might be that you have buildt it with your developer provision profile. That won't work. You need to build it with a distribution provisioning profile for App store.
Apple provides good information of how to do this, but I think the info is kind of hidden in all this itunesconnect/provisioning portal stuff... Check this link: http://developer.apple.com/iphone/manage/distribution/index.action . There you sould see two important points:
"Create and download your iPhone Distribution Provisioning Profile for App Store Distribution"
"Building your Application with Xcode for Distribution"
Good luck :-)
Does your profile show up in Xcode's Organizer window? (If not, drag the files from Finder to Xcode.)
What profile is selected in your Xcode project settings? Are you building debug, release, or for distribution?
There are many possible causes of the -19011 code verification error (as evidenced by the dozens of near identical stackoverflow questions about it). The specific cause is hinted at in the detail of the message (see Apple Technical note TN2250 advice on the -19011 issue for details)
In my case the error detail contained the phrase "Failed to load provision profile from:" after which I discovered that having spaces or special characters in the app OR the xcode scheme name can cause codesign verification fail.

Testers unable to install application

I've sent my iphone application to my testers and all but one complain that the get error OxE8003FFE when they sync their devices. They are not able to install and run the application.
I'm using an ad hoc distribution provisioning profile and all of the testers devices are included in the profile.
I'm not sure how to proceed and would really appreciate any help you might be to give.
One more interesting bit of information: The program is a universal iPad/iPhone application. My testers are able to install it on their iPads but not their iPhones.
Did you properly add entitlements.plist, and uncheck the box therein?
I would recommend having one device locally that you deploy to through iTunes (not building through XCode), to test that the IPA file will work for other testers. That may mean buying an iPod touch, even the very oldest one will do (if you are targeting 3.x users).
I'd suggest you to right click your package, find a file embedded provisioning profile and open it with TextEdit. See that the name of the profile you've signed your application is indeed of that of ad-hoc.
After that be sure you sent this file (embedded provisioning profile) along with your ad-hoc build to your testers, because they have to install it on their devices, it's not being done automatically and w/o that profile your ad-hoc build will not sync to the device.
After some back and forth with DTS I managed to fix this issue.
The problem was that I was compiling for armv7 only which caused the installation to fail on armv6 machines.
Another interesting bit, the default universal project template and iphone projects converted to universal will compile for both architectures by default, this didn't happen for me bacause my project was initially an iPad only project which I converted manually (since there are no automatic tools for this) to be iPhone/iPad universal, this is the probable reason for this setting being incorrect in my project.

Not Jailbroken - getting Provisioning is not applicable for product type 'Application' in SDK Device

Codesign warning: provisioning is not applicable for product type 'Application' in SDK Device - iPhone OS3.1'; ignoring..
Redownloaded my developer certificate, made a new provisioning profile, still getting this error. Searched the Xcode project and removed all lines referencing a Provisioning Profile, but that didn't seem to remove it from the project settings (went to show package contents, then opened the project file).
Was originally on a different machine then transferred over, if that makes a difference?
Thanks
Check the file
/Developer/Platforms/iPhoneOS.platform/Info.plist
and make sure the following keys are set to YES
<key>PROVISIONING_PROFILE_ALLOWED</key>
<string>YES</string>
<key>PROVISIONING_PROFILE_REQUIRED</key>
<string>YES</string>
When developing for a jailbroken devices, these should normally be set to NO, so you can self sign and copy the file over, etc, but it's not necessary to skip this when you actually have a proper certificate and provisioning for your device.