Apple Cracks Down on iOS Hot‑Update Frameworks: What Developers Need to Know

Yesterday morning many iOS developers received warning emails from Apple

The email said that using hot‑update solutions that bypass App Store review violates Apple's developer agreement and poses security risks, and developers must remove the related code, frameworks or SDKs and resubmit for review.

The news caused a stir in the iOS community

Common iOS hot‑update solutions include JSPatch, React Native (RN), Weex, and the foreign service Rollout. So far Apple appears to target JSPatch and Rollout, as well as third‑party SDKs that embed JSPatch (e.g., GeTui, AMap) because they can execute arbitrary Objective‑C methods via JavaScript.

React Native engineers responded on GitHub that RN is not affected, and Weex developers reported no immediate issues

Rollout’s CEO issued a statement saying they are not in violation and are contacting Apple for possible adjustments

JSPatch author Bang posted a blog advising developers to stop using JSPatch for now and to negotiate with Apple’s review team.

Bugly Announcement on Apple Review Policy Changes

Bugly’s iOS hot‑update SDK also bundles JSPatch, so until a clear conclusion is reached, products using Bugly’s hot‑update SDK should switch to the exception‑reporting‑only SDK to avoid review risk.

The exception‑reporting SDK is unaffected; no changes are needed if you already use it.

Integrate via CocoaPods

pod 'Bugly'

Remember to remove BuglyHotfix.

Manual Integration

Remove BuglyHotfix.framework from the project.

Download the Bugly iOS SDK from https://bugly.qq.com/ and drag Bugly.framework into the Xcode project (check “Copy items if needed”).

Add the following libraries:

SystemConfiguration.framework

Security.framework

libz.dylib or libz.tbd

libc++.dylib or libc++.tbd

For any questions, contact support QQ: 800014972.