Yes Dmitri, this is exactly what I am doing -- I am not manually
inserting records into the contacts db like the test case does, but
there is definitely a contact with a mobile phone number
617939 (with real digits, not xs), and when I open a cursor on
the query:
Uri filterUri1 =
Then it has to be an emulator issue, because the test passes fine on Droid.
See if you can read the phone number using the plain Data.CONTENT_URI API.
If you can, the issue is indeed with the lookup URI.
On Dec 5, 2009 8:37 AM, ghassett greghass...@gmail.com wrote:
Yes Dmitri, this is exactly
Hi Greg,
Take a look at the testPhonesFilterQuery unit test we have for
verifying the behavior in question:
http://android.git.kernel.org/?p=platform/packages/providers/ContactsProvider.git;a=blob;f=tests/src/com/android/providers/contacts/LegacyContactsProviderTest.java;hb=HEAD
Is what it's
Hey Dmitri --
I have a question regarding the legacy apps only having access to the
primary account. I am writing an application that interfaces with
contacts and started on it before 2.0 was released. I am developing
with a Motorola CLIQ running 1.5 and my app works fine. Today, I
purchased a
On Fri, Nov 6, 2009 at 6:31 PM, Ravi textlo...@gmail.com wrote:
Now 2.0 Breaks every thing.
Wow that's pretty over-the-top. The original contacts API still works, as
long as you weren't using private parts of it, and only for the primary
Google account. So it still gives you the same
And as we've said repeatedly for everything, if you use private APIs
you will break in the future, so that shouldn't be a surprise.
You can also get your name on my handy dandy androidhallofshame
website for using private APIs. :)
On Nov 17, 1:31 pm, Dianne Hackborn hack...@android.com wrote:
Both Wow! and over-the-top. Now I am excited. This pattern/technique
was lifted from a distinguished Android pro's recent textbook. So
does the wow imply there is a better way to accomplish the mission? I
think I considered the contact PICK Intent, but I need to allow the
user to select
How do we then get all contacts/phonenumbers from all accounts?
If I use the new Contacts API and send an ACTION.PICK for phone
numbers like
Intent i = new Intent(Intent.ACTION_PICK,
android.provider.ContactsContract.CommonDataKinds.Phone.CONTENT_URI);
it doesn't give me for example Facebook
It's deprecated, not removed. The old API is still functional, but with
restrictions:
1. If your app was using something non-public, that part is likely to break.
We tested a bunch of apps on the market against the legacy API - most
worked, but some did not. Those were the cases when the app
Could you post the exact Uri you're passing to query()? As the
javadoc describes, you need to append a filter string to the
CONTENT_FILTER_URI so it knows what to filter on.
Uri lookupUri = Uri.withAppendedPath(PhoneLookup.CONTENT_URI, phoneNumber);
Also, you might be able to skip your second
Hold up... I'm confused. Are you saying that Contacts portion of the
SDK is deprecated? Whatever happened to stick to the SDK because
those are stable apis that won't break in future versions? Very
disappointing...
On Oct 30, 11:12 am, Jeff Sharkey jshar...@android.com wrote:
Could you post the
The original, public android.provider.Contacts APIs that has shipped
since Android 1.0 are still very much supported, but are now marked as
deprecated. There are additional features (like multiple accounts)
that will require upgrading to the new
android.provider.ContactsContract APIs to access.
Jeff, thanks for clarifying. I'd hate to have seen a bunch of apps
break in the meantime.
On Oct 30, 1:26 pm, Jeff Sharkey jshar...@android.com wrote:
The original, public android.provider.Contacts APIs that has shipped
since Android 1.0 are still very much supported, but are now marked as
13 matches
Mail list logo
