Skip to main content
Legend
March 8, 2013
Question

Cannot test in standard mode iOS

  • March 8, 2013
  • 4 replies
  • 783 views

Hi,

I'm having a fairly fundamental issue with iOS debug at the moment on FB 4.7.

If I either a) compile for ad hoc release or b) compile for fast mode debug, it works fine.

If I compile for standard mode debug, it launches the app and then crashes out and dies horribly.

Any ideas where to start looking?

Thanks,

G

This topic has been closed for replies.

4 replies

Pahup
Adobe Employee
Adobe Employee
March 11, 2013

HI Gaius,

Would it be possible for you to reproduce the problem with a sample project, please consider it reporting it via bugbase.adobe.com, attach the sample projects.

Share the bug number here for reference.

-Thanks for reporting.

Pahup

Legend
March 13, 2013

Hi Pahup,

Sorry for the delayed response, I'm afraid the issue could be specific to my project which is a large, proprietary codebase that I'm not at liberty to share!

I've tried generating a simple app, but packaging does appear to work for a very basic app. I'm going to look into one of the libararies I'm using as I did previously encounter a similar issue with SWIZ where I'd not got all the compiler directives set correctly, but I think I need a list of possible candidates for digging, if at all possible.

G

Legend
March 27, 2013

Hi,

I have recently rebuilt my workspace and I am now seeing the error message that, I think, was triggering it... Either way, I _still_ can't debug in standard mode for this project.

Error occurs on line 2815 of SystemManager code, according to FlashBuilder, with a null pointer for the following:

                var c:Class = Class(getDefinitionByName(mixinList));

                c["init"](this);

I have looked into it, and i is set to zero so the value of mixinList is something like _my_project_name_FlexInit.

Any pointers on how to debug? Is this a problem with my project or with Flash Builder?
G

TypeError: Error #1009: Cannot access a property or method of a null object reference.

          at en_US$Messages_properties/getContent()

          at mx.resources::ResourceBundle()

          at mx.resources::ResourceBundle()

          at en_US$Messages_properties()

          at en_US$Messages_properties()

          at mx.resources::ResourceManagerImpl/installCompiledResourceBundle()

          at mx.resources::ResourceManagerImpl/installCompiledResourceBundles()

          at mx.resources::ResourceManagerImpl/processInfo()

          at mx.resources::ResourceManagerImpl()

          at mx.resources::ResourceManager$/getInstance()

          at mx.styles::StyleManagerImpl()

          at _gustavo_mobile_as_app_FlexInit$/init()

          at _gustavo_mobile_as_app_FlexInit$/init()

          at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::kickOff()

          at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::preloader_completeHandler()

          at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::preloader_completeHandler()

          at flash.events::EventDispatcher/dispatchEvent()

          at mx.preloaders::Preloader/timerHandler()

          at mx.preloaders::Preloader/timerHandler()

          at flash.utils::Timer/tick()

          at flash.utils::Timer/tick()

Inspiring
March 9, 2013

Some people have something similar with Starling apps when using standard packaging method (not debug) on iOS:

http://forum.starling-framework.org/topic/scaffold-mobile-does-not-work-correctly-when-standard-packaging-method-is-used

And here the forum post:

http://forums.adobe.com/message/4927939

In Starling the problems start when using the TextField class, perhaps you see something similar with your app.

It does happen with Flash Builder 4.6 and 4.7, AIR 3.5 and 3.6, but with AIR 3.4 a user told me having no problems.