# \[iOS Meeting SDK 6.5.1\] Why is there a nested Frameworks folder inside MobileRTC.framework?

**URL:** <https://devforum.zoom.us/t/ios-meeting-sdk-6-5-1-why-is-there-a-nested-frameworks-folder-inside-mobilertc-framework/134552>\
**Category:** Meeting SDK\
**Created:** [June 27, 2025, 1:09am UTC](https://devforum.zoom.us/t/ios-meeting-sdk-6-5-1-why-is-there-a-nested-frameworks-folder-inside-mobilertc-framework/134552 "2025-06-27T01:09:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![darby](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/darby/32/49098_2.png) [@darby](https://devforum.zoom.us/u/darby)\
**Post date:** [June 27, 2025, 1:09am UTC](https://devforum.zoom.us/t/ios-meeting-sdk-6-5-1-why-is-there-a-nested-frameworks-folder-inside-mobilertc-framework/134552/1 "2025-06-27T01:09:08Z")

</div>

**Meeting SDK Type and Version**  
iOS Meeting SDK 6.5.1 (version 6.5.1.26248)

**Description**  
After updating to the Zoom iOS Meeting SDK 6.5.1, I discovered that `MobileRTC.framework` includes a nested `Frameworks` folder inside it. This leads to App Store Connect rejecting the build with the following error:

> **ITMS-90206** : Invalid Bundle - The bundle at ‘Payload/GgugeUncleApp.app/Frameworks/MobileRTC.framework’ contains disallowed file ‘Frameworks’.

This issue did not exist in previous versions such as 6.4.5.

**Error?**

> ITMS-90206: Invalid Bundle - The bundle at ‘…/MobileRTC.framework’ contains disallowed file ‘Frameworks’.

**Troubleshooting Routes**

- Reproduced the issue in a clean Xcode project.
- Compared the 6.5.1 SDK with 6.4.5, and confirmed the nested folder only exists in 6.5.x.
- Confirmed the IPA includes the nested Frameworks folder after archiving.
- Attempted to manually remove the nested folder, but this results in runtime errors.
- Verified correct `CFBundleShortVersionString` and `CFBundleVersion` format in Info.plist.
- Used the latest Xcode 16 and iOS SDK 18.

**How To Reproduce**

1. Download and integrate Zoom iOS Meeting SDK 6.5.1 (26248)
2. Build and archive an iOS app in Xcode
3. Inspect the resulting `.ipa` → MobileRTC.framework includes `Frameworks` folder
4. Submit to App Store → receive **ITMS-90206** rejection

---

<div class="post-metadata">

**Author:** ![thinktapwork](https://avatars.discourse-cdn.com/v4/letter/t/e5b9ba/32.png) [@thinktapwork](https://devforum.zoom.us/u/thinktapwork)\
**Post date:** [June 29, 2025, 1:44pm UTC](https://devforum.zoom.us/t/ios-meeting-sdk-6-5-1-why-is-there-a-nested-frameworks-folder-inside-mobilertc-framework/134552/2 "2025-06-29T13:44:04Z")

</div>

Can confirm this issue. Having the same problem uploading. None of the last 3 versions of the SDK have been submittable to the App Store for various reasons.

---

<div class="post-metadata">

**Author:** ![darby](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/darby/32/49098_2.png) [@darby](https://devforum.zoom.us/u/darby)\
**Post date:** [June 30, 2025, 8:00am UTC](https://devforum.zoom.us/t/ios-meeting-sdk-6-5-1-why-is-there-a-nested-frameworks-folder-inside-mobilertc-framework/134552/3 "2025-06-30T08:00:20Z")

</div>

Thanks for sharing this!

I’m looking forward to a positive update!!

---

<div class="post-metadata">

**Author:** ![thinktapwork](https://avatars.discourse-cdn.com/v4/letter/t/e5b9ba/32.png) [@thinktapwork](https://devforum.zoom.us/u/thinktapwork)\
**Post date:** [July 2, 2025, 12:47pm UTC](https://devforum.zoom.us/t/ios-meeting-sdk-6-5-1-why-is-there-a-nested-frameworks-folder-inside-mobilertc-framework/134552/4 "2025-07-02T12:47:19Z")

</div>

Any word from Zoom on this issue?

---

<div class="post-metadata">

**Author:** ![Spencer3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/spencer3/32/70118_2.png) [@Spencer3](https://devforum.zoom.us/u/Spencer3)\
**Post date:** [July 8, 2025, 8:31pm UTC](https://devforum.zoom.us/t/ios-meeting-sdk-6-5-1-why-is-there-a-nested-frameworks-folder-inside-mobilertc-framework/134552/5 "2025-07-08T20:31:08Z")

</div>

We are experiencing the same issue. Any updates on this?
