libssl.dylib is not signed with an Apple submission certificate...
pinkio75
Member, PRO Posts: 1,221
here the issue:
after upload the game i received the following email:
i've revoked the certificate and reinstall them on my Keychain Access, i've remove the old provision profile of the game and i regenerate it from dev portal and reinstall it on my mac also i've removed my Apple id from xcode5 and i reinsert it but unfortunately i've the same result..."Invalid Signature - the executable at path..."
Now i'm downloading new version of xcode Version 5.1.1 and i hope to solve this issue, anyway someone have a suggestion about this issue?
thanks
Comments
i've update my xcode to 5.1.1 but i'm stuck with this issue...
nothing suggestion about it?
Ciao pinkio dato che probabilmente è un problema di gamesalad perche non invii una mail al gamesalad support o chiami qualche creatore di gamesalad dentro la discusione tramite @nome ?
@Andrea_Comisi
non sono sicuro che dipenda solo da GS, il problema è solo sulle Mac Apps.
@pinkio75 submit a bug and we will look into it
ok, but now i'm testing with NB if i can't i publish the App i will submit a bug, thank you
nothing change i've open a support ticket
cause i've receive the same message...
Dear developer,
We have discovered one or more issues with your recent delivery for "Forest Man". To process your delivery, the following issues must be corrected:
Invalid Signature - the executable at path Forest Man.app/Contents/Frameworks/libssl.dylib is not signed with an Apple submission certificate. Refer to the Code Signing and Application Sandboxing Guide and Technical Note 2206 for more information.
Once these issues have been corrected, you can then redeliver the corrected binary.
Regards,
The App Store team
The issue is located in this file: libssl.dylib,
Anyone have the same issue?
The fix for the bug has been sent to qa. Go to the bug in our data base to get updates on the bug
thanks
Yes same is happening to me, @BlackCloakGS would like a bug fix as soon a possible, thanks guys :-)
It is is a bug. Release Creator 0.12.3 ( Still in beta of this writing ) solved it for me.
http://bugs.gamesalad.com/show_bug.cgi?id=249