Client wanted Android app. I made app. Client got app. Everyone happy. Until he reported a bug that I can't possibly solve. --- He goes into a menu list, fools around, goes into a few screens, all looks good. He hits the back button (hardware back button), the list or content goes back. The top navigation bar and header image stays. ***Mind blown.*** He tries hitting the android back button more. Finally gets to home screen. Now title bar is fine. Home screen content is another plugin. It's all jumbled. Navigation is completely broken. I have *absolutely* no idea where to even start on fixing this, or what the heck went wrong. Please, please, please tell me I'm not the first person to encounter this. I haven't worked with Android much, but I don't remember folks reporting something like this. Or ever hearing of this. LOL. Help appreciated. If anyone can even fathom what I'm looking at. I seriously might need to record this, it's unbelievable. --- Full text from client explaining issue: "I can’t find a cause. It’s random. Sometimes it works fine for 10 minutes jumping all around with no issues, then sometimes it will start acting weird within a minute or two. Happens on both phones: 1) LG L34C, Android 4.4 2) Motorola Moto G, Android 4.4.4 Happening again right now. I’m at the home screen. I hit the return arrow key on lower left of phone, and “Contact” appears in the upper bar even though the home screen graphic and menu is still there. I hit it again, nothing, hit it a few more times and see “Contact” in upper bar again. Hit it a couple more times and finally it exits the app. It’s like it’s remembering pages that were visited in the cache, but it’s not showing the proper history as I keep hitting that back button. Then, if I stop and try to select “Speakers” for example, it just refreshes the home menu graphic and keeps the same home menu items while showing “Speakers” in the upper bar. It’s like it gets confused or something. Really annoying." David.

Easier to buy him an iPhone and declare it "job done". I'm sure you've been tempted to do just that ;-)

If only Niraj, if only.

Remember, as distasteful as it sounds, each of you can fire the other. Have you made a brand new app by building and testing one screen addition at a time? Perhaps there is a faulty plugin in the mix. Another approach is to keep the bad app, then delete a screen at a time and then re-test.

Vaguely remember seeing something like this. Told myself I didn't want to deal with it and walked away.

Niraj! Why did you not tell me about this one!? Don't tell me your memory is fading? ;-) http://www.freeappbuilder.com/forum/thread.php?tid=A8FED18E167C77BBA64B912&fid=06DB0BCB08E3333&sortColumn=FT.id&sortUpDown=&currentPage=2 Going to research this further... David.

Do you have a Tabbed app? Android causes amnesia in my punkin head

Tabbed app yep. http://www.buzztouch.com/forum/thread.php?tid=096A2CBA60C496685946C98&currentPage=1 I'll see if I can use the solution to "add all to stack", not sure why this would be an issue. David.

In Android, you can use the official stack or you can create your own private stack. Google "android back stack". You can start by reading this: http://developer.android.com/training/implementing-navigation/temporal.html#back-fragments Here is a more hands-on approach, if you want to change what happens when the user taps Back button. There is a method called onBackPressed and here's an example: http://stackoverflow.com/questions/7992216/android-fragment-handle-back-button-press

I don't really use the hardware controls on an Android device because it does have issues. I use the App back button! LA

@Dusko, thanks for the info, I'm trying out the solution by @peterj and we'll see if that helps any. @La, same here, but I can't tell my client that he needs to stop using the hardware button, hehe. Will report back if it's fixed..

I just ran into what I think is the same problem with an Android app with tabs. Various app fragments appear in the wrong places. My theory as to why it seems to work for awhile and then stop working is because it works until you select a tab. Once you select a tab, then it stops working correctly.

Susan I have confirmed that theory. It's surprising this is the first time I've heard of this, I would think lots of people use tabs. :-( Gotta love jumping into Android!

Tabs on BT 2.0 Android looked OK. On BT 3.0, they didn't, so I suspect many people simply stopped using them. I did. Alan

Is this on self hosted?

I can remember reading about a year ago about a bug in Android 4.3 but not in 4.4! Yeah it sounds like the layers are overlapping or when your client clicks back on the device it's creating another whole screen. What happens if your client clicks home on the hardware? LA

The "back button" on the top left is the home button.it goes to the first screen.you know methods such as actionBar.setHomeUpAsEnabled (true); are referring to this.it's meant to climb the back stack to the first fragment. I know David has made some changes in the android studio project, but not sure if he changes anything to do with this bug.

I don't have the app running right now, but I am pretty sure that when you touch the home button everything is straightened out.