Finally, I have completed my first application successfully, but I had two issues since last night while uploading.
Appnametests.octest is in redcolor.
right clicking on .app and 'show in finder' is redirecting to debug-iphoneos folder. which, when compressed and uploading with 'Application Loader', is giving an error 'Application failed codesign verification. The signature was invalid, or it was not signed with an iPhone Distribution Certificate.'
When I was playing around, I went to the 'Release-iPhoneos' folder, compressed the .app file, and uploaded and suddenly the file has been uploaded.
My question is,
Did I do anything wrong?
Is there a chance that my application could get rejected?
First of all relax. Appstore uploading is not that difficult. It's confusing process when you do first time. It's important you follow all the steps correctly. However, you can anytime go and re-upload the binary on iTunes Connect.
It's better to upload your app from Xcode. Assuming you used XCode to upload your app.
Before you are ready to upload the app on app store. You have to select your distribution certificate in your app settings. This " 'Application failed codesign
verification. The signature was invalid, or it was not signed with an iPhone Distribution Certificate." error indicates that you had not selected the distribution profile. I'd suggest you to reconfirm this. You can check this to create distribution certificate.
Once this is done you have to make your app status on iTunes connect as "Ready To Upload".
Then you go ahead and distribute you app. Which gets submitted to app store for review.
When your binary is successfully uploaded your app status change to "Waiting For Review"
1.Did I do anything wrong? - If you have missed any of above step you might have made some mistake.
2.Is there a chance that my application could get rejected? - If you have made any mistakes that means your binary isn't uploaded properly. So this is irrelevant.
If you feel there's something wrong then instead of waiting for next seven days and app telling you we didn't receive your binary. Just delete the correct binary if necessary follow the steps given here
Related
So I did what many suggested and kept TestFlight SDK in the release build to be prepared when FlightPath finally launches.
However: After following TestFlight's instructions for the predecessor called "TestFlight Live", TestFlight refuses to accept my App Store IPA (continue reading) and gives this message:
Invalid IPA: The keychain-access-group in the embedded.mobileprovision
and your binary don't match.
I did what they said:
1) Made a release build and submitted to the App Store, with TestFlight SDK and checkpoint calls included, but -setDeviceIdentifier: call removed.
2) From Xcode Organizer window: Selected the submitted archive, clicked "Distribute" to re-structure it as a TestFlight-compatible binary, signed for AdHoc distribution over TestFlight.
Apparently this binary is garbage for TestFlight which lefts me wondering: How am I supposed to ever get to the analytics data once FlightPath arrives? Am I better off rejecting my submission and stripping out all the useless TestFlight SDK code or can this be fixed?
You don't have to upload the app store build of your app for it to work with flight path. As long as you have uploaded or created an app that has the same bundle id and app token the app will appear in flightpath without you having to upload.
Make sure you have the correct app token that matches your bundle id!
This is about the 5th time I have deleted all certificates, made new ones, republished, and tried to load. I seem to get the same errors every time. I am sure the provisioning and certificate are for distribution and not development.
It seems only one little section of the adobe help mentions the zipping and unzipping. Is this hackish method really working for people? Is the ipa the only file including in the zipped folder?
When I do this, unzip it, and go into the payload folder I see the file APPNAME.app, but it looks like a piece of paper with a big white circle with a line through it. When I try to click on it the mac says, “can’t open this file”
Is this normal? I zipped it and tried uploading but I am still getting these errors:
Unable to extract codesigning entitlements from your application. Please make sure rufood8 is a valid Mach executable that’s properly codesigned.
Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an Iphone distribution certificate.
I am trying to upload my first iOS app to iTunes Connect, but I am unable to do this because every time I try to upload it, I receive the following error from Application Loader:
The binary you uploaded was invalid.
The signature was invalid, or it was
not signed with an Apple submission
certificate
I have followed the instructions on the Apple website to the best of my ability. I have noticed that the .mobileprovision file that should be in my built .app file is missing - does anyone know what would cause this particular part of the problem to happen? I suspect it could be the root cause.
Moreover, does anyone have any other suggestions as to how I might correct this issue?
on the agent account in developer.apple.com
You must create a distribution certificate
You must also create a Distribution Provisioning Profile.
Download both of these and drag them onto xcode.
In the target info for your project you need to go to the code signing section and make sure you have selected your distribution profile.
Another thing you may need to do is create an entitlements file, declare this under 'code signing entitlements' as described on the apple page here
http://developer.apple.com/iphone/manage/distribution/index.action
I tried to upload my iPhone application to the App store, but received the following error: The binary you uploaded was invalid. The icon file must be in .png format.
The icon file IS in .png format, size 57x57, so assumed it is a bug and tried to upload with Application Uploader, when I got another error:
Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate.
I followed every single step, and it is not working... it is driving me crazy! Please advise what should I do!
First, check that the icon file is in .png format, rather than .PNG format.
Second, take some deep breaths, look out a window for a few minutes, and then go back over the steps to upload your iPhone application.
Many people were confusing (like me) modifying the code signing property of XCode.
You must ensure that your code signing identity property start with
iPhone Distribution : Developer Name
instead of
iPhone Developer : Developer Name
PS : If you have no option start with iPhone distribution, you didn't get production certificate yet.
Since you haven't mentioned anything regarding the fact that you did sign the code, I'm going to assume you didn't.
You'll need to get your application code signed in order for it to be accepted, so that the phone knows it's from a trusted developer, and not just a virus someone has uploaded.
Do you have a code signing certificate?
I know you are not able to "Build and Go" a build for Appstore distribution using the appropriate certificate since it's not tied to a particular device. What is the actual error message you get when you try to do that?
When I tried to build and go my AppStore distribution, it will attempt to install it on the device and then gave this message: "The executable was signed with invalid entitlements", is that the right message?
I've actually been able to submit my Ad-hoc build to the App Store, and they've approved it. I figured they'd be able to strip off their own DRM to get it prepped for the App Store anyhow; I guess they do. The nice thing about it for me as a dev is I get to build/test the exact binary I'll be shipping off to the App Store.
I can't say it's an approved method, so YMMV.
Or perhaps you were asking something else entirely?