Hello Robert,

I'm glad to hear you finally solved your problems :)

Would you mind telling us when your application in on the App Store? I think it's good to see what other people are building with Macruby to motivate more people to start using it :)

Rgards,

Mark.

-- 

Mark Villacampa

Twitter: @MarkVillacampa

On Saturday, September 29, 2012 at 9:54 PM, Robert Carl Rice wrote:

Hi Daniel,

I think that my earlier problems with macruby_deploy were due to a corrupted Xcode project file. It finally became corrupted to the point where Xcode wouldn't open it. After rebuilding it using the latest Macruby project template, I had no problem submitting my app to the Mac App Store.

Thanks,

Bob Rice

On Sep 21, 2012, at 4:27 AM, Robert Carl Rice <rice.audio@pobox.com> wrote:

Hi Daniel,

I have an update. If I add the --no-stdlib argument along with the --embed, then my archive passes validation but doesn't run. I only see an "Exited with code: 1 error in the console log. Is there a way to get an error message to determine only what I need from the framework?

Thanks,

Bob Rice

On Sep 20, 2012, at 3:50 PM, Robert Carl Rice <rice.audio@pobox.com> wrote:

Hi Daniel:

When I use the arguments:

--compile --codesign "3rd Party Mac Developer Application: Robert Rice"

I get an app bundle that runs and passes validation but then is rejected as an "invalid binary" because the executable doesn't enable sandboxing.

When I add the embed argument:

--compile --embed --codesign "3rd Party Mac Developer Application: Robert Rice"

I get an app bundle that runs but fails validation with the error:

“Deployment” does not contain a single–bundle application or contains multiple products. Please select another archive, or adjust your scheme to create a single–bundle application.

My app could be submitted for review if I don't compile the ruby source.

Thanks,

Bob Rice

On Sep 20, 2012, at 3:32 PM, Daniel Westendorf <daniel@prowestech.com> wrote:

Bob,

I've deployed to the App Store without issue. Are you using the --embed argument for the Deployment target?

dw

On Thu, Sep 20, 2012 at 11:47 AM, Robert Carl Rice <rice.audio@pobox.com> wrote:

The silence is defening!

Is anyone able to get a compiled and sandboxed MacRuby project accepted to the App Store?

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 "Build Rules". Then I wouldn't need to run macruby_deploy and the build should even run faster since code signing would only run once.

So what don't I understand about macruby_deploy?

Thanks,
Bob Rice

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macruby-devel

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macruby-devel

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macruby-devel

_______________________________________________

MacRuby-devel mailing list

MacRuby-devel@lists.macosforge.org

http://lists.macosforge.org/mailman/listinfo/macruby-devel

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macruby-devel