Databases
StackOverflow2013
Postsdbo
POIntent for switching between Activities kills my second Activity
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIntent for switching between Activities kills my second Activity
    primarykey
    data
    text
    <p>here is my problem: I have multiple activities in my application, two of them are a bit "special". Activity A is a home type of activity, used to launch the other activities. It also holds some other info, that can be updated from the background (uses onNewIntent). In the manifest I've declared it as singleTop. It starts other activities for result, so it can't be singleTask or Instance (startActivityForResult doesn't work with them). Activity B is a standalone Activity, that is launched on certain events, also declared as singleTop. It also starts other activities for result and also uses its onNewIntent. I've two separate notifications, that are linked to the corresponding Activity. I'm using for both</p> <pre><code>intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_SINGLE_TOP | Intent.FLAG_ACTIVITY_CLEAR_TOP); </code></pre> <p>The normal flow is:</p> <ol> <li>A is running</li> <li>Something happens - B is launched</li> <li>if user presses Home button I have two notifications for A and B</li> </ol> <p>And the problem: if user presses notification for A, A is launched, but B is killed (due to clear_top flag) if after that user presses notification for B new B is launched (activity is dead, <strong>but I need the old instance</strong>)</p> <p>I've read this article - <a href="http://developer.android.com/guide/components/tasks-and-back-stack.html" rel="nofollow">http://developer.android.com/guide/components/tasks-and-back-stack.html</a> To my understanding FLAG_ACTIVITY_NEW_TASK should launch the activities in separate tasks and FLAG_ACTIVITY_CLEAR_TOP should not kill B in this case. </p> <p>A workaround is to rework the logic, make them singleTasks and handle the result from other activities in onNewIntent, but I prefer not to go this way if another solution is possible. I've also tried </p> <pre><code>FLAG_ACTIVITY_REORDER_TO_FRONT | FLAG_ACTIVITY_SINGLE_TOP </code></pre> <p>and</p> <pre><code>FLAG_ACTIVITY_MULTIPLE_TASK | FLAG_ACTIVITY_NEW_TASK | FLAG_ACTIVITY_SINGLE_TOP | FLAG_ACTIVITY_CLEAR_TOP </code></pre> <p>to launch B, but neither works.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USGlatzial
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COYour implementation is wrong, you must not keep instance of an activity if its removed from the back stack. You must be able to save your activity state and recreate its state on every launch.
      singulars
      1. POIntent for switching between Activities kills my second Activity
      1. USAnis BEN NSIR
    2. COI agree with you, but in this case it's not an option. For me this is inherited code and the activity itself holds a lot of information and states (I know it's not correct, I've tried to refactor it and move most of the business logic in some managers, but a lot is still there) In this case I need something like a singleton Activity, but without using singleInstance.
      singulars
      1. POIntent for switching between Activities kills my second Activity
      1. USGlatzial
    3. COIf your "information" data is a business logic, just move it to a singleton class. You are hacking MVC pattern.
      singulars
      1. POIntent for switching between Activities kills my second Activity
      1. USAnis BEN NSIR
 

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