Build failed

Picked up Stencyl again last night, and things have definitely moved forward! I loaded a game which has been built and submitted to App Store, but in 3.4 it´s not very welcome. Loaded, converted, cleaned, but failed to build.
I am on Mac, El Capitan, Stencyl latest build, Xcode 7.0.1,   Command Line tools 10.10 and Java 8.60.
Log attached.
Not sure, but it seems it does not find fonts that are really there....

Tried loading the generated xcodeproject into Xcode, but it fails like this. See attached screendump.

Logs are pointing to these behaviors as problematic, and the editor might highlight the blocks that are causing this. Have you taken a look at them?

KlikkGhost
DragActor

Code: [Select]

2015-10-14 12:57:06,641 INFO  [Thread-53] stencyl.sw.util.StreamGobbler: [haxelib] ../../../../Source/scripts/Design_95_95_KlikkGhost.hx:104: characters 8-15 : Int should be String
2015-10-14 12:57:06,642 INFO  [Thread-53] stencyl.sw.util.StreamGobbler: [haxelib] ../../../../Source/scripts/Design_106_106_DragActor.hx:104: characters 20-62 : Float should be Int
2015-10-14 12:57:06,642 INFO  [Thread-53] stencyl.sw.util.StreamGobbler: [haxelib] ../../../../Source/scripts/Design_106_106_DragActor.hx:104: characters 20-62 : For function argument 'layerRefType'


Thanks, Jon, I will. :-)

Jon, this may or may not be relevant, but it seems to me that stray blocks now may create errors. I´ve reloaded and tested four previously finished apps and run into stops. After going through  behaviors and cleaning up stray blocks (which I have  been a bit sloppy with leaving around. you never know..) the compiler runs through and apps run on simulator. Others may avoid errors by being aware of this, I think. (And generate less noise about stops in compiler, too) :-)

If you can reproduce that on a simple test game, could you attach that test game here?

Will try, but I found another interesting stop while reviving my apps:
The "old" block  "Send Actor to  Layer with ID"  gives  error "not enough arguments".
Replacing it with the same block, and using the same arguments, in my cases Last created Actor and ID 1 (as text) removed the error and StreamGobbler is gobbling. :-)
Edit:
Confirming this. Replacing "Send Actor to Layer with ID" with same "new" block solves error and stop.