You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling Contacts.viewExistingContact(contact); causes the iOS app to crash. However, Contacts.openExistingContact(contact); works well and opens the contact for editing.
There is also this warning in the code:
Conflicting parameter types in implementation of 'viewExistingContact:resolve:reject:': 'JS::NativeContacts::SpecViewExistingContactContact &' vs 'NSDictionary *__strong'
which I believe is due to the fact that the Obj-C implementation expects to get (NSDictionary *) as a parameter, but the auto-generated header from the JS code is creating this signature: - (void)viewExistingContact:(JS::NativeContacts::SpecViewExistingContactContact &)contact resolve:(RCTPromiseResolveBlock)resolve reject:(RCTPromiseRejectBlock)reject;
because in the JS code the signature is: async function viewExistingContact(contact: { recordID: string; }): Promise<Contact | void>
instead of
async function viewExistingContact(contact: Contact): Promise<Contact | void>
The text was updated successfully, but these errors were encountered:
Calling
Contacts.viewExistingContact(contact);
causes the iOS app to crash. However,Contacts.openExistingContact(contact);
works well and opens the contact for editing.There is also this warning in the code:
which I believe is due to the fact that the Obj-C implementation expects to get
(NSDictionary *)
as a parameter, but the auto-generated header from the JS code is creating this signature:- (void)viewExistingContact:(JS::NativeContacts::SpecViewExistingContactContact &)contact resolve:(RCTPromiseResolveBlock)resolve reject:(RCTPromiseRejectBlock)reject;
because in the JS code the signature is:
async function viewExistingContact(contact: { recordID: string; }): Promise<Contact | void>
instead of
async function viewExistingContact(contact: Contact): Promise<Contact | void>
The text was updated successfully, but these errors were encountered: