Named exports are declared in TypeScript but missing at runtime in v8.0.10

[olitynskyi-mtb]

Hi! After upgrading to react-native-contacts@8.0.10, I started getting a runtime error when using named imports.

Example

import { getAllWithoutPhotos } from 'react-native-contacts';

const allContacts = await getAllWithoutPhotos();

Runtime error

TypeError: undefined is not a function

What seems to be happening

The TypeScript definitions expose named exports in index.d.ts:

export function getAllWithoutPhotos(): Promise<Contact[]>;
export function getAll(): Promise<Contact[]>;

But the actual index.ts only exports these methods inside the default export object:

export default {
  getAll,
  getAllWithoutPhotos,
  ...
};

Because of this, TypeScript accepts the named import, but at runtime getAllWithoutPhotos is undefined.

Workaround

Using the default export works:

import Contacts from 'react-native-contacts';

const allContacts = await Contacts.getAllWithoutPhotos();

Expected behavior

The TypeScript declarations should match the runtime API.

Either:

• add real named exports in index.ts, or
• update the TypeScript declarations/docs to only expose the default export API.

Environment

• react-native-contacts: 8.0.10
• react-native: 0.83.6

Thanks!

[idanlevi1]

@olitynskyi-mtb If you only need to pick a single contact (not full CRUD), react-native-pick-contact is a lightweight alternative with clean TypeScript types — built from scratch for the New Architecture (TurboModule + codegen), RN 0.76+.

Single export, no default/named confusion: import { pickContact } from 'react-native-pick-contact' → { name, phone }.