[TIMOB-1860] Android: Empty contacts on Droid 2
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2011-04-17T01:57:22.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 1.5.0 |
Components | Android |
Labels | android, defect, rplist |
Reporter | Bill Dawson |
Assignee | Bill Dawson |
Created | 2011-04-15T03:04:07.000+0000 |
Updated | 2011-04-17T01:57:22.000+0000 |
Description
Kevin getting no contacts when we're using 1.6 contacts api, but all his contacts when using the newer contacts api (via a custom native app). He's on a Droid 2 which runs 2.2. This makes me completely distrust the deprecated contacts api.
Recommend using reflection / class loaders to get at the newer api when it's on a phone that has it.
(from [1da060f10de33e41586e76470b147f0eb95f1b7a]) [#1860 state:open] Introduces CommonContactsApi to get contact information from newer contacts API when available, or older contacts API as fallback http://github.com/appcelerator/titanium_mobile/commit/1da060f10de33e41586e76470b147f0eb95f1b7a"> http://github.com/appcelerator/titanium_mobile/commit/1da060f10de33...
(from [b32c20551b64a2fadbb210dc0b01da141601ef99]) [#1860] Introduction of separation of contact apis between api levels 4 and higher. Level 4 is still called explicitly until a few more level 5 methods are completed. http://github.com/appcelerator/titanium_mobile/commit/b32c20551b64a2fadbb210dc0b01da141601ef99"> http://github.com/appcelerator/titanium_mobile/commit/b32c20551b64a...
(from [6a13666e187f8630c289a2111050a15c06f9ee33]) [#1860 state:fixed-in-qa] Finish implementing the api level 5+ contacts api so it has parity with our contacts api which is based on the deprecated android api. http://github.com/appcelerator/titanium_mobile/commit/6a13666e187f8630c289a2111050a15c06f9ee33"> http://github.com/appcelerator/titanium_mobile/commit/6a13666e187f8...
Though only Kevin has the Droid 2 and has confirmed the problem is fixed on it, this was a major change to our contacts api, so I've put it in fixed-in-qa so QA can hammer away on the api and see how goes.
closing with thanks to Kevin for confirming