Skip to main content
Z
Zhenya1919
Known Participant
August 21, 2012
Question

Another iOS packager bug

  • August 21, 2012
  • 1 reply
  • 735 views

Came across another bug in iOS packager. In my project I have a function looking like this:

private function sample():Object

{

     var iValue:int = 10;

      return false ? iValue : null;

}

It correctly returns 'null' if packaged in ipa-debug-interpreter, apk-captive-runtime modes or if running in ADL. But it returns '0' if packaged in ipa-ad-hoc mode. I had to spend a whole day to figure out where is the problem. This is not the first type cast issue I came across. And it takes a lot of effort everytime to debug (10 minutes to build the project!). I'm breaking a dead line giving my customer an excuse that 'Adobe packager for iOS does not work right'. Which sounds like total BS of course. Adobe, please, get this straight. It is hard enough to develop with AIR for mobile. Bugs like this one make it much worse. Either way, I'm planning to advocate for using native tools in our next projects.

This topic has been closed for replies.

1 reply

P
pranjain
Participating Frequently
August 23, 2012

Hi,

I tried your code and it is working fine for me. I packaged the app with all the possible targets and got "null" in each case.

Could you please tell which version/build you are using?

-Pranali

Z
Zhenya1919Author
Known Participant
August 23, 2012

I'm still using AIR 3.2. Unfortunately, I don't have a chance to try latest AIR 3.4 at the moment. But I will check the same code when I update AIR SDK.

The code I posted is not a real code of course. I had to strip some logic and modify operators a bit. But I had hoped the bug would still reproduce. From my experience, most of the iOS packager bugs are caused by the rules of type casting that are not AS3 compliant. I have an impression that type casting rules used in the packager are more like classic C type casting rules. As the result, same code executes differently on iOS and Android|Windows. And it has being a huge problem for me.

Pahup
Adobe Employee
Pahup
Adobe Employee
August 24, 2012

Thanks for reporting the issue. With the code snippet you shared, we've not been able to reproduce the bug with AIR 3.2/3.3/3.4, would it be possible for you to share the code which demonstrates the issue.

Also, please consider it filing via bugbase.adobe.com with the sample files, thanks.

-Pahup

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