ERROR IMS-9000: Invalid code signing viewer.app/viewer

Hi Mark
I found 4 items of error on uplaod app.
1. Apple's web service operaation was not successful
2. Unable to authenticate the package:875829473.itmsp
3. Error ITMS-9000:"Invalid code signing: The exutable " viewer.app/viewer
4. Could not start delivery: all tranports failed diagonostic
5. Warning ITM-9000 versiion mismatch Neither CFBundler version 30.2.0.12.95964 nor ...
Pls.advise me.
Thank you.
Supawan Lee

I think we're missing the full error in point 3 but it looks very similar to this thread: 'Re: error itms-9000 invalid code signing viewer.app/viewer'

Similar Messages

  • Error itms-9000 invalid code signing viewer.app/viewer

    Salve sto provando a generare la mia prima app con dps (adobe CC), credo di aver seguito correttamente l'intera procedura, tuttavia nel momento in cui tento con l'app Loader di sottomettere ad Apple l'app generata, ricevo questo messaggio come feedback.
    Cosa sbaglio? Come si risolve?
    Grazie

    but APP Builder ask me two time the mobileproviosn... one in the last step to build the app and than to sign it to download! i put the same mobileprovision file but it generate the error!!
    I read the DPS guide step by step and it write:
    “The distribuition mobile provisioning file information will be entered automatically for you”
    but is not true.... where i can found that file?? i don't understand sorry..
    Thanks a lot
    Tkart

  • What does this mean and how do I fix it? Error ITMS-9000 "Invalid Code Signing The executable ´viwer.app/ viewer´ must be signed with the certificate that is contained in the provisioning profile"

    What does this mean and how do I fix it? Error ITMS-9000 "Invalid Code Signing The executable ´viwer.app/ viewer´ must be signed with the certificate that is contained in the provisioning profile"

    If you had Firefox save your Yahoo password, first try deleting that here:
    orange Firefox button ''or'' classic Tools menu > Options > Security > "Saved Passwords"
    The "signed out" message seems to be related to how Yahoo authenticates you. Some users have reported that disabling automatic proxy detection solves the problem, and it also resolves an issue of getting logged out every few minutes, if you have ever experienced that.
    To make the change:
    orange Firefox button ''or'' classic Tools menu > Options > Advanced
    On the "Network" mini-tab, click the "Settings" button, then choose "No Proxy" and OK your way back out.
    If your work connection requires you to use a proxy server, try the "Use system settings" option instead.
    Does that help?

  • Solution to ERROR ITMS-9000: "Invalid Code Signing."

    I am using FlexSDK 4.13 and AIR SDK 15.0.302. I installed the FlexSDK and AIR SDK with the Apache Flex installation binary on a Windows Vista 64-bit machine.
    I can build and run an ad-hoc version of my iOS app on an iPhone 4 (iOS 8.0.2) and iPad 2 (iOS 8.1). When I build a release version for the iTunes App Store, and submit it with the Xcode Application Loader. I get the error.
    ERROR ITMS-9000: "Invalid Code Signing. The executable, Payload/YourApp.app/YourApp, must be signed with the certificate that is contained in the provisioning profile."
    I'm using a Mac to submit my app. It is running OS X 10.10 Yosemite and Xcode version 6.1. The Application Loader is version 3.0.
    I suspect that the adt command no longer creates a payload with the correct entitlements. This post illustrates how I resigned my app so that the iTunes App Store would accept it.
    First, I copied my IPA file to my iMac. Then I changed directories to the location of my IPA file.
    Open a text editor and create a file with the name, entitlements.plist.
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>application-identifier</key>
    <string>XAXAXAXAXA.com.yourapp.yourappmobile</string>
    <key>get-task-allow</key>
    <false/>
    <key>keychain-access-groups</key>
    <array>
    <string>XAXAXAXAXA.com.yourapp.yourappmobile</string>
    </array>
    </dict>
    </plist>
    Save this file.
    Start a terminal session. Then type in the following commands.
    unzip YourApp-app-store.ipa
    cp ~/Downloads/YourApp.mobileprovision Payload/YourApp.app/embedded.mobileprovision
    codesign -f -s "iPhone Distribution: YOUR COMPANY NAME (XAXAXAXAXA)" --entitlements Payload/YourApp.app/entitlements.plist Payload/YourApp.app
    zip -qry YourApp-resigned.ipa Payload/
    Note that codesign uses the full key name of your code signing certificate.
    Now you can submit YourApp-resigned.ipa to the iTunes App Store.
    I've seen some people have success with the iReSign App, which you can find at the following URL. I prefer the command line.
    https://github.com/maciekish/iReSign

    but APP Builder ask me two time the mobileproviosn... one in the last step to build the app and than to sign it to download! i put the same mobileprovision file but it generate the error!!
    I read the DPS guide step by step and it write:
    “The distribuition mobile provisioning file information will be entered automatically for you”
    but is not true.... where i can found that file?? i don't understand sorry..
    Thanks a lot
    Tkart

  • ERROR ITMS-9000: Missing Code Signing Entitlements when adding app to Apple App Store

    My client is getting the following error when sending my app (compiled in Flash Pro CC 2014 with AIR SDK 15.0.0.356) to the Apple app store:
    ERROR ITMS-9000: "Missing Code Signing Entitlements. No entitlements found in bundle
    'com.xxxxxx.xx.xxx' for excutable 'payload/xxxxx.app./xxxx'.""
    He is saying that I need to send them the entitlements file.
    I can't find out any information about this with regards to Adobe Air compiled iOS apps, apart from this old post:
    Adding iOS entitlements to AIR apps
    which states that 'the packager configures the entitlements file '
    Can anyone explain what might be missing here?
    Thanks,
    Alan.

    It looks as if this problem is solved by doing step 2 from here:
    http://dev.mlsdigital.net/posts/how-to-resign-an-ios-app-from-external-developers/
    It basically states that the client needs to produce the entitlements file and lists the following that the client will provide themselves:
    A “Mobile Provisioning Profile”
    An “Entitlements.plist”
    An “iOS Distribution Certificate”
    iReSign OS X app (or you could use command line)
    Hope this helps someone. We've run into quite a few problems trying to get the Flash Air compiled App to both enterprise and Apple Store as it can't come from us (the developers) it has to be signed and delivered from the client.

  • Invalid  Code Signing Entitlements "inter-app-audio"

    I uploaded my binary file to the iTunes Connect portal an recived this mesage:
    "Invalid  Code Signing Entitlements - Your application bundle's signature  contains code signing entitlements that are not supported. Please check  your Xcode project's code signing entitlements configuration, and remove  any unneeded entitlements.
    Specifically, key "inter-app-audio" is not supported.
    Once  these issues have been corrected, go to the Version Details page and  click "Ready to Upload Binary." Continue through the submission process  until the app status is "Waiting for Upload." You can then deliver the  corrected binary."
    Does anyone now how to solve this problem?

    Hi,
    did you solve your problem yet??
    I got almost the same error response from application loader.
    However, that series entitlement values was not set by us,
    and I have no idea where is that values come from.
    Does anyone know how to solve this??

  • Error ITMS-9000: Invalid Segment Alignment

    Hello everyone,
    This is my first time submitting an app to the app store.  I've done ad-hoc distribution before, but my client needs this app on close to a thousand of their iPads, and they have corporate offices everywhere, so B2B is the way I have to go.
    Everything is built and tested and works fine. Certificates and Provisioning Profiles are all fine. I am at the last possible step and when I go to submit the .ipa file in Application Loader 3.0, I can't shake this message...
    ERROR ITMS-9000: "Invalid Segment Alignment. This app does not have the proper segment alignment and should be rebuilt with the latest version of Xcode. Please contact Developer Technical Support if you need further assistance."
    Here's the details...
    The app was built in Adobe Flash CC 2014 using AIR for IOS 14.0. I used my PC for the actual building/publishing of the app and then transferred the .ipa file to my Macbook when I tested it and everything was finalized by the client.  Application loader will not let me deliver the app to iTunes connect for submission.  I keep getting this error.
    I've tried everything I can think of.  I've installed Flash CC on my Macbook and tried publishing again.  All the Certificates and Provisioning Profiles were made and downloaded on the Macbook.  I've tried submitting .ipas that were published in AIR for IOS 14.0 and 13.0.  I've tried uninstalling xCode 6 and Application Loader 3 and using older versions.  So far, nothing has worked.
    Has this happened to anyone else?  I'm really in a jam here.  My client needs their app and I can't fix this last issue.  It's very difficult because Adobe Customer Support says that the problem is Apple's Application Loader since the app works fine and distributes without problem ad-hoc.  Apple Customer Support says they can't help either, since the app was built in a 3rd party software and not in xCode.  If anyone can point me in the right direction, that would be amazing.
    Thanks,
    Lee

    There's a huge issue with this on Adobe's developer forums.
    This issue is happening to people everywhere, and it's only been happening for about 20 days or so.  Before that Flash CC apps uploaded fine.
    There is a successful workaround to the problem that a couple of guys came up with, but it's all terminal coding kind of stuff, and that's miles beyond my comprehension.  That kind of coding is way past me, which is why I built it using Flash to begin with, because Action Script is simple.  It would take me longer to figure out the work around that it did for me to build the app itself. lol
    Any other ideas???

  • ERROR ITMS-9000: Invalid Bundle.

    Hi,
    I tried to upload my app to IOS store, but this message comes up each time 'ERROR ITMS-9000: Invalid Bundle.'
    I used
    - AIR 15.0.0.289 beta from adobe lab
    - Xcode 6
    - Application loader 3
    - I built  new certificate and provisioning
    what should I do to solve this problem.

    All,
    If you are you looking to get the patched Windows AIR SDK and facing the download error (509), try this link: https://t.co/C5G23nMPnq
    And what you have to do is copy the /lib/aot/bin/ld64 folder from that version to the same folder on your current AIR build. Doing that, and also adding <key>MinimumOSVersion</key> <string>6.0</string> to your <InfoAdditions> in your XML
    Thanks to @oliver_joyce

  • Solution to ERROR ITMS-9000: "Invalid Segment Alignment."

    I was using Flex 4.13 SDK and AIR 14 SDK. When I build a release version of my iOS app for the iTunes App Store, I received the following error.
    ERROR ITMS-9000: "Invalid Segment Alignment. This app does not have proper segment alignment and should be rebuild with the latest version of Xcode. Please contact Developer Technical Support if you need further assistance."
    To resolve this problem I had to install the Apache Flex SDK with Flex SDK 4.13 and AIR SDK 15.0.302. I installed the FlexSDK and AIR SDK with the Apache Flex installation binary.
    For many of you, this should be enough to rebuild and run your application. However, after I built an ad-hoc version of my iOS app, and transferred it to my iPhone 4 (iOS 8.0.2) and iPad 2 (iOS 8.1), the app crashed immediately after launch.
    If I rebuilt my App in debug mode (-debug-interpreter), it ran correctly.
    However, I found a reference on an Adobe message board to a command line parameter, useLegacyAOT, which indicated that the poster had some success with this command line option after his app crashed.
    I added the option, -useLegacyAOT yes to the build environment.
    This option tells the compiler to disable fast packaging. However, the new linker in AIR 15.0.302 still aligns segments correctly.
    Don't do this unless you have to. But this seemed to work for me, and I was able to submit my iOS App to the iTunes App Store.

    I'm about send application built by Adobe Flash CS6 with AIR SDK 15 for iOS but got error too:
    Error ITMS-9000: "Invalid Bundle. The bundle at 'XX.app' does not contain a bundle executable
    anyone know how solve this issue??

  • IOSApp rejected: Error ITMS-9000 Invalid segment alignment

    I am getting an error while trying to release the application for Apple App Store.
    Error ITMS-9000 Invalid segment alignment
    Following the process flow  mentioned on the link below:
    http://www.raywenderlich.com/8045/how-to-submit-your-app-to-apple-from-no-account-to-app-s tore-part-2
    I am stuck with this for quite sometime now, any help would be greatly appreciated.
    The SDKs and the framework details are as follows:
    Flex SDK 4.12.0
    Apple IOS 8
    Adobe AIR 16

    I'm about send application built by Adobe Flash CS6 with AIR SDK 15 for iOS but got error too:
    Error ITMS-9000: "Invalid Bundle. The bundle at 'XX.app' does not contain a bundle executable
    anyone know how solve this issue??

  • Invalid Code Signing Entitlements

    Dear developers, I was hoping someone could help me out with this.  The last time I updated my ipa for the app store was prior to ios7 and I had no problems.  Now, I tried using the latest version of AIR 3.9 (with Flash cs6) and I tried both with and without the new icons (152, 76) and got the same error.
    ERROR ITMS 9000
    "The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile.  According to the provisioning profile, the bundle contains a key value that is not allowed"
    The error goes on to say something about software assets.
    Have anyone else come across this?  Thank you for your help.
    Justin

    I have had the same problem after upgarding my AIR 3,8 to 3.9
    I reverted back to 3.8 and my app went straight up.
    I cannot get an app to go up with 3.9.
    I don't have the latest xcode but when I did upgrade last time it fixed masses of certificate issues I started getting with FLASH.
    They may not except AIR 3.9 unless you have the latest xcode sofyware.
    I can;t confirm it but the issue looks like it, just like the PIE and icon size warnings.

  • Code signing labview.app in OsX

    I'm trying to sign a built labview.app in  OsX and get the error "unsealed contents present in the bundle root".
    I believe this is due to locating  "AppContents_x64.llb"  outside of the "Contents" folder. 
    From the apple website,since Mavericks :
    ..." In addition, there may not be any content in the top level of a bundle. In other words, if a bundle has a Contents or Versions directory at its top level, there may be no other files or directories alongside them. The one exception is that alongside Versions, there may be symlinks to files in Versions/Current."...
    https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919...
    &#24;One of our programmers sniffed the lvruntime framework; the runtime will load the AppContents.llb if it is reolcated to  the Contents/Resources folder. So, the default location seems incorrect, and the project explorer does not seem to have an option to changed the destination. Does anyone know of a workaround (other than copying the file)?

    Correction_
    The AppContents_x64.llb is NOT found when placed into the Resources folder. On a clean system ( no LV development environment), the app wil run only when that .llb file is in its original location- which invaildates the codesign.  So I'm still unable to sign my app.
    Any suggestions?
    Thanks
    Kevin M

  • Invalid Code Signing Entitlements - Adobe Viewer?

    Hello everybody,
    I have had this problem during the past few days. At this point I need some help because I tried a lot of things to resolve it but it wasn't possible. When I send my App to Apple with 'Application Loader', this error appears again and again:
    I know that it means, but I don't know how resolve it. I created a several new certificates and bundle id, I'm using just roman letters [A-Z, a-z] and numbers... I'm desesperate. I'm writing that here because if you read the lines of the image, you can see that the error is in 'viewer.app/viewer', and that smells like something wrong with Adobe Viewer. It's possible?
    Please, HELP!
    Thanks,
    E.

    Hi Nate,
    Thanks for the email. The issue has been fixed. I had a problem with my mobile provision prefix. Although once I submit the zip file via application loader to the iTunes, shortly after accepting it, they email me (please see attached) some warning with regards to CF Bundler.
    I’ve searched in DPS forum and found out that apparently regardless of this warning, Apple still will publish my app. (although apparently it will take about two weeks for the app to be approved).
    I tried to see if I can rectify this warning, but left it for the moment as it seems it won’t effect on approving and publishing my app.
    Kind regards,
    Calvin Mousavi

  • New ipad 2, unknow error occured when trying to sign into app store

    I just bought this bad boy. I have an apple ID and when I try to download an app it says uknown error occurred.  Also if I try to sign into the appstore through settings it says cannot access itunes i think.  It does have internet connection.

    Apple’s having trouble with the iTunes Store servers right now. Wait for them to resolve the issue.
    (123888)

  • I get "unknown error" when I try to sign in app store, what can I do?  I am using correct password and id verified by getting on this site

    I have a problem connection to app store on iPad2. I get "unknown error" as a message.  Any suggestions on what I can do to fix?

    Sometimes - and I stress sometimes - this can help. Sign out, restart your iPad and sign in again.
    Settings>Store>Apple ID - tap your ID and sign out. Restart.
    Restart the iPad by holding down on the sleep button until the red slider appears and then slide to shut off. To power up hold the sleep button until the Apple logo appears and let go of the button.
    Go back to Settings>Store>Sign in and sign into your account. Then try to update your apps.

Maybe you are looking for

  • How can i change a program from Request/Task ?

    Hi everybody I have a main program in some request/task number and some include in other request/task numer; i want to transport them in the same task. How can i change a program/include from one request/task to other ? Thanks Frank

  • Function Module SO_OBJECT_SEND_API1

    Hi All, In the above Function Module, the exporting parameter DOCUMENT_DATA type SODOCCHGI1 has a field called DOC_SIZE. How important is this parameter and what size is to be assigned and how? How will this affect the final output? Thanks in advance

  • No 5.1 surround. Only L,R,and sub working, can't find setting to adjust

    . I read the knowledge base and it said go to start -> all programs -> creative but creative aint there. I think if I can find the creative settings then I'll probably be able to figure it out from there.

  • BOMM 3.0: ClassCastExeption

    Hi, We have installed BOMM 3.0 and BOE 3.0 (FP1) on a windowsserver 2003 64bit, and with an Oracle 10.2.0.1 32 bit client software. Our repos (AUDIT,BOMM,CMS) are placed in an Oracle 10.2.0.2 64 bit database (on different schemas) on a Solaris server

  • Call For Papers - Session Proposals

    Call for Session Proposals Open Until December 17 The time has come to begin accepting and reviewing session proposals for BrainShare 2011 in Salt Lake City. The Call for Papers (CFP) will be open from now through December 17, 2010 (5:00 PM MST). If