I've created a hybrid app, and I'm getting the "application failed codesign verification" message when I try to submit to Apple.
I have built my binary with a Distribution Profile.
Not sure where to turn next. I built using vsnomad from VisualStudio 2012.
Any suggestions will be very welcome!
Cheers,
Andy
OK I'm sorted now. The answer here was that my Developer certificate wasn't the right one... It LOOKED like the right one, no question that here wasn't anything which on the surface was out of order. But Rob from vsnomad RDPd into my laptop and did something by creating a new certificate.
Not the useful answer I hoped to give but never mind, it works. There's so little about hybrid development online, this isn't adding to the knowedge much I'm afraid.
Related
I have an application that uses HealthKit and Swift in it, everything compiles and runs fine when I test it from Xcode on a simulator or a device. I tested, debugged it, and submitted it to the iTunes store. When the application was approved I downloaded the new version from the store and it crashed right away. This was extremely puzzling as I have never had this issue before. I look at the diagnostic and usage logs on my phone and the crash report for the application says this:
Dyld Error Message:
Library not loaded: #rpath/libswiftCore.dylib
Reference from: /path/to/my/app
Reason: no suitable image found.
Did find: /path/to/my/app/Frameworks/libswiftCore.dylib: mmap() error 1 at address=0x100174000, size=0x0194000 segment=__TEXT in Segment::map()
Has anyone seen anything like this or know how to deal with it?
Thank you
EDIT:
The crashing issue magically fixed itself on the morning of October 4th, which tells me that this was an Apple issue. I have been emailing iTunes Connect Support, but they have not said one way or another what happened. I also opened a technical ticket without even a response back from Apple. This is pretty disappointing, not just for the fact that Apple is not being transparent about the issue, but also it makes me feel like I have no course of action later on down the road if this ever were to happen again.
Simply do the following two steps:
1) Delete the App from the device (or simulator)
2) Clean your workspace (CMD+SHIFT+K or via menu Product->Clean)
3) Build and run your app again.
Magically helps every time with all that startup / deploy stuff...
I also often get something like "application not found on device" or signing problems etc. Minutes before everything worked well.
This appears to possibly be a code signing issue on Apple's part, and the issue seems affect apps with embedded frameworks (including non-Swift apps). There are multiple accounts of developers being affected (myself included) who had only submitted an update, without changing any build settings. Some high profile apps appear to have been affected and tickets have been filed with Apple, but there has been no official response from them at this time.
EDIT: This has been confirmed.
Edit:
The app was rejected, after making this change, for the same reason, however, I am confident that the problem has to do with a missing architecture version in the libswiftCore.
I am going to post this as the provisional answer.
Xcode 6 Standard architectures exclude armv7s
Notice how the error says: Did find: /path/to/my/app/Frameworks/libswiftCore.dylib
So it did find the lib but it also says: Reason: no suitable image found.
After running lipo against the archived build it didn't contain armv7s in the swift library, or in the app binary. I manually added it per the link above and the binary now contains support for armv7s though the swift library still did not. My app is in expedited review so I should get feedback farily quick. I will follow up when that does happen.
I had the exact same problem with one of my app version updates (FunKeyBoard 1.1).
After doing some research, looks like it was an Apple side issue for many apps updated on October 3rd. Apple fixed the issue on October 4th by releasing an update, same version number, without needing any fix/re-upload from the app developer.
Obviously an Apple side issue, but I'm surprised Apple is very quiet about it. Many developers, including myself, got angry emails from users, and poor app reviews, as a result.
This error typically occurs when signing Swift apps with certificates that lack "OU" (Organizational Unit). All certificates created after the release of iOS 8 should have this. The simple solution is to create a new certificate to sign with.
For more details, see the official Apple comment here: https://developer.apple.com/library/ios/qa/qa1886/_index.html
It seems that my on the iTunes store is now downloading and opening as expected. From what I have been reading in the Apple Developer Forums, other apps are also working now too. I have not received any word from Apple on why this happened or what caused this. I opened up a technical support ticket with them and I also contacted iTunes Connect support and there is no
explanation or any information on this issue being resolved. This is pretty poor customer service on their part.
I had the same problem. I removed support for arm64 and added armv7s and now apple review team approve the app.
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.
Does anyone know where I can find a complete step-by-step guide for deploying an iPhone app from development tot he app store. I have actually done it before but with the new version of Xcode it is proving difficult.
My ,main problem is with the "Archive". When I validate, I get a lengthy error message. I know it has something to do with my provisioning profile and my keychain, etc. I would like to start over if I can. Apple documentation has never been good at giving you a detailed explanation. Any direction would be greatly appreciated!!
Here is the link you can follow... a step by step Guide... Hope it helps to you.
http://www.edumobile.org/iphone/iphone-programming-tutorials/submitting-iphone-apps-to-the-apple-app-store-a-step-by-step-guide/
I am inclined to reference apple in spite of your statement
Apple documentation has never been good at giving you a detailed
explanation.
Provisioning Portal - Distribution
You can start at the top and work your way down.
Obtaining your iOS Distribution Certificate
Create and download your iOS Distribution Provisioning Profile for App Store Distribution
Creating and Downloading a Distribution Provisioning Profile for Ad Hoc Distribution
Building your Application with Xcode for Distribution
Verifying a Successful Distribution Build
Updating your Application
Sorry if you have actually followed all the steps outlined there and are still having problems.
"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.
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