Re: Appstore rules on symlinks Macruby framework changed ?
Yes, i have seen that .. i will do some tests to see if i can get a working app with a symlink although a manual
change did not succeed thus far .. either it cannot find macgems (if i hack the binary with "A") or it just
crashes because it can not find "Current" through the simlink any more
and yes, it seems that apple is really stretching their rules to the limits .. i sensed some disturbance in
the python community as well with similar issues the last few days … the response from the review team was :
- - - - -
Dear developer,
We have discovered one or more issues with your recent delivery for "SubtitleReSync". To process your
delivery, the following issues must be corrected:
Malformed Framework - The framework bundle MacRuby
(SubtitleReSync.app/Contents/Frameworks/MacRuby.framework) 'Versions' directory must contain a
symbolic link 'Current' resolving to a specific version directory. Refer to the Anatomy of Framework
Bundles for more information.
- - - - -
The funny thing is that i have another framework but didn't bother to create a "cute" one so i just dumped the
.dylib into Frameworks. That seems to be allowed and ok :)
I will file a bug report as well
cheers, Rob
>
> macruby_deploy fiddles with the version symlinks on purpose. We changed it in the past for app store
guidelines at some point; you should be able to see it in the history of macruby_deploy.
>
> It would be fastest to just revert that change and see if that fixes things. Though if Apple really wants the
version to be A then we will need to do a bit more work.
>
> macruby_deploy is fairly straightforward, so it is easy to go through and find what needs to be changed.
>
>
> Sent from my iDevice
>
> On 2012-05-07, at 9:38, Joshua Ballanco <jballanc@...> wrote:
>
>> Hi Rob,
>>
>> I haven't had time to look into it, but hopefully Apple is not looking to restrict versions within
framework bundles to "A", "B", "C", etc. As for "Current" not being a symlink, that does seem like a bug.
Would you mind filing it as such so that we don't loose track of it?
>>
>> - Josh
>> On Saturday, May 5, 2012 at 8:27 PM, Rob Ista wrote:
>>
>>> Hi all,
>>> it seems that the Appstore validation has sharpened its control (again) ? submitting an app now is
rejected because the Macruby framework does not comply to the official Anatomy of Framework Bundles ?
There should be a symbolic "Current" resolving to "A" ... in the Macruby Framework this is now a fixed
"Current" .. does anyone have seen this before and is there a workaround for the time being ?
>>>
>>> Secondly, the code signing of the bundle contents is still a bit shaky although it seems to work on Lion ..
on SL the .rb files create an "argument list too long" message (see below) .. commenting out the .rb files in
macruby_deploy for codesigning makes the deploy come to a proper end but of course now the .rb are not
signed. Daniel has done some great work on this already but are there any other ideas?
>>>
>>> rgrds, Rob
>>>
>>>
/Users/robista/Library/Developer/Xcode/DerivedData/SubtitleReSyncBasic-ayrbtqtujxpvspgaanykiwlaojxy/ArchiveIntermediates/Deployment/BuildProductsPath/Release/SubtitleReSyncBasic.app/Contents/Frameworks/MacRuby.framework/Versions/Current/usr/lib/ruby/1.9.2/abbrev.rb:
Argument list too long
>>> _______________________________________________
>>>
Jean-Denis
RSS Feed