# SDK Initialization Issue **URL:** \ **Category:** Android\ **Created:** [December 19, 2023, 4:37pm UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432 "2023-12-19T16:37:37Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![vuzix\_greg](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vuzix_greg/32/45663_2.png) [@vuzix\_greg](https://devforum.zoom.us/u/vuzix_greg)\ **Post date:** [December 19, 2023, 4:37pm UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432/1 "2023-12-19T16:37:37Z")
A customer of ours is having trouble with the latest version of our app built with the Meeting SDK. While on their corporate network, the app fails to initialize the SDK. Other networks, such as mobile hotspots work fine. Also, the previous version of our app initializes without any trouble on that same corporate network. Has something changed internally with the SDK that could account for the initialization failing on certain networks? Maybe the endpoints you use have changed? SDK v5.12.2.9109 - initializes SDK v5.16.1.16439 - does not initialize Should also note, this customer is in Japan. I have not received any other reports of this issue. Would it be possible to get a list of servers and ports that should be network whitelisted to aid with SDK initialization? ---
**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:** [December 21, 2023, 8:19am UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432/2 "2023-12-21T08:19:32Z")
@vuzix_greg , 5.12.2 should have stopped working on Nov 4th as the minimum version support is 5.13.5 ---
**Author:** ![vuzix\_greg](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vuzix_greg/32/45663_2.png) [@vuzix\_greg](https://devforum.zoom.us/u/vuzix_greg)\ **Post date:** [December 21, 2023, 3:18pm UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432/3 "2023-12-21T15:18:21Z")
Yes, I realize that. 5.12.2 can’t be used anymore, but the SDK still initializes for this customer. They just can’t join meetings. 5.16 doesn’t initialize. The question was about what changed with the initialization process between the two versions that causes initialize to fail for his customer? ---
**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:** [December 22, 2023, 3:10am UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432/4 "2023-12-22T03:10:39Z")
@vuzix_greg , One thing I think of is on [5.14.10 onwards](https://devsupport.zoom.us/hc/en-us/articles/14383490124813-Zoom-Meeting-SDK-Android-5-14-10), we removed authentication using key and secret directly. You will need to sign a token using key and secret instead of passing them directly into the parameters from 5.14.10 onwards, which means this is similar for 5.16.x too. ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/4/8/48da1a852c1ef6db47f7e0b4d766b409393ef4b2.png) ---
**Author:** ![vuzix\_greg](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vuzix_greg/32/45663_2.png) [@vuzix\_greg](https://devforum.zoom.us/u/vuzix_greg)\ **Post date:** [December 22, 2023, 3:00pm UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432/5 "2023-12-22T15:00:33Z")
Yes, we switched to JWT when the key and secret init APIs were removed. So we know that is not the issue. ---
**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:** [December 26, 2023, 5:32am UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432/6 "2023-12-26T05:32:05Z")
@vuzix_greg are we able to capture the SDK log for 5.16 SDK which are unable to initialize? Please tag me in your response ---
**Author:** ![vuzix\_greg](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vuzix_greg/32/45663_2.png) [@vuzix\_greg](https://devforum.zoom.us/u/vuzix_greg)\ **Post date:** [January 2, 2024, 2:45pm UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432/7 "2024-01-02T14:45:21Z")
Let me see if I can get that for you. I will have to provide the customer with an APK that has the SDK debug flag enabled. ---
**Author:** ![vuzix\_greg](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vuzix_greg/32/45663_2.png) [@vuzix\_greg](https://devforum.zoom.us/u/vuzix_greg)\ **Post date:** [January 18, 2024, 4:00pm UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432/8 "2024-01-18T16:00:54Z")
@chunsiong.zoom I emailed the SDK log files to [developersupport@zoom.us](mailto:developersupport@zoom.us) ---
**Author:** ![vuzix\_greg](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vuzix_greg/32/45663_2.png) [@vuzix\_greg](https://devforum.zoom.us/u/vuzix_greg)\ **Post date:** [January 18, 2024, 4:07pm UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432/9 "2024-01-18T16:07:39Z")
@chunsiong.zoom so the email was rejected. So I created a created a support request (TS0447364). The request was immediately closed, but perhaps you can still access it? If there’s a better way to get you logs, let me know. ---
**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:** [January 19, 2024, 12:45am UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432/10 "2024-01-19T00:45:32Z")
@vuzix_greg I’ll PM you for the logs ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\ **Post date:** [February 18, 2024, 10:46am UTC](https://devforum.zoom.us/t/sdk-initialization-issue/100432/11 "2024-02-18T10:46:08Z")
Closed on February 18, 2024, 10:46am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.