Hello All! I run a lot of Zoom Webinars without any trouble - but today we experienced a pretty nasty glitch. 

- The entire screen went Green - no way to get it back. Just restarted Zoom and then the video was just black. Restarted the computer and then it seemed to work fine. Worried about future webinars. 

Till 12/12/25 evening we were able to host live meetings & attendees were able to join. But from 12/12/2025 8:30pm IST evening, it is Unable to connect zoom webinars, Zoom App created is of type Meeting SDK using SDK credentials SDK key , SDK Secret.
“meetingService” is returning null. We need to get value or zoom won't start from Mobile Android.

We have been using Zoom Meeting SDK in our applications for iOS and Android (mobile) and Windows UWP ( Desktop) since a while.

On December 12th 2025, our mobile apps (iOS + Android) stopped joining live classes, while the desktop/UWP app continues to work.

Issue Summary

• Platform affected: iOS (primary) and Android (also impacted)
• Platform not affected: Windows UWP desktop app
• User-visible symptom: Mobile shows “Unable to connect zoom” / join fails for live classes
• Root error: MobileRTCAuthError.tokenWrong (raw value 11) during SDK authentication on iOS, more. Same with Android
• SDK auth state: MobileRTC.shared().isRTCAuthorized = false
• Meeting SDK Version: 6.0.2.21328

iOS Debug Logs:

ZOOM AUTH: MobileRTCAuthError(rawValue: 11) raw=11

ZOOM isRTCAuthorized=false

ZOOM callStack:

0 ACE Online.debug.dylib 0x0000000104cf1574 $s10ACE_Online11AppDelegateC21onMobileRTCAuthReturnyySo0fG5ErrorVF + 884

1 ACE Online.debug.dylib 0x0000000104cf2298 $s10ACE_Online11AppDelegateC21onMobileRTCAuthReturnyySo0fG5ErrorVFTo + 44

2 libdispatch.dylib 0x000000010bc78584 _dispatch_call_block_and_release + 32

3 libdispatch.dylib 0x000000010bc92064 _dispatch_client_callout + 16

4 libdispatch.dylib 0x000000010bcb2f98 _dispatch_main_queue_drain.cold.5 + 876

5 libdispatch.dylib 0x000000010bc88548 _dispatch_main_queue_drain + 180

6 libdispatch.dylib 0x000000010bc88484 _dispatch_main_queue_callback_4CF + 44

7 CoreFoundation 0x000000019c112c30 AE3C9338-0166-397A-9643-356B14F6EE58 + 445488

8 CoreFoundation 0x000000019c0b6394 AE3C9338-0166-397A-9643-356B14F6EE58 + 66452

9 CoreFoundation 0x000000019c0b7adc

Sample token used:

"eyAiYWxnIjogIkhTMjU2IiwgInR5cCI6ICJKV1QiIH0.eyAiYXBwS2V5IjogImhZWG1Zb1BtVVZJbUl6ejExU1o4Q3RHYWdoMEdDRFZzQU5kUyIsICJpYXQiOiAxNzY1NjQ0MjI5LCAiZXhwIjogMTc2NTY1MTQyOSwgInRva2VuRXhwIjogMTc2NTY1MTQyOSwgInVzZXJJRCI6ICIxMjM0NTY3ODkwIiwgInVzZXJOYW1lIjogIkpvaG4gRG9lIiB9.TcRU3PS32cPUk4iG7_Hq7Jp8rX_OG6zDEsECz2qD6Xo"

Failing IOS Code Snippet:
"

if let meetingService = MobileRTC.shared().getMeetingService(),

let zoomMeet = zoomMeet {

   meetingService.delegate = self

   let joinMeetingParameters = MobileRTCMeetingJoinParam()

   joinMeetingParameters.meetingNumber = zoomMeet.meetingID

   joinMeetingParameters.password = zoomMeet.password

   joinMeetingParameters.webinarToken = zoomMeet.token

   meetingService.joinMeeting(with: joinMeetingParameters)

} else {

   print("Failed to fetch meetingService")

}

Can you validate if any recent enforcement/policy changes might cause sudden auth rejections for existing integrations?

Can you confirm what exact JWT claims are required for the current iOS Meeting SDK auth (e.g., whether sdkKey must be present in addition to appKey)?

The claims in the Desktop App(Working) has sdkKey, role, and mn. We have tried updating these in mobile but no luck.

Please advise on the likely causes issue and the recommended corrective steps.

Please note our "There is a business impact due mobile app outage."

When recording (or streaming to YouTube) webinars, the branding name tags are HUGE and when multiple people are on screen do not scale properly, and obscure the view of those on camera. This used to not be an issue. The change happened sometime between - Jan 10, 2025 (last good looking recording with scaled name tags) and Jan 24, 2025 (first bad name tag scaling). 

Please advise.

We stream in-person lectures to at home attendees.  All technology including mics and the laptop go through a system that projects into the room and to the audience at home (through Zoom).  When our lecture speaker includes videos in the PowerPoint presentation, a few issues happen with the volume.  Attendees on Zoom are only able to hear choppy/underwater sound clips (it's like a mix of the speaker talking and the video--just jumbled noise).  Also, attendees are saying after the videos are played, the speakers volume gets really low for a minute then comes back to normal.  How can we 1. Have a video play with the volume from both the video and speaker audible, and 2. Regulate the volume levels so the speaker's mic doesn't dip after videos are played.  Thanks! 

I sell my coaching program through webinar zooms. I would love to add to my landing pages and emails an "Add to Calendar" BUTTON to improve show-up rates. I hate having to pay AddEvent over $30 a month just for that, when it feels like a feature that would need to be included in the Zoom webinar subscription.

Is there a way to do this that I'm missing?

I'm trying to use the incoming livestream feature on a webinar and I'm trying to stream from a Blackmagic ATEM Mini Pro ISO. I copied the server URL and stream key from my webinar session into the ATEM Control Software and hit "On Air" to begin streaming, but the incoming livestream popup on Zoom shows "No data" where the stream should be.

I updated both the ATEM software (10.0) and the Zoom Workplace app (6.6.0) to their most recent versions.

I tried streaming from OBS to the same webinar session to see if Zoom wasn't accepting the incoming stream for some reason, and streaming from OBS worked. I also tried streaming from my ATEM to YouTube and Facebook to see if the ATEM wasn't sending a stream, but that worked as well. So the ATEM seems to be able to send a stream and Zoom seems to be able to receive one, but I can't get the two to work together.

Ideally I would love to be able to stream into the webinar instead of connecting the ATEM as a webcam via USB because the ATEM only has one USB output and I would like to use it to record ISO feeds and cut decisions to an SSD instead.