Alright, I think I resolved the issue, it was made a lot easier with your 
suggestion Mark. When I watched when the Activity was created I realized it 
was the AccountManager framework, which led me to check out an example of 
using it in SampleSyncAdapter (it's weird you have to use that and not a 
SampleCustomAccount or something like that) and the source of 
AccountAuthenticatorActivity. I believe the framework was hanging waiting 
for a response from my Activity that I just wasn't giving. I used the 
AccountAuthenticatorResponse and made sure to setResult before finishing 
the Activity, and that seems to resolve the problem.

On Thursday, November 8, 2012 8:51:05 AM UTC-8, Dandre Allison wrote:
>
> I had a chance to do Hierarchy Viewer, and it makes it very clear what's 
> going on. Your suspicion is correct, there's an invisible Activity that has 
> focus on top of my AccountAcitivity. The culprit is called 
> com.android.settings/com.android.settings.accounts.AddAccountSettings. Now 
> I have to figure out how to get around it, or what setting I am missing 
> that's making it stick around like this.
>
> On Wednesday, November 7, 2012 5:12:02 PM UTC-8, Mark Murphy (a Commons 
> Guy) wrote:
>>
>> Sounds like there is a transparent activity at the top of the stack, 
>> or something along those lines, that has the foreground and therefore 
>> steals input. 
>>
>> See if this recurs on the emulator. If it does, get the app in the 
>> state where it is not responding to input, then bring up Hierarchy 
>> View and see what turns up. 
>>
>> On Wed, Nov 7, 2012 at 7:56 PM, Dandre Allison <[email protected]> 
>> wrote: 
>> > I have an account picker Activity modelled after the iosched 
>> > AccountActivity, but for my app's custom accounts. When I press the 
>> "add 
>> > account" action it launches a connect account Activity for that custom 
>> > account. If I press back from here (trying on Nexus 7 Android 4.1) I 
>> come 
>> > back to what looks like my AccountActivity screen, but with one 
>> important 
>> > difference - it's just a still, non-responsive screen. I'm using ABS 
>> 4.2 if 
>> > that could affect anything. Somehow if I just press back once more, 
>> nothing 
>> > visually changes (no screen refresh of any sort), but the screen is 
>> > responsive again. Any ideas what I could look for to resolve this? I 
>> added a 
>> > test button to my layout to see if the whole screen was non-responsive, 
>> or 
>> > if it was just the "add account" action. 
>> > 
>>
>>
>>
>> -- 
>> Mark Murphy (a Commons Guy) 
>> http://commonsware.com | http://github.com/commonsguy 
>> http://commonsware.com/blog | http://twitter.com/commonsguy 
>>
>> Localized Android Question-and-Answer Sites: http://www.andglobe.com 
>>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to