builds 2011.681, 2011.689 = not signing( solved) updated xcode to 4.2

Solar2D Daily Builds and Public Releases
#1

Today I found these posts(bottom) that refer to apps possibly getting rejected due to

“openfeint use of non-public updateBadges call”

So I decide to try a daily builds 2011.681 and 2011.689 with the same results

With the daily-builds every time I build it says “Using Custom Build Id f67a…… “

I have tried the following
http://developer.anscamobile.com/reference/troubleshooting
Uninstalling the current build, then I installed the new build

Deauthorizing / reauthorized my computer

Removed anscamobile files in ~/library/Preferences/ folder:

I tried to add the apps name into the building settings plist

plist =
{
CFBundleIdentifier = “com.website.appname”

I used to be able to build for devices fine. Nothing has changed with my provisionary profiles or certificates
I have spent half my day trying to solve this; please do not suggest using a different build, very frustrating.

http://developer.anscamobile.com/forum/2011/10/19/openfeintios5-itunes-warning-non-public-selector

http://developer.anscamobile.com/forum/2011/11/11/apple-rejecting-open-feint-apps

http://support.openfeint.com/dev/updatebadge/

[import]uid: 89663 topic_id: 18062 reply_id: 318062[/import]

#2

sorry I forgot after it builds corona says

Your application built but failed to pass Apple’s validation tests.

Your application cannot be uploaded to the App Store until it passes Apple’s validation tests, though you may install it directly to provisioned devices.

warning: Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)
failed to extract requirements data: 1
/Users/ezra/Desktop/appname.app: code or signature modified
failed to extract entitlements: 1

  • (null)
    [import]uid: 89663 topic_id: 18062 reply_id: 69030[/import]
#3

I think the custom build id message is normal, especially for a daily build.
Generally your error message happens when there is a problem with your provisioning profile or certificates. Please make sure that your provisioning profiles or certificates haven’t expired. Also make sure you don’t have any duplicate entries (in Xcode Organizer or Keychain Access). Duplicate entries confuses the Xcode signing process.

[import]uid: 7563 topic_id: 18062 reply_id: 69034[/import]

#4

No Duplicate entries
No expired provisioning profiles or certificate
All certificates set to “use system default” in keychain.

I also tried what was listed over here

http://developer.anscamobile.com/forum/2011/03/16/application-failed-codesign-verification-over-and-over-again-ugh

Bruce Martin

  1. Go to the Keychain Access Program.
  2. Under “login” and “Certificates” first make sure you have the complete and correct collection of certificates.
  3. Right click the iPhone Developer certificate and select “Get Info”
    Under the “Trust” section make sure “When using this certificate” is set to “Use System Defaults”.
  4. Click the caret for the iPhone Developer sub category
    Double click on the private key and set “Access Control” to “Allow all bla bla bla…”
  5. Right click the iPhone Distribution certificate and select “Get Info”
    Under the “Trust” section make sure “When using this certificate” is set to “Use System Defaults”.
  6. Click the caret for the iPhone Distribution sub category
    Double click on the private key and set “Access Control” to “Allow all bla bla bla…”
    After these steps, a test build still generated the same error. Next I did this:
  7. Right click the Apple Worldwide Developer Relations Certificate and select “Get Info”
    Under the “Trust” section make sure “When using this certificate” is set to “Use System Defaults”.

I made an assumption that “the custom build id” was the cause of “Your application built but failed to pass Apple’s validation tests.” Is this correct?
[import]uid: 89663 topic_id: 18062 reply_id: 69039[/import]

#5

I reinstalled build 2011.591 and everything works fine which makes me think my certificates and profiles are fine. However I need to use a newer build due to openfeints api rejections problem [import]uid: 89663 topic_id: 18062 reply_id: 69042[/import]

#6

No the custombuildid is completely unrelated. But you should get a different custom build id for every different daily build version you use. (You might want to verify this.)

On the command line, run
xcode-select -print-path

Make sure the path points to the correct version of Xcode. [import]uid: 7563 topic_id: 18062 reply_id: 69049[/import]

#7

I have only ever installed one version of xcode version 3.2.4
xcode-select -print-path shows the path to be
/Developer
Which is where my xcode is installed.

any other ideas?
[import]uid: 89663 topic_id: 18062 reply_id: 69059[/import]

#8

Is there any other console output?

We don’t test Xcode 3.2.4. We have Xcode 3.2.6 for local automated testing, but we only use developer keys with that, and Xcode 4.2 is also on that machine so it could be the code signing is actually done via Xcode 4.2 on that machine.
[import]uid: 7563 topic_id: 18062 reply_id: 69094[/import]

#9

Thinking about it some more, if you go back several more builds, that coincides with when we upgraded our build machine to Lion, Xcode 4.2, and the iOS 5 SDK. Based on what you have said, my guess is that you should upgrade to Xcode 4.2.
[import]uid: 7563 topic_id: 18062 reply_id: 69097[/import]

#10

Using Custom Build Id 178ade912ceb884581439f3de69dc890
Using additional build settings from: /Volumes/Build-appname/appname/build.settings
2011-11-22 01:50:40.975 defaults[3979:607]
There is no (ContentOrientation) default for the (/Users/ezra/Desktop/appname.app/Info) domain.
Defaults have not been changed.
2011-11-22 01:50:41.026 defaults[3980:607]
There is no (UISupportedInterfaceOrientations) default for the (/Users/ezra/Desktop/FartBugs.app/Info) domain.

/Users/ezra/Desktop/appname.app: replacing invalid existing signature
codesign_allocate: for architecture armv6 object: /Users/ezra/Desktop/appname.app/appname malformed object (unknown load command 9)
/Users/ezra/Desktop/appname.app: object file format invalid or unsuitable

adding: appname.app/ (stored 0%)

i revoked and re-issued cert and profiles, no change, same error [import]uid: 89663 topic_id: 18062 reply_id: 69099[/import]

#11

yeah that is probably what i will try next. [import]uid: 89663 topic_id: 18062 reply_id: 69100[/import]

#12

just tried removing certificates and profiles then reinstalled them. same error

i uninstalled xcode with
sudo /Developer/Library/uninstall-devtools --mode=all

then reinstalled xcode. same error

i have tried building multiple apps. same error

the apps will not install on a device because they are not signed.

can i get a confirmation that new builds work with xcode 3.2.4.
[import]uid: 89663 topic_id: 18062 reply_id: 69089[/import]

#13

Unistalled xcode 3.2.4
sudo /Developer/Library/uninstall-devtools --mode=all

Updated osx 10.6.4 to 10.6.7

Installed xcode_4.2_and_ios_5_sdk_for_snow_leopard.dmg

Builds are being signed and can be installed on devices.

Looks like newer builds are not compatible with xcode 3.2.4
Thx for your help, problem is solved
[import]uid: 89663 topic_id: 18062 reply_id: 69517[/import]

#14

Hey really thanks man ezraanderson and ewing to give a valuable feedback from event i got the same error when i downloaded the corona 2011.704 but now because of you persons i installed ios sdk 5 and xcode 4.2 and solved the error [import]uid: 95072 topic_id: 18062 reply_id: 75041[/import]