0

I have a photo editing app that is registered to a share intent (ACTION_SEND). I am struggling with a strange behaviour it has in the following scenario:

  1. I launch my app from the home screen and open a photo to edit
  2. I press the home button and launch a gallery
  3. I open a photo in the gallery, press Share, and choose my app
  4. A different instance is opened. In the task overview, I see my standalone app task and the gallery task
  5. From the instance initiated by the Share intent I start a new activity (by startActivity)
  6. When I press back on the new activity, I return to my standalone app! Only if I keep pressing back, I get to my Share-launched instance, by keep "backing" I get back to the gallery.

In short, it seems as if the instance of my app that started from the icon is being annexed to the task of the gallery once it issued the ACTION_SEND intent.

I have no special setting in the Manifest regarding task management. The same behaviour happens with different galleries (including Google Photos) so I guess they fire a standard intent with no special flags.

I tried setting taskAffinity="" but that caused other activities in my app to have distinct tasks in the overview..

It's all very frustrating.. Will appreciate any hint..

AndiGeeky
  • 11,266
  • 6
  • 50
  • 66
Gili Garibi
  • 416
  • 2
  • 13
  • Have you used `NEW_TASK` falg with `startActivity()` ? – AndiGeeky Dec 14 '15 at 09:59
  • I don't want the activity to be in a new task, I want it to be in the same task with the activity that started it, but not pull the "standalone" activity into the deal.. Thanks.. – Gili Garibi Dec 15 '15 at 06:08

0 Answers0