[expo-contacts] GetContactsAsync crash on ios

[amitshabo]

[expo-contacts] GetContactsAsync crash on ios

[ChristopherGabba]

I'm also experiencing this bug for some users.

Sentry capturing this:

[ChristopherGabba]

Okay I ruled it down to the line of code:

    const { data } = await Contacts.getContactsAsync({
      fields: [
        Contacts.Fields.ID,
        Contacts.Fields.Name,
        Contacts.Fields.PhoneNumbers,
        Contacts.Fields.Image,
        Contacts.Fields.ImageAvailable,
      ],
    })

Device Info:

• iOS 17.4.1
• iPhone 13
• expo-contacts 13.0.3

I downgraded our app to expo-contacts 12.8.2 and the bug disappeared and it no longer crashes.

[amitshabo]

Still crashing on expo-contacts 13.0.4, i dont think the department name is the only problem.. i tried also with npx patch-package before the publish and still crash.
any suggestions?

[savkevip]

Same here :/

[ChristopherGabba]

I will spend some time debugging this in the evening today. It happens for one user but not the other with the same code, so I suspect it may be related to a specific contact or something in a weird format causing the crash. Will post details after.

[Gutistavo]

Guys, this freezing issue occurs when a contact in the iPhone has the department field filled. Unfortunately, it hasn't been fixed yet, but to manually correct it, do this:

Access the file:
/node_modules/expo-contacts/ios/Serialization.swift

Change the following line:

   if fieldHasValue(field: person.departmentName) {
-    contact[ContactsKey.department] = person.dates
+    contact[ContactsKey.department] = person.departmentName
   }

Finally, go to the root of your project and run the command to create the correction patch:

npx patch-package expo-contacts

[gabrieldonadel]

This issue was actually fixed here a few weeks ago #28968. I just cherry-picked the commit with the fix to our SDK 51 branch and a new version of expo-contacts will be available soon.

[ChristopherGabba]

@Gutistavo Seems like a really obvious and easy to fix bug. We shall see how long it takes for them to fix...

[gabrieldonadel]

Hi @amitshabo, the fix for this will go into expo go in the next build that we do in the coming weeks. In dev builds/release builds, you can install [email protected] today for the fix

[amitshabo]

Hi @gabrieldonadel , Im currently on dev, installed the [email protected], still crashes. you sure the department was the only problem?

[gabrieldonadel]

If you're running a development build can you share the error given by Xcode when the app crashes?

[ChristopherGabba]

@amitshabo You may need to recompile a new development build for the new version to go live. This did it for me.

[savkevip]

Guys, this freezing issue occurs when a contact in the iPhone has the department field filled. Unfortunately, it hasn't been fixed yet, but to manually correct it, do this:

Access the file: /node_modules/expo-contacts/ios/Serialization.swift

Change the following line:

   if fieldHasValue(field: person.departmentName) {
-    contact[ContactsKey.department] = person.dates
+    contact[ContactsKey.department] = person.departmentName
   }

Finally, go to the root of your project and run the command to create the correction patch:

npx patch-package expo-contacts

I have still the error even I see this is fixed in 13.0.4 - > node_modules... I tried to downgrade the version but nothing helped... getContactsAsync working only if I dont send any arguments but there are no names which I need... only solution is maybe to return to SDK 50?

[gabrieldonadel]

@savkevip If you're running a development build and not using Expo Go, can you share the error given by Xcode when the app crashes?

[savkevip]

@savkevip If you're running a development build and not using Expo Go, can you share the error given by Xcode when the app crashes?

so when I run npx expo run:ios --device on the device everything is ok when I run over the QR code just crashes without error (no error in the console just the app closes) and when I try to run it on Xcode is crashing on the build.

[ChristopherGabba]

@savkevip I think if you are using expo-dev build you need to rebuild your development client with the updated 13.0.4 version.