Context
The ed-tech company ships a native C and C++ DRM SDK for Android and iOS, used inside its React Native app. In 2026 I was release owner and the main debugger.
The problem
Fields reports said some Android builds just quit. I did not know why. The SDK also had a CPU spin on iOS and store rejections to clear.
What I did
I owned more than 15 releases in about 7 weeks.
I traced the quitting builds with a dlopen harness on a real phone. A vendor trial licence in the code protector made 10 Android versions exit silently. I shipped an unprotected build first, then moved to a commercial licence with a build guard that refuses any trial path.
On iOS, listening sockets died after suspend and resume, and 16 server workers spun at 430 to 550% CPU. I added a self-healing listener that rebinds.
I rewrote the encrypted download engine with range resume, 4 parallel segments, and hardware AES.
I fixed an App Store rejection for private APIs, and false anti-debug triggers that closed the app for real users.
Key decision
When I found the trial problem, I shipped an unprotected build to stop the damage before the licence was sorted. It lowered protection for a while.
The reason was that bricked apps hurt learners right now, while the protection gap was a risk I could close next.
Result
More than 15 releases shipped, the 10-version outage was found and fixed, and the 430 to 550% CPU spin is gone.
What I learned
I would add the build guard from the start. A check that fails on trial paths would have found this before release.
Stack
- C
- C++
- JNI
- Objective-C
- OpenSSL
- libcurl
- NDK
