flambe icon indicating copy to clipboard operation
flambe copied to clipboard

Could not parse `flambe.platform.ManifestBuilder.use(build/.cache/air/assets)`

Open accidentalrebel opened this issue 9 years ago • 13 comments

This is the continuation of the problem I've outlined here. The problem was fixed by using a nightly version of Haxe. However, a new problem has appeared and it seems to be a Flambe issue.

--macro:1: character 0 : Could not parse flambe.platform.ManifestBuilder.use(build/.cache/air/assets) --macro:1: character 0 : Unexpected .

The code I am using is below:

haxe -main hyper_app.Main -lib flambe -cp src -dce full --no-traces --macro flambe.platform.ManifestBuilder.use("build/.cache/air/assets") --flash-strict -swf-header 640:480:60:000000 -D native_trace -swf-lib-extern build/.cache/air/admob_all_in_one_6.12.2.ane.swc -swf-lib-extern build/.cache/air/AirFacebook.ane.swc -swf-lib-extern build/.cache/air/Flurry.ane.swc -swf-lib libs/Flurry.swc -swf-version 14 -D air -D ios -D no-flash-override -swf build/.cache/air/main-ios.swf

Thinking that it might be caused by the quotes, I changed:

flambe.platform.ManifestBuilder.use("build/.cache/air/assets")

to

flambe.platform.ManifestBuilder.use('build/.cache/air/assets')

With the above change, no more error appears but unfortunately, I still can't deploy to IOS. Anyone have any ideas?

Some additional notes:

  • I am using the nightly build for Flambe.
  • To make it work with an extension I am using, I am using "-swf-version 14" instead of the default "-swf-version 11.7". Not sure if this affects anything but I thought that it might help out.

accidentalrebel avatar Dec 15 '14 05:12 accidentalrebel

This is probably a shell quoting issue and using single quotes might be the expected solution.

Simn avatar Dec 15 '14 09:12 Simn

You are correct Simn. Changing the double quotes to single quotes removed the error. But nothing seems to be happening after that.

accidentalrebel avatar Dec 16 '14 01:12 accidentalrebel

Found the cause of the problem. I was using Air 15.0.0 and it wan't working well with the IOS deployment of the latest version of Flambe.

To fix: I downgraded to 14.0.0 and removed the "useLegacyAOT=true" in the "index.js" file of the flambe source.

It seems to be working fine aside from a warning that appears:

ld: warning: CPU_SUBTYPE_ARM_ALL subtype is deprecated: C:\Development\Tools
AirSDK\14.0\lib\aot/lib/libNoDebugger1.arm-air.a(avmplusDebuggerStubs.cpp.o)

I'll mark this as resolved.

Thanks everyone~!

accidentalrebel avatar Jan 07 '15 02:01 accidentalrebel

Thanks for the update on this!

markknol avatar Jan 07 '15 21:01 markknol

Is this resolved in the current nightly flambe build or do I need to do as @accidentalrebel is stating?

camaech avatar Jan 14 '15 20:01 camaech

@accidentalrebel I can't seem to find how to remove "useLegacyAOT=true" from "index.js". Could you tell me where I can find the file index.js?

Thanks!! Kreso

kreso22 avatar Jan 15 '15 00:01 kreso22

You need to grab the source (use the hacking instructions in the readme), then remove the line containing -useLegacyAOT in command/index.js.

This is only an interim fix. It will make your app build and run again... but Apple will reject your appstore submission if you use this. I'm working on a proper fix that will allow appstore submissions.

aduros avatar Jan 15 '15 02:01 aduros

Thank you for the answer Bruno. I know flambe is a passion project, but I am just curious if you have any guestimate for this feature?

Thanks again, Kreso

kreso22 avatar Jan 15 '15 02:01 kreso22

Not sure yet, but it's high on my priorities. I would guestimate a week or so.

aduros avatar Jan 15 '15 03:01 aduros

@kreso22 Yeah, sorry if I was vague. As @aduros has mentioned, you need to get the Flambe source and edit from there.

but Apple will reject your appstore submission if you use this. I'm working on a proper fix that will allow appstore submissions.

Ah, so it seems that mine is just a temporary fix. Reopening the issue as it is not fully resolved.

accidentalrebel avatar Jan 16 '15 03:01 accidentalrebel

Any new fixes ready for this issue?

markknol avatar Jan 26 '15 11:01 markknol

Hi, no fix yet? I have a potential deal including iOS version, so it'd be cool to hear something about it :)

apands avatar Feb 13 '15 14:02 apands

Hi, Just wanted to give a quick +1 on this issue. Any word on a fix? Timescale? Thanks

benwager avatar Feb 25 '15 00:02 benwager