App Store rejection

Ernesto Giannotta erne at apimac.com
Sun Jan 22 16:14:56 CST 2012


On 22-gen-2012, at 22:05, jda wrote:

> 
>> 
>> #####################################
>> # Codesign the libraries
>> #####################################
>> 
>> codesign -f -s "3rd Party Mac Developer Application: <your identity here>" "$app_frmw"/V4CC.framework/Versions/A/V4CC
>> codesign -f -s "3rd Party Mac Developer Application: <your identity here>" -i "com.apimac.notepad.v4cclib" "$app_vcomp"/libvshared_fat_release.dylib
>> codesign -f -s "3rd Party Mac Developer Application: <your identity here>" -i "com.apimac.notepad.v4cclib" "$app_vcomp"/libvkernel_fat_release.dylib
>> codesign -f -s "3rd Party Mac Developer Application: <your identity here>" -i "com.apimac.notepad.v4cclib" "$app_vcomp"/libvclient_fat_release.dylib
>> codesign -f -s "3rd Party Mac Developer Application: <your identity here>" -i "com.apimac.notepad.v4cclib" "$app_vcomp"/libicucore.A.dylib
>> 
>> # WX (required for VREPORT only)
>> #codesign -s "3rd Party Mac Developer Application: Ivan Gobbo" "$app_vcomp"/libwx_mac.dylib
>> #codesign -s "3rd Party Mac Developer Application: Ivan Gobbo" "$app_vcomp"/libvreport_fat_release.dylib
>> 
>> 
>> the -f option will force any previous signature to be removed
>> the -i option adds a bundle identifier to the signature, and it's omitted when signing V4CC because it already has a bundle identifier
>> 
>> 
>> hope this makes sense ;-)
>> 
> Hi Erne,
> 
> I'm trying to make sense of this. Particularly this line
> 
>> codesign -f -s "3rd Party Mac Developer Application: <your identity here>" -i "com.apimac.notepad.v4cclib" "$app_vcomp"/libicucore.A.dylib
> 
> Why use "com.apimac.notepad.v4cclib" ?
> 

it's an arbitrary identifier for the libraries, 

codesign will use the bundle identifier if it finds the appropriate entry in the related info.plist 

V4cc framework is already set up with info.plist and bundle identifier so no need to supply one.

vcomponents dylibs are not bundled so some kind of identifier must be supplied for the to be signed

> Is v4.cclib part of the bundle id?
> 
> Should I just use the bundle id of my app there? My bundle id is
> 
> com.sonnysoftware.bookends.mas
> 
> So should I use 
> 
>> codesign -f -s "3rd Party Mac Developer Application: <your identity here>" -i "com.sonnysoftware.bookends.mas" "$app_vcomp"/libicucore.A.dylib
> 

of course <your identity here> should be replaced with your actual identity

and yes, I guess any identifier should work for signing the libraries

I choose com.mycompany.myapp.v4cclib because it seemed appropriate to me






More information about the Valentina mailing list