# iOS SDK deprecated protocol methods

**URL:** <https://devforum.zoom.us/t/ios-sdk-deprecated-protocol-methods/78773>\
**Category:** iOS\
**Tags:** faq-ios\
**Created:** [November 14, 2022, 6:34pm UTC](https://devforum.zoom.us/t/ios-sdk-deprecated-protocol-methods/78773 "2022-11-14T18:34:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mistermark](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mistermark/32/42988_2.png) [@mistermark](https://devforum.zoom.us/u/mistermark)\
**Post date:** [November 14, 2022, 6:34pm UTC](https://devforum.zoom.us/t/ios-sdk-deprecated-protocol-methods/78773/1 "2022-11-14T18:34:21Z")

</div>

**Description**  
Protocols have deprecated methods, but the methods themselves are not set as optional, so they are causing warnings in every implementation of the protocols: MobileRTCUserServiceDelegate and MobileRTCShareServiceDelegate. If the deprecated methods are implemented, the deprecated method warning is shown, but if they aren’t implemented, the unimplemented protocol method(s) warning is shown, so it’s a catch 22. I’m recommending the new SDK set all deprecated methods as optional in the next update.

**Which iOS Meeting SDK version?**  
5.11.2.3958

---

<div class="post-metadata">

**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:** [December 15, 2022, 4:35am UTC](https://devforum.zoom.us/t/ios-sdk-deprecated-protocol-methods/78773/2 "2022-12-15T04:35:18Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
