Authenticating meeting with Android 14 mobile device

I am using Zoom Android SDK v5.16.5.17050 and am getting a crash when authenticating with Zoom on Android 14 device.
Error log:
java.lang.SecurityException: org.alanon.meetings: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn’t being registered exclusively for system broadcasts
at android.os.Parcel.createExceptionOrNull(Parcel.java:3057)
at android.os.Parcel.createException(Parcel.java:3041)
at android.os.Parcel.readException(Parcel.java:3024)
at android.os.Parcel.readException(Parcel.java:2966)
at android.app.IActivityManager$Stub$Proxy.registerReceiverWithFeature(IActivityManager.java:5684)
at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1852)
at android.app.ContextImpl.registerReceiver(ContextImpl.java:1792)
at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:767)
at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:767)
at com.zipow.videobox.broadcast.ZmConfBroadCastReceiver.a(ZmConfBroadCastReceiver.java:23)
at us.zoom.proguard.kl2.a(ZmConfUIStatusMgr.java:5)
at com.zipow.videobox.VideoBoxApplication.initAppForSDK(VideoBoxApplication.java:1)
at com.zipow.videobox.VideoBoxApplication.onSDKCreated(VideoBoxApplication.java:25)
at com.zipow.videobox.VideoBoxApplication.initializeForSDK(VideoBoxApplication.java:55)
at us.zoom.internal.impl.e.a(ZoomSDKImpl.java:62)
at us.zoom.sdk.ZoomSDK.initialize(ZoomSDK.java:1)
at org.alanon.meetings.ui.dashboard.ui.meetings.MeetingsFragment.initZoomSDK(MeetingsFragment.kt:90)

Hey @scot.powers ,

Can you please take a look at this response?

I am facing this issue on Android 14, too.
And it works far on Android 13.

Zoom SDK version: 5.16.6.17198
gradle version: 7.6.3
AGP version: 7.4.2
Kotlin version: 1.7.20

Hi @bobby_hung ,

Please see the following:

So, your Zoom meeting SDK is not support Android 14 for now?

It work for now after downgrading compileSdk and targetSdk from 34 to 33.

Hi @bobby_hung , the team is working on resolving the challenges and I’m happy you were able to troubleshoot with what we’ve been doing!