Closed GoogleCodeExporter closed 9 years ago
I'm afraid I cannot reproduce this. After 6, I am always at the main screen.
Do you really use the "back" key in step 4? Is your problem reproducable if
Android Wallet is not synching or you don't wait for it to clear the icon in
step 5?
Which Android version does your phone run? I have just tested this on Android
2.3.4 (Nexus One).
Original comment by andreas....@gmail.com
on 21 Aug 2011 at 2:40
Aha - this only happens when I go back to the bitcoin app from the list of
recent apps in the recent notifications pulldown (I'm running android 2.3.4),
or from a long-press on the home key. If I go to the app from my apps list, I
get to the home screen.
Original comment by neal...@gmail.com
on 21 Aug 2011 at 3:05
I think it happens because the main activity is closed or forced closed after
switching to submenus, thus popping it out of the history queue. So when you
resume the app, the queue is missing the main menu and thus returns to the next
in line which is the home screen(also an activity). It might be a bug somewhere
and I've experienced it myself. I don't have free time to do a debug so it's
either up to neal to set his device on development mode with logging on or a
developer to reproduce and debug it.
Original comment by arcusiul...@gmail.com
on 21 Aug 2011 at 11:39
1. Launch Android Wallet
2. Tap Send.
3. Long-hold Home button, switch to another app.
4. Tap Home button.
5. Long-hold Home button, switch to Android Wallet.
You will return to the Send screen.
6. Tap Back or Cancel.
You will go to the device Home, not Android Wallet's main page.
Original comment by br...@bitcoinrigs.com
on 23 Aug 2011 at 4:15
Actually you can leave out step 3 (comment #4).
This proves to be a bit tricky. I intentionally restricted the
android:launchMode of certain activities, so you don't get multiple instances.
What you are seeing is the side effect.
Original comment by andreas....@gmail.com
on 23 Aug 2011 at 1:46
Original comment by andreas....@gmail.com
on 23 Aug 2011 at 1:46
I think this is fixed with version 3.09. Can you confirm this? If not, feel
free to comment again and I'll re-open the ticket.
Original comment by andreas....@gmail.com
on 26 Jun 2013 at 1:23
Original issue reported on code.google.com by
neal...@gmail.com
on 21 Aug 2011 at 2:31