Realm® build errors in 2026 and how to fix them
The last realm-js release is 20.2.0, from August 2025. Since then, new React Native, Xcode, Expo and Google Play versions have broken builds that used to work. Each page below gives the exact error, the cause, a manual workaround when there is one, and the fix with afterdb.
Updated 9 November 2026.
-
iOS build · Xcode 26.4
'is_pod' cannot be specializedA header shipped in realm 20.2.0 breaks with Xcode 26.4's C++ library. #7115
-
iOS link · React Native 0.86+
Undefined symbols for architecture …(jsi::Value)The RealmJS pod misses React Native dependencies when pods are built as frameworks. #7157
-
Install · CI, Node 22
npm cihangs onprebuild-install, orFailed to download prebuild for RealmAn install-time download from static.realm.io that can hang in CI, and a 404 on Node 22. #7119, #7068
-
Android build
CMake Error: Downloading ... Failed(OpenSSL from static.realm.io)The Android build downloads OpenSSL each time CMake configures a clean build. #7044
-
Google Play · 16 KB pages
librealm.soflagged as not 16 KB compatibleFrom 1 February 2027, Google Play blocks updates without 16 KB support. #7129
-
Android release · R8, Expo SDK 58
Crash at start:
ClassNotFoundException: io.realm.react.util.SSLHelperR8 removes a class that only native code uses. Found while testing afterdb.
-
Install · pnpm, Yarn
ENOENTonrealm-core/dependencies.ymlinsubmit-analyticsThe postinstall analytics script reads a file missing from the package. #7126, #7048
-
Android build · @realm/react
Failed to apply plugin 'com.facebook.react.rootproject'@realm/react 0.20.0 can install a second react-native. #7066
The fix with afterdb
afterdb is an independent open-source fork of the realm-js SDK v20 (Apache-2.0) that we maintain. It fixes the build and install errors above for apps on realm 20.x without Device Sync. For 16 KB pages, every 64-bit native library in our test app passes the 16 KB checks. It is not an official Realm release.
"realm": "npm:@pomwik/afterdb@20.3.0",
"@realm/react": "npm:@pomwik/afterdb-react@0.20.1"Then reinstall, run pod install on iOS, and rebuild. For Expo dev builds, run npx expo prebuild --clean. Your code keeps import Realm from "realm".
Tested with React Native 0.88.1 on Android 7, 11 and 16 emulators and on Android 16 with 16 KB pages; with React Native 0.86.3 and 0.87.1 and Expo SDK 56, 57 and 58 on the 16 KB emulator; and on the iPhone simulator with React Native 0.88.1 on Xcode 26.4.1 and 26.6. Not tested yet: real devices, iOS with React Native 0.86 or 0.87 or with Expo, and realm 10, 11 or 12. Details: the compatibility matrix on GitHub.
Not fixed by afterdb
- Debug builds on React Native 0.83 and later can throw
Accessing object which has been invalidated or deleted. It comes from React (react/react #35126), and release builds are not affected. Workarounds are listed in the afterdb README. See also #7086. - Bugs inside the Realm engine itself: afterdb uses the upstream engine unchanged.
- Device Sync and the old React Native architecture.
Planning to leave Realm?
We compare afterdb, op-sqlite, expo-sqlite, WatermelonDB, PowerSync and Ditto in Leaving Realm in 2026: your options.
Need help? Send your versions and the full error for a free 15-minute check. We reply within 12 hours.