I tried last 1 day. refer all the question related my problem but can't find such a solution.
I had follow all the steps create certificates, appid, adding device id , create provision, set in the project. with this provision the app work fine in my iPhone4.
please help me
Thank you in advance
In xcode 4.2 there is a totally bug for when the creating the ipa and share that time best solution find me first of all find the share bundle and then following link for the solve that problem it's rally amazing
I solve that problem while creating the project
Reference link is here :-)
You need to go to Build Settings > Code Signing and set the code signing profile automatically for each setting. Don't just use 'Automatic'.
there maybe problem with Entitlements file as well.
You can find it in XCode 4.2 -> Targets -> bottom section 'Entitlements'
There you can "Enable Entitlements". Other fields may be empty if the app doesn't need it.
Other codesign problems issued many time here. So you can find one of lots tutorials and remake codesign profile.
There is currently a lot of chatter on the forums (especially the Apple dev forums) that something has broken or been modified in the creation of certificates in the dev portal. All Apple dev portals are currently down (displaying the "back soon" post-it message) so hopefully this means that Apple are providing a fix.
Related
"The app "App Name" was not installed on iphone "iphone name" because it is not signed."
I m getting this error when I try to create an adhoc build. I founds some solutions and tried those but none of them are working for me.
I have created a distribution certificate again and .mobileprovison certificates for 'n' numebr of times, but still i m getting this error. I have added Entitlements.plsit and also creating build for distribution configuration(which is copy of release). In organizer also it shows a valid provision profile. I m cleaning up Targets all the time when I create the build.
Am I missing any steps to create adhoc build. Please some one help me out of this. I m working on this issue from so many days.
Sometimes Entitlements.plist need full path.
Looks like
~/iOSProject/myProject/Entitlements.plist
I hope so that is a little problem for quick solution.
There are a few steps missing in your description of your problem, so it's unclear whether the problems are with the signing and packing of the ipa files or whether it's related to your installation of the app.
The good folks over at TestFlightApp have provided an excellent step-by-step guide for Xcode 3 and Xcode 4 on how this should be done.
It's not entirely black magic to make it work, but it's close. Just make sure you follow the steps one by one exactly as they are described and it should work - at least it did for me.
This question already has answers here:
App Submission Error - Invalid binary - Invalid Code Signing Error
(3 answers)
Closed 5 years ago.
I ve followed all the procedure that app store support placed for help yet when ever i sumit the app after upload the status becomes "invalid binary" with following msg in the mail.
Invalid Code Signing Entitlements - Your application bundle's signature contains ubiquity code signing entitlements that are not supported.
Specifically, value "( 79FWT492R4.* )" for key "com.apple.developer.ubiquity-container-identifiers" in is not supported.
I will be thankful if someone help
Thanks
MGD
Well i really dont know why Apple has set so many complications for the app submission.Now coming towards the solution, What i did was, I used the same APP ID but i reconfigured it by unchecking the iCloud option, then i renewed the provision and distribution profiles downloaded them, deleted the old profiles from the xcode organizer added the new ones (those i downloaded after renew), first my app started giving error during the that "key does not match .... " then i went to the built info of the target there i simply set "iphone distribution" in code signing, Thats it i build the app and uploaded via organizer, and it went with the status "Waiting for Review" :)
Cheers
MGD
Just to clarify the answer, which I found confusing. I had ths problem just now (October 2011) and solved it quickly.
I thought I had to revoke my own distribution certificate, but this clarifying note saved me (can't find the source right now but THANK YOU)
Go to App IDs in the provisioning portal. Scroll to the bottom. Click configure on the row that represents your app’s ID. Uncheck Enable for iCloud. Click Done.
--
Now you can just regenerate your distro provisioning prof (no need to create a new one) and redownload it into Xcode, reubild and resubmit. i hope this helps people
There is indeed no more option to disable iCloud in Provisioning Portal. But apparently Apple has noticed that the iCloud entitlements in distribution certificates may cause trouble during submission and has recently REMOVED these entitlements from the certificates again.
So help is near: Just re-create your distribution certificate and you'll see that it doesn't contain the offending keys any more. Hope that helps.
Under the Code Signing section in my Build Settings, Xcode had selected iOS Developer for Release instead of iOS Distribution. Selecting the correct distribution profile for Release resolved this issue for me.
My solution was to remove the provisioning profile entries. Evidently in addition to the Code Signing entries, now there are also Provisioning Profile entries and mine was stuck on an old version or something. Clearing that fixed the problem.
In order to distribute my iPhone for test purposes on a couple of device Over the Air, I have created an AdHic distribution profile and followed the explanation I found in this blog (sorry it's in French but the screenshot are quite detailled):
http://www.media-business.biz/content/iphone-cr%C3%A9ez-votre-propre-appstore
I install the position profile on the device from my web site but when it comes to the application I have an error message saying it's impossible to download the app.
Is this a known problem ?
Thanks a lot for your help.
Regards,
Luc
ps: just adding a last minute question... is there a place I could see some error logs ?? :(
Here's another explanation in English. This distribution method only works with devices running iOS 4.x
Make sure that:
The IPA file name matches exactly the name of the server (case sensitive).
The bundle version number is identical in the IPA file and your plist file, and that you update it every time you make a new IPA (or the phone will think it's already installed and not update)
You are using an itms-services:// link to point to the plist file, and the plist file has the correct URL to your IPA file.
When you go into Organizer and press the "Share" button, you select exactly the distribution profile you intend to use (sometimes I think it can select the wrong one with automatic).
I had this exact same issue, and it was because I hadn't installed an AdHoc mobileprovision file and was building against my Dev mobileprovision. Check that first.
I finally found testflightapp.com, that is really great !
I also think testflightapp.com is the most convinient way to do this, as long as the beta testers you'll contact accept to sign up there. The great additional value is that if you install their SDK in your app, you'll be able to monitor the activity of your beta-testers (for instance you can define waypoints with definite names).
However, if:
You already konw the UDIDs of your beta testers
You just want them to be able to click on a link from your server to start installing the app,
You don't need "in app" follow-up and just request feedback from your testers,
Then I strongly recommend this tutorial:
I really combed this site and others. I read and re-read the related links here and the Apple docs. I'm sorry, but either I am obviously missing something right under my nose, or this Apple profile/certificate stuff is a bit convoluted. Here it is:
I have a product in the App Store.
I have updated it several times and users like it.
My development profile recently expired just when I was improving the app for its next release.
I can run the app in the simulator.
I can compile and put the distribution build on my iPhone just fine.
I went to the Apple portal and renewed the development profile.
I downloaded it and installed it in Xcode.
I see it in the Organize window.
I see it on my iPhone.
I CANNOT put the debug build on my iPhone to debug or run with Instruments. The message is that either there is not a valid signed profile or it is untrusted.
I subsequently tried to download and install the certificate to my Mac's keychain.
Still no success.
I checked the code signing section of Project settings and also for the target and the root. All appears to indicate that it is using the expected development profile for debug.
Yes, I had deleted the old profile from my iPhone, from the Organizer. I cleaned the Xcode cache and all targets. I have done all of this several times and in varying sequences to try to cover every possibility.
I am ready to do anything to be able to debug with Instruments in order to check for leaks or high memory usage. Even though the distribution compile runs fine on my iPhone and plays well with other running processes, I will not release anything without a leaks/memory test.
Any ideas will be appreciated. If I missed something obvious, please forgive me - it was not due to just posting a question without searching for similar postings.
Thanks!
All problems solved! I am very happy this all happened because I learned so much about Xcode, keychains, certs and provisioning. Unfortunately, there is not a simple answer. Here are the highlights:
I needed to recreate the ad-hoc profile and install it on my device. (That was MY BIG oversight and the reason the dist build no longer ran on my device.)
Between the very first time I created my profiles and the date my development profile expired, I upgraded to the 3.1.3 Xcode SDK.
It seems that this now means you need 2 entitlements files; a debug version with the get-task-allow checked and a distribution version with get-task-allow unchecked. Each need to be set in the respective settings.
In Project settings, I needed to set both my working directory and intermediate directory to the build product directory.
BIGGIE - I had to double click on the target and reset the appropriate code signing profile. There was an old profile name still there for some reason! Now, I can debug, and drop my distribution on my device without a hitch.
So, in summary, I believe that my original problem (not being able to debug after renewing my dev profile) and the problem that resulted from all my efforts to fix the first were caused by:
the fact that I upgraded to 3.1.3 during my dev cycle
my own oversight (I apologize to Apple for my criticism)
an Xcode quirk (the old profile name hanging around in target settings).
I hope this helps others. The best advise I can give is to take a day off and then create a new empty project, going through the same process step by step.
Thank you all!!
Try re-creating your development mobileprovision file on Apple's site. Be sure to delete all old copies from Organizer (including those on the iPhone itself).
For a long time now I have been searching through the forum whilst teaching myself the delights of iPhone programming, and I thank you all for the massive number of questions you have unknowingly helped me with!
I seem to have come up against a brick wall regarding the upload of my finished application to Apple and would appreciate any help/advice that you may be willing to give.
This is my first upload to apple so apologies if this is all a little sketchy!
After some tweaking I have successfully managed to follow Apples guidelines on creating a new Distribution profile for my project, applied my new Distribution certificates in the Target info and got the project to successfully build. Sounds good! Problem is when I upload this to apple i get their generic "App is not Signed" error.
After one hell of a late night and some research I realised that in the detailed Build Log of my application there is no line that includes the word "CodeSign" as apple suggest. It appears that XCode when compiling isn’t even attempting to CodeSign .app.
What I have tried:
Creating new AppIDs, Certificates and Distriution profiles (a number of times).
Trying to package an Apple example (untampered).
After a 7.5 hour download i have reinstalled XCode to no avail.
Is there something simple I am missing? Has anyone else experienced this where XCode doesn’t add a CodeSign row to the Detailed build log?
Any help would be very much appreciated.
Regards,
Ralph
Solved
I think the fact I wasn’t building under device played quite a big part in this. After much (more) tweaking I managed to get it to CodeSign by:
Re-installing XCode
Running the Clean All targets function a huge number of times in-between everything I did.
Deleted all certs on my Keychain and downloaded all new ones.
Making sure I was using device and my Distribution profile on both Target and Project settings.
And a lot of sweat and tears..!
Thanks for your help!
That's weird. You're definitely building for the device and not the simulator?
Double check your Code Signing Identity in your Release/Appstore configuration settings.
It should be Any iPhone Device: iPhone Distribution: Your company name