# Zoom android sdk integration in android dynamic feature module

**URL:** <https://devforum.zoom.us/t/zoom-android-sdk-integration-in-android-dynamic-feature-module/7611>\
**Category:** Android\
**Created:** [January 21, 2020, 5:46am UTC](https://devforum.zoom.us/t/zoom-android-sdk-integration-in-android-dynamic-feature-module/7611 "2020-01-21T05:46:23Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![Farbklex](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/farbklex/32/13069_2.png) [@Farbklex](https://devforum.zoom.us/u/Farbklex)\
**Post date:** [September 23, 2020, 12:16pm UTC](https://devforum.zoom.us/t/zoom-android-sdk-integration-in-android-dynamic-feature-module/7611/15 "2020-09-23T12:16:26Z")

</div>

Ah, yes this is a problem with how the zoom sdk tries to access some raw resources. Zoom SDK tries to access the resources by looking them up with the package name of the main app module. However, the resources are in the separate dynamic feature module. The only workaround I found is to extract the raw resources (around 450 KB) and copy them in the main app module like this:

1. Unzip the `mobilertc.aar` file
2. Copy the content of the `mobilertc\res\raw` folder into your apps raw folder (for example: `app\res\raw`)

This is hacky. When zoom updates their SDK, we need to make sure to repeat this copy step again. But it allows us to save space and install the rest of the zoom SDK only when it’s required.

---

_[View the full topic](https://devforum.zoom.us/t/zoom-android-sdk-integration-in-android-dynamic-feature-module/7611)._
