*bump* ;-)
Dianne, nobody else stepped up with more explanation. Do you have any
idea whom to contact or how to proceed to get more information?
Did cupcake change your previous answer in any way?
On Mar 20, 10:50 pm, Dianne Hackborn hack...@android.com wrote:
Sorry maybe someone else can
Well, did Cupcake bring some functionality that lets non-Google apps access
the user's Google credentials or has there been any progress in that
direction?
Reading your question I assume the answer is no. But what would be good way
to get to know if there are any plans to provide the functionality
You probably want to star issue 1073
http://code.google.com/p/android/issues/detail?id=1073
then you will get updates if it is worked on.
On Apr 16, 5:09 am, Mariano Kamp mariano.k...@gmail.com wrote:
Well, did Cupcake bring some functionality that lets non-Google apps access
the user's
I did. The last comment is mine. But the most recent update is from February
and I thought it would be interesting to know if there is any progress.
On Thu, Apr 16, 2009 at 8:47 PM, dar dher...@gmail.com wrote:
You probably want to star issue 1073
This will be fixed in cupcake, where we have a secure settings area that
nobody outside of the system can touch.
Also keep in mind that GoogleLoginServiceBlockingHelper is not public API.
In fact it is not an Android API at all, it is part of the Google
application suite which will not be on all
On a related note, is there any API today or planned for tomorrow for
accessing the user's Google credentials in a safe way to pass them onto a
Google service?
The actual context is that I have users complaining that they don't want to
give my app their google userid/pw to access Google Reader via
Sorry maybe someone else can help you but I can't; I work on the Android
platform, I am not that familiar with what is going on with the Google apps.
On Fri, Mar 20, 2009 at 1:01 PM, Mariano Kamp mariano.k...@gmail.comwrote:
On a related note, is there any API today or planned for tomorrow for
I have a related question - is android_id implemented on the device
and thus will not change no matter which gmail account is used on that
device?
I am hoping that if a user downloads my app and runs it on one device
that they will get one android_id, and if they also use the same gmail
account
Here is a small snippet;
Log.v(??, attempt to get android_ID);
// GoogleLoginServiceBlockingHelper test;
try {
long A_ID =
GoogleLoginServiceBlockingHelper.getAndroidId
(getApplicationContext());
} catch
On Thu, Feb 26, 2009 at 12:15 PM, strazzere str...@gmail.com wrote:
Here is a small snippet; [...]
I'm sorry to harp on this, but please provide a complete, *compilable*
and *runnable* example, along with what you actually observed when
running it (e.g., log output)
I don't doubt that you are
On Mon, Feb 23, 2009 at 8:31 PM, strazzere str...@gmail.com wrote:
Everything seems to be going smoothly until I get to running the
project and the dalvikvm spits out errors such as rejecting opcode
0x6e at 0x000e which seems to make no sense to me.
Can you provide a bit more context from the
11 matches
Mail list logo
