VoiceConnectionServices not being invoked even when RNCallKeepModules are

[GlennAzx]

Bug report

• I've checked the example to reproduce the issue.

• Reproduced on:

• Android

• iOS

Description

Followed guide to

Steps to Reproduce

Followed the installation steps in the GitHub repository for a fresh React Native project integrated with Firebase Cloud Messaging (FCM) to send POST payloads. However, the displayIncomingCall method does not work, even when trying to simulate a call locally. Logs indicate that VoiceConnectionService is not triggered when displayIncomingCall is called.

The AndroidManifest.xml file has been checked, and phone profile and permissions have also been verified, but the issue persists.

Versions

- Callkeep: 4.3.16
- React Native: 0.76.3
- iOS: 
- Android: 29
- Phone model: Android Studio 10.0 ("Q") | x86

Logs

12-13 09:25:07.534 29244 29297 I ReactNativeJS: Simulating incoming call...
12-13 09:25:07.537 29244 29298 D RNCallKeep: [RNCallKeepModule] hasPhoneAccount check - isConnectionServiceAvailable: true
12-13 09:25:07.561 29244 29298 D RNCallKeep: [RNCallKeepModule] hasPhoneAccount check - hasPermissions: true
12-13 09:25:07.566 29244 29298 D RNCallKeep: [RNCallKeepModule] hasPhoneAccount check - phoneAccount exists: true
12-13 09:25:07.572 29244 29298 D RNCallKeep: [RNCallKeepModule] hasPhoneAccount check - phoneAccount enabled: true
12-13 09:25:07.626 29244 29298 D RNCallKeep: [RNCallKeepModule] displayIncomingCall, uuid: test-call-uuid-12345, number: +1234567890, callerName: Test User, hasVideo: true, payload: null
12-13 09:25:07.626 29244 29298 D RNCallKeep: [RNCallKeepModule] listenToNativeCallsState
12-13 09:25:07.636  2007  2035 E memtrack: Couldn't load memtrack module
12-13 09:25:07.636  2007  2035 W android.os.Debug: failed to get memory consumption info: -1
12-13 09:25:08.014 26277 26277 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.feedback.internal.IFeedbackService dat=chimera-action: cmp=com.google.android.gms/.chimera.GmsBoundBrokerService }
12-13 09:25:08.016  2007  2035 E memtrack: Couldn't load memtrack module
12-13 09:25:08.016  2007  2035 W android.os.Debug: failed to get memory consumption info: -1
12-13 09:25:08.512  1753  2443 E GnssHAL_GnssInterface: gnssSvStatusCb: a: input svInfo.flags is 8
12-13 09:25:08.512  1753  2443 E GnssHAL_GnssInterface: gnssSvStatusCb: b: input svInfo.flags is 8
12-13 09:25:09.513  1753  2443 E GnssHAL_GnssInterface: gnssSvStatusCb: a: input svInfo.flags is 8
12-13 09:25:09.513  1753  2443 E GnssHAL_GnssInterface: gnssSvStatusCb: b: input svInfo.flags is 8
12-13 09:25:10.513  1753  2443 E GnssHAL_GnssInterface: gnssSvStatusCb: a: input svInfo.flags is 8
12-13 09:25:10.513  1753  2443 E GnssHAL_GnssInterface: gnssSvStatusCb: b: input svInfo.flags is 8


12-13 09:25:10.666  1744  1934 W audio_hw_generic: Not supplying enough data to HAL, expected position 24165740 , only wrote 24029333```

[JoBolNex]

We had the same issue on our side and after some investigation, it seems that android.os.Looper is the one 'blocking' the thread. We did a fix on our side and it fixed => #825