Skip to main content
Inspiring
September 24, 2012
Question

InvokeEvent.INVOKE re-dispatches when I close the application and I launch by multitask button

  • September 24, 2012
  • 5 replies
  • 915 views

Hello,

on my galaxy nexus, Android 4.1, InvokeEvent.INVOKE re-dispatches when I close my application with

NativeApplication.nativeApplication.exit()

and I launch my application with the multi task manager.

When I launch my application with the application icon, I don't have this problem.

Thanks.

This topic has been closed for replies.

5 replies

chris.campbell
Legend
September 24, 2012

Thanks for reporting this, we had a similar bug about InvokeEvent.INVOKE with regards to device orientation but this was fixed in AIR 3.4.  Could you give this release a try if you haven't already?  If it's still a problem, could you please open a new bug report on this over at bugbase.adobe.com?  Please post back with the URL so that others affected can add their comments and votes.

pol2095Author
Inspiring
September 25, 2012

I'd like to ask everyone affected by this issue to take a minute and vote for the following bug.  It currently has zero votes:

https://bugbase.adobe.com/index.cfm?event=bug&id=3336533

pol2095Author
Inspiring
September 28, 2012

It isn't a bug, it's the default behavior for android.

<activity android:launchMode="singleTop">

          <intent-filter>

                    <action android:name="android.intent.action.MAIN"/>

                    <category android:name="android.intent.category.LAUNCHER"/>

          </intent-filter>

          <intent-filter>

                    <action android:name="android.intent.action.VIEW"/>

                    <category android:name="android.intent.category.BROWSABLE"/>

                    <category android:name="android.intent.category.DEFAULT"/>

                    <data android:scheme="mycustomuri"/>

          </intent-filter>

</activity>

the solution is to add android:launchMode="singleTop" in the application descriptor