Adobe AIR Team - please stop trolling us and start fixing critical bugs.

Hey , it's  adobe ..OK.  It's very very very  normal . Just  waiting ,just be  patient , we will fix it  several years  later ,because we have more bugs important than it.

OK ,let me tell you  another funny thing.

Refer to this article :  http://help.adobe.com/en_US/air/extensions/air_extensions.pdf  , Adobe  said in  page 49

Resources on Android devices

For the Android-ARM platform, put the resources in a subdirectory called res,relative to the directory containing the

native code library. Populate the directory with resources as described at Providing Resources on

developer.android.com. When ADT packages the ANE file, it puts the resources in the Android-ARM/res directory

of the resulting ANE package.

When accessing a resource from the extension’s Java native code library, use the getResourceID() method in the

FREContext class. Do not access the resources using the standard Android resource ID mechanism. For more

information on the getResourceID() method, see “Method details” on page 125.

The method getResourceId() takes a String parameter that is the resource name. To avoid resource name conflicts

between extensions in an application, provide a unique name for each resource file in an extension. For example, prefix

the resource name with the extension ID, creating a resource name such as

com.sample.ext.MyExtension.myImage1.png.

SO ..I follow they says to do.  OK ,i got an  ANE  successfull .  Then  ,i  Add the  ANE into my mobile project . And Click  "release"  button(or  debug ).

THat  is the  funny  thing .I actually got an error message:

java.lang.Exception:

aapt tool failed:invalid resource directory name: D:\LocalProfile\Localtemp\8d438362-8178-429a-858f-715c1e176235\res/values-sw600dp

invalid resource directory name: D:\LocalProfile\Localtemp\8d438362-8178-429a-858f-715c1e176235\res/values-sw720dp-land

          at com.adobe.flexide.multiplatform.android.launching.ADBLaunchHandler.doPackage(ADBLaunchHandler.java:454)

          at com.adobe.flexide.multiplatform.android.launching.ADBLaunchHandler.launch(ADBLaunchHandler.java:350)

I've test it on windows 7 32bit + FB4.7+AIR3.7 SDK ,and i  also asked my  friend test it  on  Mac OS + FB4.7+3.6SDK  ....cann't package APK too. but error message is diffrent .

I wonder if anyone of adobe  actually fully tested what they said . But I spent a few days checking my approach. And i responsible for my words.

I'm tired of reporting BUG.No matter what happens, i  tell myself ,"it's product by adobe".

To add some more "weight" to the seriousness of this bug, today I discovered that only on Windows there is a problem with writing over existing files using the proposed "workaround" for this bug suggested by Adobe. Using the normal open file method does fire any close events, so there is no way to monitor when the file is available again for writing. Since the code I'm writing is being used on mobile and desktop, the async methods can't be used on the mobile but would work fine on the desktop. It's just a mess all around, and this just needs to be fixed.

Yes, that Filestream bug is a big problem for anyone who wants to develop a responsive UI. The suggested work around IS NOT a work around. There is a reason the API has async methods; if the work around is so perfect then remove the async methods from the API. Sorry for sounding sarcastic but it is silly for this type of defect to have been ignored for so long; these types of API methods are the buidling blocks of our apps.

Hi develop-me,

First of all, let me appreciate your taking time and providing us feedback.

Regarding the point that you have raised, we would try to see what we can do here.

In general however, there is a huge backlog of bugs and features (features which are very important for some of your fellow developers) and we try our best to proritize them appropriately, based on how important the use cases are. The entire runtime team is extremely focussed, and never picks up anything which is not in the best interest of developer community. So such comments from your end would not really help us in making the things better.

Let's keep the feedback coming, and have the process constructive.

We will update you on the progress of the bug you have reported.

Thanks.