Skip to main content
September 1, 2010
Question

Air Update Problem

  • September 1, 2010
  • 3 replies
  • 2480 views

Hi everyone,

i just wanted to update an AIR Application for a client. But when the update framework (i'm using the ApplicationUpdaterUI) has downloaded the AIR file and wants to install it, it says that the AIR file is damaged. When i'm installing the downloaded file (copied it from the #ApplicationUpdate dir) by hand everything works fine. Wiredly enough, everything worked fine the last time.

Any idea what maybe be the cause to this problem?

Adobe AIR 2.0.2.12610

App compiled with Flex 4.0

Thanks in advance

Timo

Edit: This is whats in the Logfile when the updating process fails:

[2010-09-01:14:09:20] Starting update of c:\programme\myapp\myapp.exe

[2010-09-01:14:09:20] Updating from file:///C:/Dokumente%20und%20Einstellungen/VAdmin/Anwendungsdaten/myapp.4BCA79BE2D83E8B0AFDB124EAD7E123E1B6A1E28.1/Local%20Store/%23ApplicationUpdater/update.air

[2010-09-01:14:09:20] Updating to version 0.9.509

[2010-09-01:14:09:20] UI SWF load is complete

[2010-09-01:14:09:21] UI initialized

[2010-09-01:14:09:21] beginning UI styling

[2010-09-01:14:09:21] UI styling complete

[2010-09-01:14:09:21] Unpackaging to C:\Dokumente und Einstellungen\VAdmin\Lokale Einstellungen\Temp\fla1E6.tmp

[2010-09-01:14:09:21] failed while unpackaging: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2032" errorID=2032]

This topic has been closed for replies.

3 replies

September 20, 2010

Actually i don't think i'll find the time at the moment to build an example since i cannot post the whole project here. But thanks anyway. If i find the time, i'll be posting it here.

Adobe Employee
September 17, 2010

Hi,

From a first look at the error log you've attached the problem appears to be in the air app installer but we cannot say what is causing it. Can you send me a copy of the apps in order to try to reproduce the issue on one of our machines? You can send me a private message with it or put on one of your servers and send us a link to it. We would really appreciate if you could simplify the app and reduce it to a small reproducible use case.

Have you tried to directly install the downloaded file file:///C:/Dokumente%20und%20Einstellungen/VAdmin/Anwendungsdaten/mya pp.4BCA79BE2D83E8B0AFDB124EAD7E123E1B6A1E28.1/Local%20Store/%23Applica tionUpdater/update.air? The problem might be happening due to an antivirus that you are using and which interferes with the update file.

Also can you give us more details on the two apps (the one installed and the updated one) like with which AIR versions were they compiled and packaged and also on the buffer overflows you are seeing.

Regards,

-Catalin

September 17, 2010

Thanks for your reply.

For everyone interested in the solution:

I was doing this:

try {

for each (var win:NativeWindow in NativeApplication.nativeApplication.openedWindows) {

winClosingEvent = new Event(Event.CLOSING, false, true);

win.dispatchEvent(winClosingEvent);

if (!winClosingEvent.isDefaultPrevented()) {

win.close();

}

}

} catch (e:Error) {

}

when i was closing my application. After removing this source it worked.... again. Still, i have no idea why this seems to break the air app now.

Adobe Employee
September 17, 2010

Thanks for sharing this.

We are trying to understand what exactly was causing the problem the first time and for this we would need your help.

Can you give us more details regarding the code snippet you've pasted in the previous post and the context in which it is running like on which action / event are you calling and executing this handler? If you could create a small app that can reproduce your initial problem it could help us in better understanding what the causing this problem.

Regards,

-Catalin

September 1, 2010

Hi,what was your sdk version before ?

September 1, 2010

Hi, thanks for your replay.

It was the same.

After some further investigation i found out, that the air app is deleting the downloaded update.air file right before the update application could start. The processmonitor tool did show some buffer overflow events in the Windows Event flow. I have no clue where they come from... -.- but it looks like the file gets deleted due to this overflow error. I hope i'll find a solution soon.