Alright, sorry I got confused reading the history because of some fast-forward merges.
Seems all is well in the repo -- but the last plugins release Steven held back contacts due to failing tests, hence whats up on plugins.cordova.io being so stale. -Michal On Fri, Jun 20, 2014 at 2:23 PM, Michal Mocny <[email protected]> wrote: > That may not be right at all. Something seems fishy at first glance, but > its hard to track the history. Ian and I are looking at it. > > > On Fri, Jun 20, 2014 at 2:18 PM, Michal Mocny <[email protected]> wrote: > >> Looks like the last release was based on dev branch ( >> https://github.com/apache/cordova-plugin-contacts/blob/55ba3f2580d2c3bbd1662f49d89043710446220a/www/contacts.js), >> which was closed, but maybe wasn't merged in to master? >> >> -Michal >> >> >> On Fri, Jun 20, 2014 at 2:10 PM, Ray Camden <[email protected]> wrote: >> >>> Ok, so.... doing >>> >>> cordova plugin add org.apache.cordova.contacts >>> >>> brings in org.apache.cordova.contacts/www/contacts.js that does NOT >>> match what I'm seeing in >>> https://github.com/apache/cordova-plugin-contacts/blob/master/www/contacts.js, >>> which was last updated *2* months ago. >>> >>> Any ideas? >>> >>> ________________________________________ >>> From: Ray Camden <[email protected]> >>> Sent: Friday, June 20, 2014 1:07 PM >>> To: [email protected] >>> Subject: Contacts API, iOS >>> >>> (I struggled with whether or not this should go here or the Google >>> Group. Settled on here but if folks think it should be moved, just let me >>> know.) >>> >>> I was building a small test of the pickContact API when I noticed it >>> didn't work in iOS. I opened up a remote debug session with Safari and >>> noticed it had chooseContact. >>> >>> Thinking it was just a doc bug, I corrected it with a pull request and >>> returned to my code. But then my app crashed after selecting a contact. >>> >>> From what I can see, the chooseContact iOS API is: >>> >>> chooseContact : function(successCallback, options) { >>> >>> not >>> >>> chooseContact : function(successCallback, errorCallback) { >>> >>> So something is seriously weird here compared to the original docs. >>> Anyone know what is going on with the plugin? >>> >> >> >
