Cannot Connect with new Release 1.18.0

[brianraymes]

Cannot Connect with new Release 1.18.0

[joshtynjala]

Do you have the as3mxml.sdk.editor setting configured to point to a previous Royale SDK?

[brianraymes]

I had an earlier 0.9.11-SNAPSHOT. Updated to the latest and it still fails.

Can you remind me the difference between the following two settings?

• as3mxml.sdk.framework
• as3mxml.sdk.editor

I have them both set to the same thing.

[joshtynjala]

as3mxml.sdk.framework

This one is like choosing a particular Flex/AIR SDK in other IDEs, like Flash Builder or whatever. It tells the extension which SWCs to load, which compiler to use for building, etc.

as3mxml.sdk.editor

This is is more advanced. It tells the extension to use the Royale compiler .jar files from a particular SDK for code intelligence — instead of the .jar files bundled with the extension. In general, you don't need to use this setting unless:

• Royale introduces new AS3 syntax that you want to use early
• A bug in Royale is affecting code intelligence and you can't work without the fix

Since Royale just had a release, there's not much to gain by using this setting right now.

I had an earlier 0.9.11-SNAPSHOT. Updated to the latest and it still fails.

Are you building from source? Did you rebuild royale-asjs only, or did you also rebuild royale-compiler too? Even if you have the latest framework, it could be that your compiler is out of date.

Or did you download a nightly .zip/.tar.gz? I just checked the CI server, and it appears that nightlies haven't been built since January, for some reason. With that in mind, the official 0.9.10 release is actually newer than the latest nightly.

[brianraymes]

I build all three (compiler, typedefs, and asjs) whenever I update.

I went ahead and removed the as3mxml.sdk.editor config line and only have as3mxml.sdk.framework, and now it seems to work as expected.