# App failed to Access meeting content **URL:** \ **Category:** Realtime Media Streams\ **Created:** [July 28, 2026, 2:24am UTC](https://devforum.zoom.us/t/app-failed-to-access-meeting-content/145088 "2026-07-28T02:24:47Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Daniel38](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/daniel38/32/54536_2.png) [@Daniel38](https://devforum.zoom.us/u/Daniel38)\ **Post date:** [July 28, 2026, 2:24am UTC](https://devforum.zoom.us/t/app-failed-to-access-meeting-content/145088/1 "2026-07-28T02:24:47Z")
Hi Zoom Developer Team, I’m currently developing a **General App** that uses **Real-Time Media Streams (RTMS)**. I’m encountering the following error whenever I start RTMS during a meeting: > **“Your App failed to Access meeting content.”** I’ve attached a screenshot of the error. ### ![IMG_7660](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/8/e/8ee6626551f6ba4858a38f8f18b1177f5d4b0d4a.jpeg) ### App Details - **App Type:** General App - **Feature:** Real-Time Media Streams (RTMS) - **RTMS Status:** Enabled - **Meeting SDK:** Not used - **OAuth Scopes:** All required RTMS scopes have been added and the app has been reinstalled. ### What I’ve Tried - Verified that RTMS is enabled in the app configuration. - Reinstalled the app after adding the required scopes. - Tested with both the app owner account and another user. - Confirmed the app launches successfully inside the meeting. Despite this, the app still displays **“Your App failed to Access meeting content.”** Could you please advise: 1. What are the common causes of this error? 2. Are there any additional permissions or account-level settings required for RTMS? 3. Does this indicate the app is not authorized for meeting content, or could it be related to RTMS provisioning on Zoom’s backend? I’ve attached a screenshot of the error for reference. Thank you for your assistance. ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [July 28, 2026, 2:25am UTC](https://devforum.zoom.us/t/app-failed-to-access-meeting-content/145088/2 "2026-07-28T02:25:38Z")
@Daniel38 are you using the sample code to connect to the signaling and media server? ---
**Author:** ![Yek\_Khai](https://avatars.discourse-cdn.com/v4/letter/y/a87d85/32.png) [@Yek\_Khai](https://devforum.zoom.us/u/Yek_Khai)\ **Post date:** [August 13, 2026, 9:51am UTC](https://devforum.zoom.us/t/app-failed-to-access-meeting-content/145088/3 "2026-08-13T09:51:37Z")
Hi Zoom Developer team, I’m hitting the exact same issue: **“Your App failed to Access meeting content”** /“Connection failed” shown in the client’s “Apps that access meeting content” panel — even after fully following the reference implementation. **Setup:** - General App, RTMS enabled, Developer Pack active - Scopes: meeting:read:meeting\_video (confirmed working, see below); tried adding audio/transcript scopes too - Account ID: 7066479118 - App ID: LXgJ4mUjSqKMS9sqboM00Q **Yes, using the sample code** (zoom/rtms-samples, boilerplate/working\_dotnetcore) as the reference for the signaling/media handshake implementation. **What’s actually happening, step by step:** 1. meeting.rtms\_started webhook received correctly, signature validates. 2. Signaling handshake (SIGNALING\_HAND\_SHAKE\_REQ → SIGNALING\_HAND\_SHAKE\_RESP): succeeds, status\_code: 0. 3. Media handshake (DATA\_HAND\_SHAKE\_REQ → DATA\_HAND\_SHAKE\_RESP), requesting media\_type: 2 (Video only, matching this app’s actually-authorized scope): succeeds, status\_code: 0. 4. Client sends msg\_type: 7 (ready-to-receive) with `rtms_stream_id`, per the sample. 5. **Zero MEDIA\_DATA\_VIDEO frames ever arrive.** No errors, no further messages of any kind. 6. Connection times out after ~60 seconds: meeting.rtms\_stopped, stop\_reason: 11 (“connection timed out”). 7. Zoom’s own client simultaneously shows “Connection failed” in the “Apps that access meeting content” panel (screenshot attached). **Also tried, for completeness:** requesting media\_type: 11 (Audio | Video | Transcript, matching the sample’s default) — this gets an explicit hard rejection instead, `status_code: 14` (“Media type invalid value”), which at least confirms the server _does_ validate media\_type against granted scopes rather than silently ignoring unauthorized bits. That makes the silent Video-only failure (a scope we do have) more puzzling, not less. No host-approval popup ever appears during the session. This is fully reproducible, every single attempt, exact same behavior. Happy to share full logs/payloads if useful. ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [August 13, 2026, 12:31pm UTC](https://devforum.zoom.us/t/app-failed-to-access-meeting-content/145088/4 "2026-08-13T12:31:20Z")
@Yek_Khai I’ll push a code update for this, thanks for highlighting. In the latest version of RTMS, we split the media connection for each media. Audio, Video,Chat, Transcript and Sharescreen each have their own media socket connection. In the “unified” model, where all media shares the same websocket connection, you can either have a combination of 2, or use 32 where it will subscribe to all media. It doesn’t work if you have a combination of 3 such as 1 + 2 + 8 ( audio video transcript ). ---
**Author:** ![Yek\_Khai](https://avatars.discourse-cdn.com/v4/letter/y/a87d85/32.png) [@Yek\_Khai](https://devforum.zoom.us/u/Yek_Khai)\ **Post date:** [August 14, 2026, 3:57am UTC](https://devforum.zoom.us/t/app-failed-to-access-meeting-content/145088/5 "2026-08-14T03:57:04Z")
Hi Chun Siong, Thanks for the clarification! Tried both suggestions, neither resolves it: **media\_type: 32 (All)**: handshake succeeds (status\_code: 0), and interestingly the response now echoes back both audio and video media\_params even though I only sent a video block — but still **zero media frames of any kind** , same stop\_reason: 11 timeout at ~60s. **media\_type: 3 (Audio | Video)** : retested this cleanly per your “combination of 2” note, but it’s rejected identically to before: status\_code: 14, “Media type invalid value”. This is the same result whether I’m requesting it alongside Transcript or alone, so it doesn’t look like a Transcript-specific problem. For reference, the account’s “Apps that access meeting content” panel does list this app as having access to both **Audio** and **Video** : so if status\_code: 14 for Audio | Video really is an authorization issue rather than a “combination of 3” issue, that’d be worth knowing, since it contradicts what that panel shows. Current state across everything I’ve tried: - media\_type: 2 (Video alone) → handshake OK, zero frames, timeout - media\_type: 3 (Audio | Video) → hard rejected, status\_code 14 - media\_type: 11 (Audio | Video | Transcript) → hard rejected, status\_code 14 - media\_type: 32 (All) → handshake OK, zero frames, timeout Every path that gets past the handshake ends the same way: no data, stop\_reason: 11. Would it help to have you look at the raw session/rtms\_stream\_id from one of these attempts on your end? Happy to provide the exact IDs and timestamps. ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [August 14, 2026, 5:44am UTC](https://devforum.zoom.us/t/app-failed-to-access-meeting-content/145088/6 "2026-08-14T05:44:08Z")
@Yek_Khai did you check out the latest commit? I’ve tested it and verified it works. I’ll PM you for more information