Databases
StackOverflow2013
Postsdbo
POActivity history stack wrong upon first install on device?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POActivity history stack wrong upon first install on device?
    primarykey
    data
    text
    <p><strong>Edit / Update:</strong></p> <p>As an update to the below problem, I found the exact action which causes it to happen.</p> <ol> <li>Download an apk from a url through the android browser</li> <li>Install the app.</li> <li>After install, the app gives you two choices: "Open" or "Done".</li> <li>If you choose "Open", the quirky behavior described below starts.</li> <li>If you choose "Done", then launch the app from the app tray, it works fine.</li> </ol> <p>So it seems like this problem is caused by using the "Open" button the browser provides you after installing the APK.</p> <hr> <p>I'm experiencing an error in the history stack of applications upon first install. I made a test app to demonstrate this.</p> <p>The test app is simply two activities, A and B. Activity A launches B. That's all it does. Rest is wizard generated template code from eclipse.</p> <p>When the user installs the app (via web url apk), and runs it for the <em>first</em> time, I get an out-of-order activity stack:</p> <p>-User starts the app, A is on top.<br> -They make A launch B by clicking a button. B is on top of the stack.<br> -User hits the home screen button.<br> -User returns to the app, A is displayed, instead of B.<br> -User hits the back key, B is shown!<br> -User hits the back key again, A is shown!<br> -User hits the back key again, home screen shown.<br> -Now the stack is clean, and app behaves "normally" from now on! </p> <p>Is any one else seeing this? This is almost exactly like this known bug, however my users are not installing from eclipse: <a href="http://code.google.com/p/android/issues/detail?id=2373&amp;q=first%20%20i" rel="noreferrer">http://code.google.com/p/android/issues/detail?id=2373&amp;q=first%20%20i</a>...</p> <p>I can provide the test app/source if anyone wants to try. This is the manifest, which does not have any special customizations made to it.</p> <pre><code>&lt;activity android:name=".ActivityA" android:label="ActivityA" &gt; &lt;intent-filter&gt; &lt;action android:name="android.intent.action.MAIN" /&gt; &lt;category android:name="android.intent.category.LAUNCHER" /&gt; &lt;/intent-filter&gt; &lt;/activity&gt; &lt;activity android:name="ActivityB" android:label="ActivityB" &gt; &lt;intent-filter&gt; &lt;action android:name="android.intent.action.VIEW" /&gt; &lt;category android:name="android.intent.category.DEFAULT" /&gt; &lt;/intent-filter&gt; &lt;/activity&gt; </code></pre> <p>as far as I know, this should definitely not be happening, and works fine after you clear the history stack the first time.</p> <p>Thanks</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmark
    1. USmark
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POActivity history stack wrong upon first install on device?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POActivity history stack wrong upon first install on device?
      1. USSkolVikingsGuy
      1. VTFavorite
    3. VO
      singulars
      1. POActivity history stack wrong upon first install on device?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COUnfortunately, the marketplace also does the same thing. It launches your app, and then if you try pausing it, then resuming it from its icon on the app tray, you get this same exact behavior. This is extremely confusing.
      singulars
      1. POActivity history stack wrong upon first install on device?
      1. USmark
    2. COCouldn't it be that hitting HOME destroys your app, e.g. because of low memory? In that case, Android would restart your app, hence A will be visible, but B was the last known Activity, so 'back' will launch B.
      singulars
      1. POActivity history stack wrong upon first install on device?
      1. USMatthias
    3. COHi Matthias, this doesn't seem to be the case. As a test, I gave Activity B some member variables. When resuming the app, if Android really did destroy my app due to low mem, those variables would be reset, instead they're the same as when I left. So it really is creating a second instance o the app. Also, I'm watching the process list through DDMS, and there are no other apps (besides core OS apps) running during tests, so there's plenty of memory for the system. I think this is definitely an issue with any app that tries acting as a launcher, and we are all the victims!
      singulars
      1. POActivity history stack wrong upon first install on device?
      1. USmark
 

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