Change / Update:
As the problem updated below, I found the exact action that triggers it.
- Download apk from url via android browser.
- Install the app.
- After installation, the application provides you with two options: Open or Finish.
- If you select βOpen,β a bizarre behavior will appear, described below.
- If you select Finish, then run the application from the application tray, it works fine.
So it seems like this problem is caused by using the "Open" button that the browser provides you after installing the APK.
I get an error in the history of the application stack during the first installation. I made a test application to demonstrate this.
A test application is just two actions: A and B. Activity A starts B. What does all this do. Rest is the code generated by the wizard code from eclipse.
When the user installs the application (via the web url apk) and launches it for the first time, I get the stack due to the order:
-User launches the application, A is on top.
-They start B by pressing the button. B is on top of the stack.
-User presses the home screen button.
-User returns to the application, A is displayed, not B.
-User hits the back key, B is shown!
-User presses the back key again, A is displayed!
-User presses the back button again, the home screen is displayed.
-Now the stack is clean, and the application behaves "normal" from now on!
Does anyone else see this? It is almost exactly the same as this error, but my users do not install it from eclipse: http://code.google.com/p/android/issues/detail?id=2373&q=first%20%20i ...
I can provide a test application / source if someone wants to try. This is a manifest that does not have any special settings made for it.
<activity android:name=".ActivityA" android:label="ActivityA" > <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> </intent-filter> </activity> <activity android:name="ActivityB" android:label="ActivityB" > <intent-filter> <action android:name="android.intent.action.VIEW" /> <category android:name="android.intent.category.DEFAULT" /> </intent-filter> </activity>
as far as I know, this certainly should not happen, and works fine after you clear the history stack for the first time.
thanks
android
mark
source share