It turns out that my error was a null error because AIR doesn't support stage.nativeWindow on mobile devices.
Through all my searching I'm no closer to finding a way to bring the app the the foreground, any suggestions? On Feb 25, 5:31 am, TreKing <treking...@gmail.com> wrote: > On Thu, Feb 24, 2011 at 2:26 PM, RJM <mccormack2...@googlemail.com> wrote: > > I don't actually know what the error is, I wasn't debugging on the phone at > > the time (not sure how to do that), > > Please learn to debug your app. There's not much anyone can do for you > without so much as an error message to from. > Also, since you're using NativeApplication I'm assuming you're using the > NDK, in which case you probably want to direct your query to that group. > > > all I know is that the method stopped and the code after the call to > > nativeWindow.activate didn't get called. > > And all I know is that that is not enough information to help you. > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
