App Store rejection - icu resign, vkernel not touch

Ruslan Zasukhin ruslan_zasukhin at valentina-db.com
Sun Jan 29 15:34:05 CST 2012


On 1/29/12 12:50 PM, "Ernesto Giannotta" <erne at apimac.com> wrote:

Hi Ernesto,

I did say, but it seems this was not heard.

* I think you need resign icu. And this step works fine. You say.
This is require to remove certificates of apple.

* DO NOT sign at all vkernel.  You self told, this is not required step YET.

-----
In future builds of vkernel and other dylibs we can use that linker switch,
To increase HEADER SIZE to 4096.


> Yep jon, it's an arbitrary string i pass to the -i option to identify the lib
> being signed.
> I put in one that fits well with my app, and forgot to point out you should
> make yours.
> 
> In your example you are identifying the lib with the path to your lib but the
> command is missing which lib you're going to sign.
> 
> I guess this is a no-op. You can verify if your library is correctly signed
> with the codesign -d <path to lib> command
> 
> 
> On 25-gen-2012, at 00:42, jda wrote:
> 
>> 
>>> 
>>>> install_name_tool: for architecture x86_64 object:
>>>> /Developer/Cocoa/Builds/Release/Apimac
>>>> Notepad.app/Contents/vcomponents/libicucore.A.dylib malformed object
>>>> (unknown load command 8)
>>> 
>>> I can fix this getting rid of the change id of icu command
>>> # change id of ICU dylib
>>> #    install_name_tool -id
>>> "@executable_path/../vcomponents/libicucore.A.dylib"
>>> "$app_vcomp"/libicucore.A.dylib
>>> 
>>> 
>>>> codesign_allocate: can't allocate code signature data for:
>>>> /Developer/Cocoa/Builds/Release/Apimac
>>>> Notepad.app/Contents/vcomponents/libvkernel_fat_release.dylib (for
>>>> architecture i386) because larger updated load commands do not fit (the
>>>> program must be relinked using a larger -headerpad value)
>>>> 
>>>> 
>>>> /Developer/Cocoa/Builds/Release/Apimac
>>>> Notepad.app/Contents/vcomponents/libvkernel_fat_release.dylib: object file
>>>> format unrecognized, invalid, or unsuitable
>>>> 
>> 
>> Erne, what's the purpose of "com.apimac.notepad.v4cclib" in
>> 
>> codesign -f -s "3rd Party Mac Developer Application: <your identity here>" -i
>> "com.apimac.notepad.v4cclib" "$app_vcomp"/libvkernel_fat_release.dylib
>> 
>> I don't see that in other example I found on the web. When I remove it and
>> use (my equivalent for my app)
>> 
>> codesign -f -s "3rd Party Mac Developer Application: <your identity here>" -i
>> "$app_vcomp"/libvkernel_fat_release.dylib
>> 
>> the signing process goes well (no complaints from Terminal).

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]




More information about the Valentina mailing list