Launch Timeout Expired ???

[Bill Norris]

I asked about this way back when I was just getting started. Never really got anywhere with a solution. My app has an activity (I call it the navigator activity) with several buttons that user clicks to start another activity, we'll call them activity1, activity2, activity3. If I go to activity1, then back to navigator and touch activity1 button again, nothing happens. I can go to activty2 or activity3 with no problem. After several (7-10) seconds, activity1 button works again. Same behavior with the other buttons. In a nutshell, when I try to go back to the same screen that I just left, it won't go right away. Log file acknowledges the touch, but says Launch Timeout Expired. Once I see that message, I can start that activity no problem. In my original post, Erel said something about using a timer to start the activity. I'm not sure what that would accomplish. Typical users will expect that when you touch a button to launch an activity, it should immediately go to that activity. I foresee a user assuming that the app has a bug when they encounter this behavior.

ADDITION: The "Navigator" activity I referred to is not the Main activity of the app. I observer that whenever I go back to Main activity, this delay I am describing does not occur.

 

[Kevin]

Have you tried stripping the code down to basics where the only code is for the button clicks and loading layouts? Does the full code run lots of stuff when the activities start or finish?

I assume you are calling Activity.Finish when finishing an activity or are you calling StartActivity to go back to the navigator activity?

 

[Bill Norris]

Resolved:

I tried inserting a "RETURN" at various points within the code of the Navigator activity, and was able to determine that this issue was occurring after I was initializing an animation. I eliminated the animation and all works fine now.