Denying Keychain access prevents ZoomSDK from being authorized properly
I have noted the previous topics posted here about the new keychain access dialog asking for permission to use “(App Name) Safe Storage” and “(App Name) Safe Meeting Storage”. I see that these are present when launching the official Zoom client too, however in the official client starting/joining a meeting is still possible after choosing “Deny”, while when using the SDK this seems to prevent proper authorization and ZoomSDK.shared().getSettingService() (for example) returns nil if the user chooses Deny. So my questions are:
- Is this expected behavior if the user chooses Deny?
- If so, could the SDK be updated so that meetings are still possible after the user chooses Deny as is possible in the official client?
- Since the dialog doesn’t present a great experience for first time users of our app, could the SDK be updated to allow for opting out of requiring keychain access entirely?
Thanks for any help!