expo-contacts 57.0.7 → 58.0.8: deprecates 23 API(s)
Compared with 57.0.7: `isAvailableAsync`, `hasContactsAsync`, `shareContactAsync`, `getContactsAsync`, `getPagedContactsAsync`, and 18 more.
registry.npmjs.orgquote checked- 58.0.8from 57.0.7
- Your code23 things to find
Nemotron fixes
In its own wordsread from the page
- isAvailableAsync: Import this method from `expo-contacts/legacy`. This method will throw in runtime.
- hasContactsAsync: Use `Contact.hasAny()` or import this method from `expo-contacts/legacy`. This method will throw in runtime.
- shareContactAsync: Import this method from `expo-contacts/legacy`. This method will throw in runtime.
- getContactsAsync: Use `Contact.getAll()` or import this method from `expo-contacts/legacy`. This method will throw in runtime.
- getPagedContactsAsync: Use `Contact.getAll()` or import this method from `expo-contacts/legacy`. This method will throw in runtime.
- getContactByIdAsync: Use `new Contact(id).getDetails()` or import this method from `expo-contacts/legacy`. This method will throw in runtime.
- addContactAsync: Use `Contact.create()` or import this method from `expo-contacts/legacy`. This method will throw in runtime.
What Teire looks for in your code
- isAvailableAsync (ts)
- hasContactsAsync (ts)
- shareContactAsync (ts)
- getContactsAsync (ts)
- getPagedContactsAsync (ts)
- getContactByIdAsync (ts)
- addContactAsync (ts)
- updateContactAsync (ts)
- removeContactAsync (ts)
- writeContactToFileAsync (ts)
- presentFormAsync (ts)
- addExistingGroupToContainerAsync (ts)
- createGroupAsync (ts)
- updateGroupNameAsync (ts)
- removeGroupAsync (ts)
- addExistingContactToGroupAsync (ts)
- removeContactFromGroupAsync (ts)
Does it reach your code?