Answered

No callback found

  • 4 October 2023
  • 3 replies
  • 411 views

Hello,

I am using the React Native SDK.

Since the last upgrades (from 4 to 6), I get this type of error when calling Intercom.sendTokenToIntercom in JS side.

 WARN  [Error: Error in sendTokenToIntercom]
ERROR Invariant Violation: No callback found with cbID 31610 and callID 15805 for IntercomModule.sendTokenToIntercom - most likely the callback was already invoked. Args: '[true]', js engine: hermes

I did : 
- Full cleaning of cache (node_modules, xcode...etc)
- downgrading from 4 to 6.0.1.

No success.
I don’t know if it comes after upgrades of another packages.
But the rest works well (messenger...etc). Except this call.

If you have any idea?
​​​​​​​Thank you !
 

React Native 0.72.5
Xcode 15
iOS 17

icon

Best answer by Jacob Cox 8 October 2023, 23:16

View original

3 replies

Userlevel 4
Badge +5

Hi @Erwan !

This looks like an issue that might be specific to your app’s unique setup. You’ll want to chat with our Support team for an issue like this. I’m going to send this conversation their way and they will reach out to you in a day or two via the email address that you signed up with.

Did you reach any satisfying conclusion with this @Erwan? Having the same issue, @intercom/intercom-react-native library being upgraded from 4.x to 6.x and getting the following error

ERROR  Invariant Violation: No callback found with cbID 3911 and callID 1955 for  IntercomModule.sendTokenToIntercom - most likely the callback was already invoked. Args: '[{"code":"302","message":"Error in sendTokenToIntercom","domain":"IntercomSDKErrorDomain","userInfo":{"NSLocalizedDescription":"ERROR - Failed to register a device token - push notifications are not enabled on the host device"},"nativeStackIOS":["0   Beryl Test                          0x0000000100a90b40 RCTJSErrorFromCodeMessageAndNSError + 112","1   Beryl Test                          0x0000000100a23c96 __41-[RCTModuleMethod processMethodSignat...(truncated)...","2   Beryl Test                          0x00000001016c6c35 __56-[IntercomModule sendTokenToIntercom:...(truncated)...","3   Intercom                            0x00000001119f966f IntercomSDK_PINRemoteImageManagerSubclass...(truncated)...","4   libdispatch.dylib                   0x00000001215f7a90 _dispatch_call_block_and_release + 12","5   libdispatch.dylib                   0x00000001215f8d3a _dispatch_client_callout + 8","6   libdispatch.dylib                   0x0000000121607ac0 _dispatch_main_queue_drain + 1420","7   libdispatch.dylib                   0x0000000121607526 _dispatch_main_queue_callback_4CF + 31","8   CoreFoundation                      0x000000011f24b850 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9","9   CoreFoundation                      0x000000011f24618b __CFRunLoopRun + 2463","10  CoreFoundation                      0x000000011f245409 CFRunLoopRunSpecific + 557","11  GraphicsServices                    0x0000000126f4f187 GSEventRunModal + 137","12  UIKitCore                           0x000000014c6ac3a2 -[UIApplication _run] + 972","13  UIKitCore                           0x000000014c6b0e10 UIApplicationMain + 123","14  Beryl Test                          0x0000000100223c60 main + 96","15  dyld                                0x000000010e2633ee start_sim + 10","16  ???                                 0x0000000205fe2366 0x0 + 8690475878"]}]', js engine: herme

Are you able to assist @Jacob Cox?

Userlevel 4
Badge +5

Hi @Huw Martin 

It looks like this type of issue is normally due to your app running the sendTokenToIntercom call before the user is logged into your app. Can you make sure you’re making those calls in the correct order?

 

If you are and you’re still having the issue then I would encourage you to write into our Support team via the Messenger in your workspace or at team@intercom.io and they can dig into this further with you!

Reply