I have an update, and would greatly appreciate anyone's help:
Upon further investigation, the issue is not the Extension itself (regardless of whether it was created newly in EB2.1, in EB1.5, or created "manually" by building my own manifest, etc.).
The issue is that there are two library projects whose inclusion as project referennce in any Extension Builder project (regardless of whem/how it was created) causes the EB project not to produce a ZXP file using the Export wizard.
I tried deleting the 2 library projects, creating them anew empty - and they could be referenced successfully. I added back all the source files and this solved the problem, as of yesterday. Today, I tried building the ZXPs again, and it stopped working. I should mention that it appears that when the Export did work, it seemed to be changing the referenced project somehow. I noticed that they were given .mxi files, which I thought should not be created for a non EB project.
I should add (i'm about to post a seperate discussion) the Flash Builder error log is giving me a ton of Eclipse errors for many actions. Is this "normal"? By that, I mean is everyone getting those warnings and errors?
All help greatly appreciated.
And the plot thickens: An attrociusly ugly workaround -
If I remove the problematic projects from the workspace, move them to another workspace, and then have the EB Projects from the first workplace access those problematic projects' SWC, then the Export Wizard works.
Anyone have a better idea? Could this be because we're still in the trial period?
I'd appreciate hearing from Adobe staff.
We did some test here and could not reproduce the issue. Could you send us the problematic project built by EB1.5?
Thanks - how do I send it?