I'm developing an air chat application with file sharing support using FlashBuilder 4.6, Air 3.2 and Adobe Cirrus.
When I run my application in adl, it works perfectly.
But when I export it as a release build and run it from Air 3.2, it just won't work anymore:
I use an ArrayCollection as dataprovider, but the binding to this ArrayCollection fails when running in Air.
I tried to dispatch an event when I add an element to the ArrayCollection and manually refreshing the dataprovider,
but the eventListener function isn't launched (yet again, this code does work when running in adl).
I'm also experiencing problems with the NetStream.send() function.
It just doesn't seem to do anything when running in Air.
I disabled firewalls and ran it as administrator, but without success. It only works when running in adl.
I installed Air 3.3 beta, but it didn't help either.
While investigating another bug in my application (also with P2P connectivity), I discovered that the NetStream.send() function wasn't working properly.
The function is executed but it never reached the connected peer.
Again, this code worked when running from adl.
So I started digging into the differences between adl and Air:
Apparently FlashBuilder 4.6 is by default based on the Air 3.1 SDK.
I removed Air 3.3 from my system and replaced it with Air 3.1.
Now all my problems with ArrayCollection binding & NetStream.send() are solved!
Are these bugs already known? Or should I report them somewhere?
Does anyone knows if these bugs are already reported?