-
|
Hi! I'm trying to test my application using AIR SDK for MacOS, that running on a virtual machine. I'm using VMWare Latest + Win 11 Latest (host) + MacOS Sonoma (guest). I can build and run my app, but I can't test it as the debugger is not working. The code didn't pause on error. There're nothing on the console (trace outputs) during my test, but sometimes when my app exit, I got this error output: I don't know if this issue happens with a real Mac. Everything else are working properly on the virtual machine: JDK, AIR Runtime, VSCode, Terminal... except this. Maybe related: I've tested with AIR SDK 32, 51 Latest. Same issue. I'm working with VSCode + AS3MXML. Is there anything I can do to make it work? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 17 replies
-
|
As a workaround, to see the console output of compiled application and where the errors appear, I recommend adding junkbyte’s console: https://www.reddit.com/r/as3/comments/lyg16d/junkbyte_console_very_useful_tool_for_tracking/ |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! First time to hear about junkbyte. A handy tool. I also have a similiar tool for capturing traces and error messages. But it's not enough to resolve complex problems. So I need to pause the code execution on error, to use debugger tools (breakpoint, navigating back/ford, viewing properties...) |
Beta Was this translation helpful? Give feedback.
-
|
@ajwfrost Could I get some info about the ADL's exit code Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
When I switch to Air 51.0.1.1, I got this dialog:
I followed this instruction but no luck, still can't connect to the debugger. |
Beta Was this translation helpful? Give feedback.
-
|
Same with Air SDK 51.1.3.4:
|
Beta Was this translation helpful? Give feedback.
-
|
Are you trying to run adl from a terminal? Can you also do |
Beta Was this translation helpful? Give feedback.
-
|
I'm just trying to debug my application using VSCode. This is the output: I got this output in the debug console: ADL exited with code 137 |
Beta Was this translation helpful? Give feedback.
-
|
After I pressed "Show in Finder", I got
I double-clicked to open
I pressed OK. I opened System settings... > Privacy & Security, scroll down:
I pressed
I double-click adl in the Finder again. And I saw this:
I pressed Open. Then:
"Adobe AIR.Framework" can't be opened because Apple cannot check it for malicious software.
I pressed Show in Finder. Then the Finder show the folder and opened a popup again:
Now I pressed OK. Then I see "Process completed" on the Terminal:
I opened System Settings again and saw this:
I pressed Allow anyway > Unlock
|
Beta Was this translation helpful? Give feedback.
-
|
I restarted and try to debug my app again:
Why this happened again? I wanna cry... I pressed Cancel
Then I got this error message in the debug console. Then I opened System settings again:
Still saw this "Adobe AIR.Framework" was blocked. I pressed Allow Anyway > Unlock again...
|
Beta Was this translation helpful? Give feedback.
-
|
Try debugging my app again, still got this:
This time I pressed Open. My app successfully launched.
But my app still can't connect to the debugger. There're no trace output. Breakpoints and other debug tools still did not work. |
Beta Was this translation helpful? Give feedback.
-
|
Ah ... okay I think I see a way around this, I just spotted a bit of sub-text in one of the above pop-ups that mentioned quarantine... Can you use a terminal and go to the root folder e.g. the one called If you run something like "xattr *" then you shouldn't see anything (or maybe an attribute about 'Finder', but definitely no quarantine...) Best way to avoid this in general is to use the AIR SDK Manager; if you download a zip file from a website and extract it, Apple started to add this extended attribute which blocks it from doing various things... thanks |
Beta Was this translation helpful? Give feedback.
-
|
I've re-unziped the AIRSDK and ran your command. Now I can test my app without any security dialog popup. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
There're no trace outputs on the debug console during my application test, but when my application crash, I got the trace outputs including the crash stack trace: |
Beta Was this translation helpful? Give feedback.
-
|
We'll take a look at the call stack, but in terms of it not debugging - can I check whether you see anything in Scout if you load that before running the app? And do you see anything useful in any of the other tabs on the VSCode window, like the "terminal" or "output" windows? The debugger connection should just be a case of the AIR runtime trying to open a socket to the port that FDB will open. But of course the SWF needs to be built with the -debug flag, and FDB needs to be running and waiting for the connection. thanks |
Beta Was this translation helpful? Give feedback.
-
Everything else is ok. I can see outputs on TERMINAL, DEBUG, PROBLEMS tabs. I'm looking for Adobe Scout download link for MacOS... thanks! |
Beta Was this translation helpful? Give feedback.
-
|
According to this:
I think I can't understand why it contains My asconfig.json: No mater specify Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Does seem weird .. the only thing I'm wondering though - can you actually put I notice you also have |
Beta Was this translation helpful? Give feedback.
-
|
It's my fault. On Windows, I reverse the keyboard shortcuts to test applications: Default:
I changed them to:
Because I want to press And... I forgot to change the keyboard shortcuts on MacOS. Then when I pressed Command+Enter to test my app, it actually run Quick compile and run (no debug). Aghhhh!!! With this setting you can put comments in json files: And with this setting you can disable warnings for trailing commas: Thank you so much! |
Beta Was this translation helpful? Give feedback.
-
:-) actually I'm quite interested in how to set up the keyboard shortcuts .. I also would normally use Ctrl-Enter to debug things! Good information on the comments-in-json, that's good to know! thanks |
Beta Was this translation helpful? Give feedback.
:-) actually I'm quite interested in how to set up the keyboard shortcuts .. I also would normally use Ctrl-Enter to debug things!
Good information on the comments-in-json, that's good to know!
thanks