Skip to main content
A
Anonymous
June 17, 2011
Question

Installation Issue worth a million dollars!

  • June 17, 2011
  • 1 reply
  • 592 views

Ok, anyone that can explain this one stands a chance for the million dollar prize!

We have an application that runs perfectly fine on my PC, during dev and after installation.

I give the installer to a colleage to run on his pc. He installs, hits run, and the App does not work. It just sits on the first loaded html.

If we simple edit the default.html file that was installed on his machine (the main app file) and do anything to it, add a space, an extra line, remove a tab, anything... and then save the file... the app will then work.

Er... explain this one?

His PC is XP with the latest updates and running Air 2.7. The app was also compiled with 2.7 SDK.

This topic has been closed for replies.

1 reply

chris.campbell
chris.campbell
Legend
June 17, 2011

That's very odd.  Is there any way you could send us this app so we could try it out internally?

Thanks,

Chris

A
Anonymous
June 19, 2011

Sure Chris, we've had the App installed on a variety of PC's, and it just so happens that on the one XP machine, this issue occurs.

I will send the App to you via email.

O
OMA2k
Inspiring
June 22, 2011

Hello lordgthefirst.

That sounds like a text format encoding issue. Probably the HTML files are encoded in UTF-8 with a BOM (or get a BOM somewhere along the process). Check your files with Notepad++ (free code editor, NOT the one included with Windows) and see if they have a BOM or not (if you can read "ANSI as UTF-8", they don't have a BOM, and if you see just "UTF-8", they DO have a BOM). You can also "see" the BOM by using the "type" command in a Windows console:

type myfile.html |more

If the first three characters shown are something like:

´╗┐

Then the file has a BOM. Flash/AIR doesn't seem to like it.

I also had an AIR application that didn't work each time a settings

file was edited with Windows Notepad (the bundled basic editor),

even if just a space was added at the end, and that was because

Windows Notepad adds a BOM to any UTF-8 file, with no option

to do otherwise (unlike Notepad++). I lost a lot of time until I realized

that was the problem.

So check that your HTML files do not have a BOM and try again.

I hope that works!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices