Well, an Android dev in Google's online office hours helped me
troubleshoot this today.
It turns out that the reason the authToken from the AccountManager
wasn't working was because it was expired. It was dated Dec. 9th,
which is probably the day I first got my authentication code working.
I
It turns out that the reason the authToken from the AccountManager
wasn't working was because it was expired. It was dated Dec. 9th,
which is probably the day I first got my authentication code working.
I guess it cached the authToken and has been using the same one ever
since.
How do you
On Jan 6, 3:01 pm, Mariano Kamp mariano.k...@gmail.com wrote:
It turns out that the reason the authToken from the AccountManager
wasn't working was because it was expired. It was dated Dec. 9th,
which is probably the day I first got my authentication code working.
I guess it cached the
Rory,
where did you get the ah information from? Is there any
documentation on the actual Google service behind this?
I checked the Android 2.0 Calendar and Contacts app and they only seem
to use a homegrown mechanism. Maybe better luck with Android 2.1?
Cheers,
Mariano
On Dec 3 2009, 9:59 pm,
Any update on this one? Does it work again?
How do you it fails?
I think I am in a similar situation. I get back an auth token, but
when using it accessing the Google Reader API it is not accepted.
On Jan 4, 12:10 am, polyclefsoftware dja...@gmail.com wrote:
I'm about to tear my hair out. The
I'm about to tear my hair out. The authToken I was getting from
AccountManager was working fine before I went away for the holidays. I
get back home and start back into development and now the authToken I
get from the following code is no longer valid when requesting a
cookie:
AccountManager mgr
Just tested on my Droid. That does indeed work.
Thanks!
On Dec 11, 9:25 pm, Micah mi...@zoltu.net wrote:
The application only needs permission to ask authenticators for access
to anaccount, but when they install they don't have to say which
accounts the app will access. Just because an app
Well, if anyone is still following this thread at all...
I'm able to replicate the behavior RoryD describes, but it is still
less than ideal from the user's perspective. Here's what happens:
1) The user opens the app for the first time, clicks a button to log
in.
2) Account Manager tries to get
The application only needs permission to ask authenticators for access
to an account, but when they install they don't have to say which
accounts the app will access. Just because an app has permission to
access your Facebook account doesn't mean you want the app to have
access to your Google
Thanks for this. I'm able to get the auth token after granting
permission to the app. Anyone have any ideas how to clear the
credential information once you have allowed an app to access them?
Uninstalling the app doesn't work, and under Location Security
Settings, Clear storage is grayed out.
On Nov 9, 5:00 pm, Nerdrow troybe...@gmail.com wrote:
I don't know the authTokenType to pass as an input parameter.
It looks like ah does the trick for authTokenType!
If you specify true for notifyAuthFail, you'll get a notification
posted saying Permission Requested that takes you to a screen
I would be careful removing your own authentication code just yet. So
far Droid is the only phone with 2.0 on it and it's uncertain that
once other phones get 2.0 whether or not they will also get the
Facebook and Google authenticators. The emulator currently does *not*
support Facebook or
I am working on a similar project over at:
http://code.google.com/p/google-authenticator-for-android/
The end goal is to simulate the Google Account Authenticator found on
the Droid so that developers can use Google Accounts on their AVDs, as
well as people with 2.0 phones without Google Accounts
Still wants an authTokenType (not Account.type). Here's what I tried:
final AccountManager accountManager = AccountManager.get(this);
final Account[] accounts = accountManager.getAccounts();
final int accountsCount = accounts.length;
Account account = null;
for(int i=0;iaccountsCount;i++) {
On Nov 13, 3:55 pm, Nerdrow troybe...@gmail.com wrote:
A working example from the Android team would be nice :)
No kidding.
I'm interested in using the authentication from the user's Google
account to automatically log them into a Google App Engine app. I was
hoping the new AccountManager
I would also like some documentation. The APIs are insufficient to
deduce any sort of real world usage...
The sources to the Dev Tools AccountsTester app would be a great
start it seems that they left it out of the git repo.
On Nov 13, 7:05 pm, polyclefsoftware dja...@gmail.com wrote:
To facilitate the discussion around this topic, I've started up a project
over here:
http://code.google.com/p/androidaccounts/
http://code.google.com/p/androidaccounts/If anyone is interested in
pitching in and writing some examples, let me know so I can add you.
The current state of the project
Using an already existing account is pretty easy, which means in the
case of Droid Facebook, Google and Exchange. Writing the actual
account providers is the hard part.
I'm just coding this off the top of my head, since I haven't finished
writing an authenticator yet (and the SDK has no built-in
To reply to your more specific questions, it is my understanding that
the type you see in your log output is the type you would pass in to
most of the AccountManager functions. The type should be a java style
universally unique name (ie: domain.subdomain.accounttype) in the form
of a string. So
I just tried this real quick on my Droid:
AccountManager mgr = AccountManager.get(this);
Account[] accts = mgr.getAccounts();
final int count = accts.length;
Account acct = null;
for(int i=0;icount;i++) {
acct = accts[i];
Log.d(ACCT, eclair account - name=+acct.name+,
type=+acct.type);
}
20 matches
Mail list logo
