Flash Builder 4.6 is not compatible with AIR 3.6, to my knowledge.  4.7 is
the only version that can handle the newest SDKs...

I'm using a self-signed cert, since this app is deployed only to machines
that we own...  We never bothered to buy a real code-signing certificate...
 But the problem seems to be within FB 4.7 somewhere, not with the
certificate -- it's not even letting me enter the password for the cert...
 And I did try creating a new self-signed certificate, in case the old one
was messed up somehow...

No one else seems to have this problem with FB 4.7 -- everyone I've talked
to has no problems exporting AIR apps, and FB 4.7 behaves exactly as it
should for them...  Weird...  You would think that
uninstalling/reinstalling would've fixed any problems I was having...

L.




On Wed, Mar 6, 2013 at 9:43 AM, Scott Talsma <[email protected]> wrote:

> Other than the satisfaction of having it running FB4.7, is there a
> compelling reason to use FB4.7?  Also, are you using a self-signed cert, or
> a real cert?  (Maybe try it w/both?)
>
> I just went to the Adobe page (
> https://adobeformscentral.com/?f=aqd5Yq*ONlcAvnasuWDB8w#) and submitted a
> request for my FB4.7 serial.  Once I have it, I'll try it out on an simple
> AIR project.
>
>
>
> On Wed, Mar 6, 2013 at 9:12 AM, Laurence MacNeill 
> <[email protected]>wrote:
>
>> Well, I completely uninstalled and re-installed FB 4.7, and I still can't
>> export an AIR project...  Any ideas?
>>
>> L.
>>
>>
>>
>> On Tue, Mar 5, 2013 at 11:58 PM, Laurence MacNeill <
>> [email protected]> wrote:
>>
>>> LOL.  I paid for Flex Builder 3 Professional, Flash Builder 4
>>> Professional, Flash Builder 4.5 Professional, and got free upgrades to
>>> Flash Builder 4.6 Professional and Flash Builder 4.7 Professional...  A
>>> free upgrade still counts as having paid for the software, doesn't it?  :-)
>>>
>>> If I don't get this figured out by 9AM tomorrow, i'm gonna pay for a
>>> single-incident tech-support call...  I think they're only $35?  Hell, even
>>> if it's $100, I've got to get this solved...  Stupid damn Adobe...
>>>
>>> L.
>>>
>>>
>>> On Tuesday, March 5, 2013, Eric DeCoff wrote:
>>>
>>>> you really should pay for the software
>>>> On Mar 5, 2013 9:09 PM, "Laurence MacNeill" <[email protected]>
>>>> wrote:
>>>>
>>>>> So, I just created a whole brand-new AIR project.  Just a simple thing
>>>>> with a <s:TextArea> in it.  I can't export a release build on that 
>>>>> project,
>>>>> either.
>>>>>
>>>>> When you're on the initial screen you see after you select Project |
>>>>> Export Release Build, you fill in the folder where you want it to be
>>>>> exported and select which "Export As" option you want -- it's not supposed
>>>>> to jump immediately to compiling when you click "Next" is it?  "Finish" is
>>>>> grayed-out, so I would imagine there's another window that's supposed to
>>>>> pop up after I click "Next."  But it jumps straight to compiling when I
>>>>> click "Next," so I don't ever get a chance to even look at the certificate
>>>>> or enter a password for it...   How do I get it to stop jumping straight 
>>>>> to
>>>>> compiling?
>>>>>
>>>>> L.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Mar 5, 2013 at 6:12 PM, Laurence MacNeill <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Already did that, too.  :-)  Great minds think alike...
>>>>>>
>>>>>> It appears to be something in the file where the compiler options are
>>>>>> saved -- almost like it can't write to that file because it's an older
>>>>>> project that wasn't created in FB 4.7.
>>>>>>
>>>>>> L.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Mar 5, 2013 at 6:11 PM, Eric DeCoff <[email protected]>wrote:
>>>>>>
>>>>>>> could try dumping your certificate file and then recreating it with
>>>>>>> the 4.7 tools
>>>>>>>  On Mar 5, 2013 6:10 PM, "Eric DeCoff" <[email protected]> wrote:
>>>>>>>
>>>>>>>> nope that was was thinking
>>>>>>>> On Mar 5, 2013 6:08 PM, "Laurence MacNeill" <[email protected]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I did select Clean Project...  Is there something else I can do?
>>>>>>>>>
>>>>>>>>> L.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Mar 5, 2013 at 6:07 PM, Eric DeCoff 
>>>>>>>>> <[email protected]>wrote:
>>>>>>>>>
>>>>>>>>>> you have done the simple thing like cleaning rebuild
>>>>>>>>>>  On Mar 5, 2013 6:06 PM, "Laurence MacNeill" <
>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>
>>>>>>>>>>> Also, it won't seem to save the Package Contents -- I go to the
>>>>>>>>>>> Package Contents tab and select the items I want to be packaged and 
>>>>>>>>>>> click
>>>>>>>>>>> OK.  It says updating compiler options or whatever, then when I go 
>>>>>>>>>>> back to
>>>>>>>>>>> Package Contents, nothing I selected is in there -- only the two 
>>>>>>>>>>> items that
>>>>>>>>>>> are listed as required are in there.
>>>>>>>>>>>
>>>>>>>>>>> Additionally, if I try to export a release build AIRI app to be
>>>>>>>>>>> signed later, it gives me a "You need to specify Package Contents" 
>>>>>>>>>>> error...
>>>>>>>>>>>  But it won't let me save them...  WTH is going on here?!  I'm 
>>>>>>>>>>> beginning to
>>>>>>>>>>> think upgrading to Flash Builder 4.7 was a huge mistake.
>>>>>>>>>>>
>>>>>>>>>>> L.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Mar 5, 2013 at 5:53 PM, Laurence MacNeill <
>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have a certificate for my AIR app, and since upgrading to
>>>>>>>>>>>> Flash Builder 4.7, I cannot export a release-build of this app...  
>>>>>>>>>>>> I go to
>>>>>>>>>>>> Project | Properties | Flex Build Packaging and select the 
>>>>>>>>>>>> certificate,
>>>>>>>>>>>> click OK and it never asks me for the password.  Then when I click 
>>>>>>>>>>>> Project
>>>>>>>>>>>> | Export Release Build, I'm selecting the "Signed AIR Package" 
>>>>>>>>>>>> option, and
>>>>>>>>>>>> it tries to compile it but then gives me an "Incorrect Password 
>>>>>>>>>>>> for this
>>>>>>>>>>>> Certificate" error...  But it never even let me enter the 
>>>>>>>>>>>> password...  So
>>>>>>>>>>>> what do I do?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> L.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>
>>
>

Reply via email to