October 2011 - MacRuby-devel - lists.macosforge.org

MacRuby App Store Code Signing Issue
by Elliot Temple 13 Oct '11

13 Oct '11

Short version: Getting errors like this emailed from Apple when I submit my app, please help: > Invalid Signature - the executable Hard Platformer.app/Contents/Frameworks/MacRuby.framework/Versions/Current/usr/lib/ruby/1.9.2/date.rbo is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to the Code Signing and Application Sandboxing Guide for more information. Details: I'm submitting a platformer game I made with MacRuby to the Mac App Store. I'm creating a writeup of what I had to do to get it to work which I'll post once it's accepted. I have one issue left I wanted to ask about. At first I got an automated "invalid binary" rejection and was emailed a very long list of invalid signature errors including one for the main app bundle. This is even though I can see Xcode 4.1 is doing code signing like this > CodeSign "/Users/curi/Library/Developer/Xcode/DerivedData/Hard_Platformer-bffekhylxcfntifvgtzszieplvfm/ArchiveIntermediates/Deployment/InstallationBuildProductsLocation/Applications/Hard Platformer.app" > cd "/Users/curi/c/cs/xcode/Hard Platformer" > /usr/bin/codesign --force --sign "3rd Party Mac Developer Application: Elliot Temple" "/Users/curi/Library/Developer/Xcode/DerivedData/Hard_Platformer-bffekhylxcfntifvgtzszieplvfm/ArchiveIntermediates/Deployment/InstallationBuildProductsLocation/Applications/Hard Platformer.app" So I took the advice here http://astonj.com/tech/how-to-submit-your-macruby-app-to-the-mac-app-store/ and manually signed it > codesign -f -s "3rd Party Mac Developer Application: Elliot Temple" Hard\ Platformer.app/ Which looks to me like the same thing Xcode already did, but whatever. That fixed the signature for the main app bundle and avoided automated rejection. A human reviewer will now look at my app :) But I still got all the other code signing errors emailed to me, and Apple recommends fixing them. Here's some examples: > Invalid Signature - the nested app bundle MacRuby (Hard Platformer.app/Contents/Frameworks/MacRuby.framework) is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to the Code Signing and Application Sandboxing Guide for more information. > > Invalid Signature - the executable Hard Platformer.app/Contents/Frameworks/MacRuby.framework/Versions/Current/usr/lib/libmacruby.1.9.2.dylib is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to theCode Signing and Application Sandboxing Guide for more information. > > Invalid Signature - the executable Hard Platformer.app/Contents/Frameworks/MacRuby.framework/Versions/Current/usr/lib/ruby/1.9.2/date.rbo is not signed, the signature is invalid, or it is not signed with an Apple submission certificate. Refer to the Code Signing and Application Sandboxing Guide for more information. What should I do about those? Or should I ignore them? I'm using the MacRuby Nightly from yesterday night, OS X 10.7.2, Xcode 4.1 Thank you for any help. -- Elliot Temple http://beginningofinfinity.com/

2 1

observable ruby methods
by Alex Greif 13 Oct '11

13 Oct '11

Hi, I bound an array to an NSArrayController and realized that not all array manipulation methods trigger the binding observer. These trigger: += -= This does not trigger << Is there a list which ruby methods cocoa can automatically register as observer for the classes Array, Hash, etc ? Thanks, ALex

1 0

is there a sane way to use/create XPC services via macruby?
by Takao Kouji 12 Oct '11

12 Oct '11

Does Anyone know any idea below? ----- on IRC #macruby channel ----- 03:58 Aphelion: is there a sane way to use/create XPC services via macruby? 11:10 takaokouji: Aphelion: Sorry, I don't know XPC. What is XPC? XML-RPC? 13:08 Aphelion: takaokouji: IPC/sandboxing technology that apple is requiring all mac app store applications to make use of as of the first of next month to get new apps or updates approved 13:10 Aphelion: takaokouji: so if you need to talk to the network, you create a service with permission to do so and the main application remains completely sandboxed, only communicating with the service. or if you need to interact with another app via apple events, you make a service that does this and communicate with that. it's to decrease the potential surface area of any given vulnerability. 13:11 Aphelion: takaokouji: and, well... there's no choice in the matter. nothing will make it into the app store without using app sandboxing at least, which realistically means making use of xpc services, as of the first of next month. period. ----- --- TAKAO Kouji <kouji(a)takao7.net> blog: http://d.hatena.ne.jp/kouji0625/ twitter: takaokouji / projects: ruby, s7-seven

3 2

Progress towards 1.0?
by Dave Baldwin 11 Oct '11

11 Oct '11

Hi, I have been away from MacRuby dev for about 6 months and I am looking to start again and I was wondering if it is still a viable development platform as development seems to have stalled. It has been a long time since the last release and looking back through the list archives I see Laurent seems to have disappeared and the main regular contributor to the git repository is watson1978. None of this is a criticism as I know how open source project wax and wane but I still live in hope MacRuby will become the main way to develop Cocoa apps in the future especially as it is being accepted into the mac app store. Dave.

2 1

Using ORM with MacRuby
by Jon Doud 11 Oct '11

11 Oct '11

I am trying to use Sequel, ActiveRecord or Datamapper with MacRuby and XCode. So far I haven't had any success. Environment: XCode 4.2 Beta MacRuby 0.10 and 0.11-nightly Sequel 3.28 ActiveRecord 3.0.10 Datamapper 1.1.0 Sqlite3 1.3.4 Sqlite-ruby 1.3.3 Both ActiveRecord and Sequel die in IRB (segmentation fault: 11) when I try to access the data table. Datamapper doesn't even load in IRB for me. Has anyone had any success with any ORM in XCode? - Jon

4 5

Re: [MacRuby-devel] NSInvocationOperation usage Segmentation fault
by Mateus Armando 11 Oct '11

11 Oct '11

Hi Alex, this works for me! 1. Alternativ framework 'Foundation' class Foo def bar puts "hallo" end end queue = NSOperationQueue.alloc.init #queue.addOperation operation queue.addOperationWithBlock ->{ Foo.new.bar } NSRunLoop.currentRunLoop.runUntilDate(NSDate.dateWithTimeIntervalSinceNow(2.0)) _____________________________________________________________________ 2. Alternativ class Foo < NSOperation def main p :hallo end end queue = NSOperationQueue.alloc.init operation = Foo.new queue.addOperation operation NSRunLoop.currentRunLoop.runUntilDate(NSDate.dateWithTimeIntervalSinceNow(2.0)) _____________________________________________________________________ 3. Alternativ framework 'Foundation' class Foo def bar p :hallo end end queue = NSOperationQueue.alloc.init operation = NSInvocationOperation.alloc.initWithTarget Foo.new, selector: :bar, object: nil queue.addOperation operation NSRunLoop.currentRunLoop.runUntilDate(NSDate.dateWithTimeIntervalSinceNow(2.0)) Mateus > The following code crashes with a segmentation fault. > Any idea whether I misunderstood the usage or it is a macruby bug? > > thanks, > ALex. > > ---code------------------------------------------- > framework 'Foundation' > > class Foo > def bar > puts 'bar' > end > end > > operation = NSInvocationOperation.alloc.initWithTarget Foo.new, selector: > 'bar', object: nil > > queue = NSOperationQueue.alloc.init > queue.addOperation(operation) > > # run the main loop for 2 seconds > NSRunLoop.currentRunLoop.runUntilDate(NSDate.dateWithTimeIntervalSinceNow(2.0))

1 0

NSInvocationOperation usage Segmentation fault
by Alex Greif 11 Oct '11

11 Oct '11

The following code crashes with a segmentation fault. Any idea whether I misunderstood the usage or it is a macruby bug? thanks, ALex. ---code------------------------------------------- framework 'Foundation' class Foo def bar puts 'bar' end end operation = NSInvocationOperation.alloc.initWithTarget Foo.new, selector: 'bar', object: nil queue = NSOperationQueue.alloc.init queue.addOperation(operation) # run the main loop for 2 seconds NSRunLoop.currentRunLoop.runUntilDate(NSDate.dateWithTimeIntervalSinceNow(2.0))

3 3

Re: [MacRuby-devel] NSInvocationOperation usage Segmentation fault
by Sean Mateus 11 Oct '11

11 Oct '11

Hi Alex, try to use: operation = NSInvocationOperation.alloc.initWithTarget Foo.new, selector: ':bar', object: nil the only change is that the selector is a Symbol now! I'm not on any OS X devices so I can't test this! but I hope it'll work! Grüßen aus Köln Sean Mateus >> The following code crashes with a segmentation fault. >> Any idea whether I misunderstood the usage or it is a macruby bug? >> >> thanks, >> ALex. >> ---code------------------------------------------- >> framework 'Foundation' >> class Foo >> def bar >> puts 'bar' >> end >> end >> operation = NSInvocationOperation.alloc.initWithTarget Foo.new, selector: >> 'bar', object: nil >> queue = NSOperationQueue.alloc.init >> queue.addOperation(operation) >> # run the main loop for 2 seconds >> NSRunLoop.currentRunLoop.runUntilDate(NSDate.dateWithTimeIntervalSinceNow(2.0))

1 0

Re: [MacRuby-devel] macruby NSTask problem
by Colin McPhail 11 Oct '11

11 Oct '11

Alex Greif wrote ... > I tried the subprocess sample with the AsyncHandler from > http://ofps.oreilly.com/titles/9781449380373/_foundation.html > and found the following problem: > if I execute the code many times (I tried 20 times) in my terminal with > $ macruby sample.rb > then 2-3 times it does not print any output. In this 10% the data_ready: > method of the AsyncHandler is not called. > > Is this a macruby problem or an NSTask problem? It may be that the order of delivery of the data_ready and task_terminated notifications is indeterminate. I modified the task_terminated handler to set a 'terminated' flag rather than call exit. At the bottom of the example I executed the run loop in 1-second slices until the terminated flag was set and then executed it for one more second in case the data_ready notification hadn't arrived yet. Under light testing this seemed to give the expected result consistently. Note that the example has another small defect: it issues only one readInBackgroundAndNotify call. If the task produces a lot of output not all of it will necessarily be delivered by this single read. The data_ready handler should really issue a further readInBackgroundAndNotify I think. Regards, -- CMcP

1 0

performSelectorOnMainThread Problem
by Alex Greif 10 Oct '11

10 Oct '11

The xcode documentation states that if the method performSelectorOnMainThread has the argument withObject:nil, then the nil means that the target method takes no arguments. The following code throws an ArgumentError wrong number of arguments (1 for 0): def foo self.performSelectorOnMainThread(:'bar', withObject:nil, waitUntilDone:true) end def bar # some gui change end But it works fine if I add a dummy argument to the bar method and change the selector to 'bar:' like def foo self.performSelectorOnMainThread(:'bar:', withObject:nil, waitUntilDone:true) end def bar(dummy) # some gui change end Is this a bug, or do I really need the dummy argument in the target method? Thanks, Alex.

2 1