Any IntelliJ IDEA Users here? Debug vs Release issue in ScoutCC

retropunk

I am compiling AIR to iOS using IntelliJ and testing in Scout CC
No matter what I do the SWF Type says Debug in the Scout CC Session Info Panel

I checked the IntelliJ forum and they told me that by installing or uninstalling the Debug Player would allow me to target the installed player when exporting.

That seems to be like a whole lot of trouble.

Has anyone here had the same issue with Scout reporting a Debug SWF type?

Thanks

Patrick

santiagoIT

I use IntelliJ as well. I don't have any experience with Scout CC though.

In my module Compiler Options I use these two compiler options:

-define=CONFIG::DEBUG,true -debug=true

For release builds I set those to false.

I also uncheck the 'Generate debuggable SWC' option that displays in the same Compiler Options dialog.

retropunk

Can you post a screenshot of your compiler window?
I haven't seen the compiler options written like that
usually I see this pattern
-debug=true
-swf-version=25
-advanced-telemetry=true

Here is what I added and it still runs the debugger
-define=CONFIG::DEBUG,false
-debug=false

santiagoIT

retropunk

so your true settings create a Debug version?
To create a release you set those to false?

What are you using to test if the SWF is a release version and not debug?

No matter what I do I get a debug version according to Scout.

Are you compiling for Mobile or Desktop/Web?

retropunk

I did a test with Flash Builder and FDT.
Both create release and/or debug version easily.

I'm not sure why IntelliJ doesn't have the same options.
Typing -debug=false in the additional compiler area doesn't seem to matter when compiling to iOS and Android.
It always shows up as debug.

I'll report back if I figure out a solution.

Alesys

I didn't noticed this before, but you are right. It produces debuggable SWFs and now I have to update 4 apps that are live with those settings, damn.

retropunk

if you figure out how to create release and debug SWFs in IntelliJ please let me know.
I tried for a couple of hours last night and I couldn't get it.

Flash Builder and FDT allow this switch very easily. IntelliJ has TONS of options, why not this one?

Thanks and good luck @Alesys

Patrick

Alesys

It also lacks an option or a way to pack a x86 APK.

It seems to me that the only way to keep using IntelliJ is handling the compiling and packing via command line while they fix this.

I have never compiled by command line so I'm not sure how helpful is this link since it was made before ASC2 compiler was released.

http://help.adobe.com/en_US/flex/mobileapps/WS19f279b149e7481c-24dc70c812b9cbf7285-8000.html

I'll come back when I've done a successful test.

Thank you Patrick and good luck to you too!

Rolf

retropunk

Yes, this is another reason why I might switch back to FDT again 🙁
such a pain!

I've seen scripts on how to build via ANT but I don't know enough about it.
Someone showed me once a while back and it looked super easy.
It's a matter of getting the syntax right in the XML

Josh Tynjala seems to use ANT quite a bit to compile. Maybe he can shed some light on it.

🙂

retropunk

btw I just did a test with my latest project which is about 75 megs as an IPA file.
When I check the stats on load this is the difference.

Using IntelliJ I attempted a release build but still get the debug build no matter what.
Stats are - MEM 11.2

Using FDT to create a release build
Stats are - MEM 6.4

Thats a HUGE difference to me...for now I will stick with FDT until IntelliJ works out this issue.

Alesys

This is what I've found out until now.

I managed to get the command line and the XML that IntelliJ uses. In both, the XML and the command line, debug is set to false. So, it is supposed to produce a non-debug SWF.

I will try to get the command line generated for the packaging, but even if -target is set to apk-debug it shouldn't affect the SWF but the runtime.

Alesys

I still haven't been able to get the packaging command line from IntelliJ but ran some tests with SWF Investigator.

I ran it with a SWF before and after packing. And none of them shown the tag EnableDebugger2 (but they do if I enable the option in IJs interface or by adding the option to the compiler).

So, in theory those SWFs are not compiled with the debug flag.

retropunk

I downloaded 4 AIR/iOS apps from the App Store and ran them through Scout CC.
They all say the SWF type is debug.

I'm starting to think Scout has the problem. 🙂

tsangwailam

I also struggling to package the x86 apk. I don't want to switch other IDE. Hope intellij fix the problem soon.

Alesys

Finally managed to get the command line for the packaging.
-target is set to apk‑captive‑runtime so, everything seems to be fine.

So, I did what I should have done first. Created an empty project in both: IntelliJ and Flash Builder. And both are just fine (same memory usage, etc.).

Maybe the reason is not the compiling / packaging, maybe an ANE or a SWC is causing this (although I don't know if this is even possible).

retropunk

update:
after creating a basic release build, a sample Hello World with Starling/AIR/iOS with the following IDE's:
Flash Builder 4.7, FDT, Flash Develop and IntelliJ

Scout CC always reports DEBUG SWF via Desktop emulator or on the device directly.

I logged a bug here but haven't seen too much noise on it yet
https://bugbase.adobe.com/index.cfm?event=bug&id=3808342

It's been annoying having to explain to our QA team that the release build is "not really" a Debug build and tat Scout CC has a bug

Please vote for this if you are having this issue.

Thanks

Patrick

mr_mmmmore

Hey Alesys, how did you manage to get the adt commands used by IntelliJ IDEA?

I have been using it happily for a year but I am now working on a project where I need a more sophisticated build process and it's a real pain with IDEA... I wanted to mix build and run configurations with ant scripts, and the whole process is awkward and really I don't get that "I-can-build-exactly-how-I-want" feeling I had when I was using FDT years ago.

I was considering setting a full-ant build process but I don't have the time to rebuild all the adt commands using ant. If I had a work base like the commands involved in the IDEA build and run configs that would be a different story...