# WebView.setWebContentsDebuggingEnabled(true) found in release build — Zoom Meeting SDK Android 6.3.10

**URL:** <https://devforum.zoom.us/t/webview-setwebcontentsdebuggingenabled-true-found-in-release-build-zoom-meeting-sdk-android-6-3-10/142552>\
**Category:** Android\
**Tags:** android, securityreview\
**Created:** [March 23, 2026, 7:30am UTC](https://devforum.zoom.us/t/webview-setwebcontentsdebuggingenabled-true-found-in-release-build-zoom-meeting-sdk-android-6-3-10/142552 "2026-03-23T07:30:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kumar4](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kumar4/32/52704_2.png) [@Kumar4](https://devforum.zoom.us/u/Kumar4)\
**Post date:** [March 23, 2026, 7:30am UTC](https://devforum.zoom.us/t/webview-setwebcontentsdebuggingenabled-true-found-in-release-build-zoom-meeting-sdk-android-6-3-10/142552/1 "2026-03-23T07:30:50Z")

</div>

**Description**

Hi everyone,

I am using Zoom Meeting SDK for Android, version 6.3.10 (build 27979) in my app. During a routine security audit, our security team decompiled our release APK and found that `WebView.setWebContentsDebuggingEnabled(true)` is being called from Zoom’s internal SDK code.

Specifically, it was found in these locations:

- `com.zipow.videobox.ptapp.PTUI.doModulesInitAfterLogin()`

- `com.zipow.videobox.ZoomApplication.onCreate()`

Our app’s own release build has `debuggable false` set, and we do not call `setWebContentsDebuggingEnabled` anywhere in our code. This is coming entirely from the Zoom SDK.

As per Android security best practices and OWASP MASTG guidelines, `setWebContentsDebuggingEnabled(true)` should not be enabled in production/release builds since it allows remote inspection of WebView content through Chrome DevTools.

**My questions:**

1. Is this a known issue? Is anyone else facing this?

2. Is there a plan to fix this in an upcoming SDK version?

3. Is there any workaround or configuration on our side to disable this?

**Which Android Meeting SDK version?**  
6.3.10

**To Reproduce(If applicable)**  
Steps to reproduce the behavior:  
Decompile the apk ( i used jadx ) , and search for WebView.setWebContentsDebuggingEnabled(true) ,

**Screenshots**

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/7/a/7a945e4bfc31de06bd6e4ffb722ad86295e2ed4e.png)

**Smartphone (please complete the following information):**

- Device: [Samsung SM-E146B]
- OS: [e.g. Android 14]

---

<div class="post-metadata">

**Author:** ![enda.zhang](https://avatars.discourse-cdn.com/v4/letter/e/41988e/32.png) [@enda.zhang](https://devforum.zoom.us/u/enda.zhang)\
**Post date:** [March 24, 2026, 10:00pm UTC](https://devforum.zoom.us/t/webview-setwebcontentsdebuggingenabled-true-found-in-release-build-zoom-meeting-sdk-android-6-3-10/142552/2 "2026-03-24T22:00:46Z")

</div>

Hi @Kumar4 ,

Thank you for reaching our to us regarding this question. The logic in SDK for 6.3.10 `doModulesInitAfterLogin()` is not accessible for SDK, so this issue in itself does not pose a security problem for the APK.

If your security team still has the concern, you can call `setWebContentsDebuggingEnabled(false)` in the `onZoomSDKInitializeResult` (ref doc: [Link](https://marketplacefront.zoom.us/sdk/meeting/android/interfaceus_1_1zoom_1_1sdk_1_1_zoom_s_d_k_initialize_listener.html#a6527c86fca3c1d75b9f4a034d67ececb))and `onZoomSDKLoginResult`(ref doc: [Link](https://marketplacefront.zoom.us/sdk/meeting/android/interfaceus_1_1zoom_1_1sdk_1_1_zoom_s_d_k_authentication_listener.html#ac86f8e0c6193470a13d2d74f26104602)) callbacks as a workaround. We will address the issue in the next SDK release.

Thanks!
