Thank you for the information @elaine.ku . I’ll be refreshing [@zoom/react-native-videosdk - npm] all day Friday.
This bug being introduced in 1.7.x has put us in quite a pickle because we haven’t been able to release an update to our app of the library above 1.6.x, but you guys are going to stop supporting 1.6.x on Saturday. So we have a single day to load it in and test and push the update for apple to approve. It’ll be quite a day 
Looks like if disable ENABLE_CALLKIT_VOIP_MEETING from MobileRTCCallKitManager.h
#define ENABLE_CALLKIT_VOIP_MEETING 1
to
#define ENABLE_CALLKIT_VOIP_MEETING 0
I am able to take control of this again.
Can I make a feature request for the RN Zoom Video SDK to make this an option when initializing the provider with ZoomVideoSdkProvider? so Its back under the developers control. This is especially important since we’re using other libraries / systems to handle all the native CallKit / ConnectionService (android) functionality.
But this might let us actually get a few days of testing to release before you remove 1.6.x!!!
Hi @ray.elward,
I’ve added an enableCallKit param in the InitConfig. If you would like to disable the CallKit, please set it as false. This param will be available in our latest release 1.11.0 which will be released this week.
Thank you
Elaine
Amazing.
Thank you!
Hello I see its published on the marketplace. I’m wondering when it’ll be pushed to npm? based on the history it looks like you guys tend to publish to npm that repo sometime between the same day (1.10.10) and a couple months (1.7.5).
What do you think the lag time on publishing this one will be?
Sorry, I am currently experiencing the same problem. Can you elaborate on what InitConfig is? Is it the same as ZoomVideoSDKInitParams? I am trying to find how to access enableCallKit but am not sure where exactly to look for it.
Thanks for your help!
Hello @elaine.ku ,
I am using just ZoomVideoSDK for iOS, no wrappers as far as I know.
Hi @riana.soumi ,
If you’re testing on our VSDK iOS sample App, you’ll find there’s #define ENABLE_CALLKIT_VOIP_MEETING 0 in our SDKCallKitManager.h. You can set it to 0 or 1 to decide whether you would like to enable the CallKit.
Thank you
Elaine
I am actually not testing your sample App, I am trying to migrate from Twilio to using ZoomVideoSDK to support calls in our product app. Is there any way to set this value in the scenario I just explained?
Okay, I finally get it - it seems like this setting is only possible inside of your wrappers for reactNative etc, is that correct?
Would it be possible to add ENABLE_CALLKIT_VOIP_MEETING for native ZoomVSDK for iOS too? We really want to be able to control CallKit on our side - currently both ZoomVSDK and us try to control it and it causes conflicts.
Hi @riana.soumi,
The CallKit isn’t part of our SDK, it is an implementation in our native sample App. If you do not need the CallKit in the application, you do not need to implement it.
Thank you.
Elaine
I understand that CallKit is not part of your SDK, but I’m encountering an issue similar to the one described by the original poster. It appears that the ZoomVSDK is triggering CallKit to call provider(_ provider: CXProvider, perform action: CXSetMutedCallAction), with action.isMuted set to true. This results in an inconsistency on our end. Additionally, action.isMuted seems to be set to true when the device is running iOS 17 or later.
So, we are looking for a way to prevent this CXSetMutedCallAction from being triggered, if possible.
I hope my explanation is clear, but please let me know if you need any further details.