Bob,<div><br></div><div>I&#39;ve deployed to the App Store without issue. Are you using the --embed argument for the Deployment target?</div><div><br></div><div>dw<br><br><div class="gmail_quote">On Thu, Sep 20, 2012 at 11:47 AM, Robert Carl Rice <span dir="ltr">&lt;<a href="mailto:rice.audio@pobox.com" target="_blank">rice.audio@pobox.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The silence is defening!<br>
<br>
Is anyone able to get a compiled and sandboxed MacRuby project accepted to the App Store?<br>
<br>
If I understand how macruby_deploy works then it seems that it is trying to duplicate a lot of work that Xcode does by post-processing an Xcode application package. It also seems to me that it would solve my problem it I could include a source code bundle for the  macruby runtime in my project so that Xcode would build it correctly with sandboxing enabled. Then I would need an option for macruby_deploy to not overwrite the executable, or, better yet, a macruby pre-compiler that I could invoke from the Xcode &quot;Build Rules&quot;. Then I wouldn&#39;t need to run macruby_deploy and the build should even run faster since code signing would only run once.<br>

<br>
So what don&#39;t I understand about macruby_deploy?<br>
<br>
Thanks,<br>
Bob Rice<br>
<br>
_______________________________________________<br>
MacRuby-devel mailing list<br>
<a href="mailto:MacRuby-devel@lists.macosforge.org">MacRuby-devel@lists.macosforge.org</a><br>
<a href="http://lists.macosforge.org/mailman/listinfo/macruby-devel" target="_blank">http://lists.macosforge.org/mailman/listinfo/macruby-devel</a><br>
</blockquote></div><br></div>