Databases
StackOverflow2013
Postsdbo
POAndroid App Lifecycle and Intents
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid App Lifecycle and Intents
    primarykey
    data
    text
    <p>I'm having a bit of an issue with interaction beween my app and other apps on my phone, but I'm starting to think that maybe it's working as designed? Anyway, here's the problem.</p> <p>My App, call it <em>App A</em> is a photo-manipulation app. So a user goes in, plays around to make changes and then uses the <em>Share</em> button to pass it on <em>(SEND Intent)</em>. The photo is sent to another app, chosen from the <em>Share</em> menu, call it <em>App B</em>. This stand-alone app has its own menus, completely different look and feel, etc. The user does his thing in this app for a bit, then hits the home button and goes his way to do something else. </p> <p>Sometime later, he decides he wants to run my app again. He goes into the launcher, hits the icon for <em>App A</em> (my app), and up pops <em>App B</em>. Very confusing. If he happens to remember that last time he ran <em>App A</em>, he used the share button to get into <em>App B</em>, maybe he'll think to use the back button, to get back into <em>App A</em>. If he doesn't remember, all he knows is that he is trying to use <em>App A</em>, but Android is giving him <em>App B</em>.</p> <p>(I have one app on my phone that takes over the back button for its own use so you more-or-less get stuck in <em>App B</em> with no way out. Ugh. You hit the icon for <em>App A</em> and always end up in <em>App B</em>)</p> <p>Is there any solution to this, or is it working as designed? None of my onCreate, OnResume, onStart, etc. methods get called when this is second-open is occurring, so I can't trap it. And realistically, I can see the desire for this behavior when timelines are short - i.e. hit the home button, quickly use some other tool, and then go back to what you were doing. But with a timeline any longer than a minute or two, it gets very confusing.</p> <p>Anybody else dealing with this problem? Is there a basic Android architectural issue here? Is the SEND intent being mis-used by being accepted by stand-alone apps instead of small utilities?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser1088497
    1. USuser1088497
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid App Lifecycle and Intents
      1. USGangnus
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload