Now I don't use any flags just call startActivity. I don't know which
flag should I use to get the expected result.
On Jul 29, 9:18 pm, TreKing treking...@gmail.com wrote:
On Fri, Jul 29, 2011 at 2:13 PM, b_t bartata...@gmail.com wrote:
I have an app A and an app B. B has an activity called
On Sat, Jul 30, 2011 at 12:44 AM, b_t bartata...@gmail.com wrote:
Now I don't use any flags just call startActivity.
You are doing much more than that or you're not explaining the problem
correctly. There is no way you're associating an Activity that lives in one
App with another separate App
webmonkey: I confirm the behavior you are describing. If the
application is started from Eclipse it behaves the way I described
above. Once I start it from the Home screen the problem goes away.
Justin: Given what webmonkey stated I removed all the launch flags
from all the activities in the
On Aug 27, 1:37 pm, Gil [EMAIL PROTECTED] wrote:
Justin: Given what webmonkey stated I removed all the launch flags
from all the activities in the manifest file. The behavior seems
correct now if I start the app from the Home screen but not if I
launch the app from Eclipse.
The behavior in
The behavior in Eclipse is correct. Each time you run from Eclipse,
you are uninstalling and reinstalling the app, so it will be started
completely fresh.
True, and I wouldn't expect Eclipse to go back to where you left. But
the fact still is that in this freshly started app the problem
Thanks hackbod, I understand that the app is uninstalled and then
reinstalled when started from Eclipse. I guess what I did not
understand is that when you launch the app from Eclipse the behavior
is different (as outlined in the sequence of steps to reproduce the
problem I posted earlier) than
Hi Justin,
Any update related to this issue?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this
No, I would have provided one if there was, :-) . But if your question
is if its still be looked at, the answer is yes.
Cheers,
Justin
Android Team @ Google
On Aug 25, 5:46 pm, Gil [EMAIL PROTECTED] wrote:
Hi Justin,
Any update related to this issue?
hackbod,
I wrote a simple app, based on the SDK Forwarding example, which
reproduces the problem. The only difference between my app and the
Forwarding app, as far as I can tell, is that the manifest:
?xml version=1.0 encoding=utf-8?
manifest
If I use singleTop for both activities the code works as expected.
The singleTask launchMode is causing the behavior described
above.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post
It turns out that singleTask is what I need in my app for my main
(LAUNCHER) activity otherwise sometimes I end up with multiple
instances of my activities.
On Aug 22, 10:33 am, Gil [EMAIL PROTECTED] wrote:
If I use singleTop for both activities the code works as expected.
The singleTask
I've replicated the behavior you're seeing, and it seems anomalous, so
I'll keep looking at it.
Cheers,
Justin
Android Team @ Google
On Aug 22, 12:20 pm, Gil [EMAIL PROTECTED] wrote:
It turns out that singleTask is what I need in my app for my main
(LAUNCHER) activity otherwise sometimes I
The normal behavior would be for the user to return to activity B.
You must be doing something more than you describe here.
Fwiw, this might be useful: http://code.google.com/android/intro/appmodel.html
Also from a command like prompt, adb shell dumpsys activity while
the emulator is running
I did more research on this subject and I have a new situation.
Activity A is the main activity and it uses the singleTask launch
mode. Activity B uses the singleTop launch mode. In my app Activity A
is the login activity for my application. The user enters the username
and password and if it is
Dianne, please save me one more time.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group,
The user enters the username
and password and if it is correct I call finish() on Activity A an
call startActivity to start Activty B.
You are calling startActivity from onPause() then? If you are calling
startActivity and then finish(), finish() won't actually execute until
the new activity
Sorry it was not clear.Please let me try to explain the second part in
a different way.
1) Start the application for the first time. Activity A is displayed
(it is the main Activity i.e. uses MAIN/LAUNCHER in the intent
filter). Activity A also uses singleTask launch mode.
2) User enters
How are you performing your asynchronous authentication? Are you just
starting another thread from your Activity or are you using a specific
class?
Cheers,
Justin
Android Team @ Google
On Aug 21, 4:13 pm, Gil [EMAIL PROTECTED] wrote:
Sorry it was not clear.Please let me try to explain the
I'm starting my own thread from Activity A and then I use a Handler to
post the callback to make it thread safe.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send
On Aug 21, 4:13 pm, Gil [EMAIL PROTECTED] wrote:
finish();
Intent intent = new Intent( this, ActivityB.class);
intent.setAction( Intent.ACTION_VIEW);
intent.setData( m_signedInUser.getContentUri());
startActivity( intent);
You should call finish -after- starting the next activity.
Thanks hackbod! I moved the call to finish() after startActivity().
The behavior has not changed though.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
If you look at ApiDemos App Activity Forwarding, you will see an
example that does this exact same thing, so there must be something
different that you are doing. Just making an activity singleTop won't
have that effect (though singleInstance or singleTask -would).
On Aug 21, 7:09 pm, Gil
Thanks hackbod! I'll look into that example tomorrow to try to
understand the differences.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
23 matches
Mail list logo
