This repository is the `react-native-update` SDK (branded as Pushy for China and Cresc globally), a production-grade over-the-air (OTA) update library for React Native applications. It enables incremental patching of JavaScript bundles (including Hermes bytecode) and native resources across iOS, Android, and HarmonyOS platforms. The system comprises a JavaScript layer (React context, hooks, client classes) that orchestrates check, download, patch, and switch operations, and native modules on each platform that handle binary patching (via HDiffPatch/LZMA), secure zip extraction, resumable downloads, and a native cold-start check that can recover from crashes without JS involvement. The core patching and decision logic is implemented in C++ and shared across all platforms, enforced by golden-vector test suites. The SDK supports staged rollouts, telemetry, error reporting, crash rescue, and multiple update strategies (silent, alert, etc.). It is not a standalone application but a library integrated into React Native apps, with extensive CI/CD, unit tests, and e2e tests.
HybridCLR is a Unity Editor plugin and runtime library designed to enable native C# hot updates for games using the IL2CPP backend. It achieves this by modifying the IL2CPP runtime to support a hybrid AOT (Ahead-of-Time) and Interpreter execution model, allowing dynamic assembly loading without recompiling the native binary. The system operates through a deep integration with Unity's build pipeline, utilizing Editor-only build processors to analyze metadata, strip unnecessary AOT code, and generate necessary native bridges. Architecturally, the repository is split between Editor tools (metadata analysis, code generation, build hooks) and Runtime components (assembly loading, method dispatch). It relies heavily on native code patching (UnityHook) and custom binary parsing (UnityFS) to intercept and modify Unity's internal behavior. External dependencies include dnlib for IL metadata manipulation and embedded compression libraries (7zip, LZ4) for asset handling. While the solution is technically sophisticated, it carries significant maintenance risks due to its tight coupling with Unity's internal APIs and IL2CPP runtime internals. The codebase maintains compatibility across multiple Unity versions (2019-2023+) through version-specific build processors, but this creates a high surface area for breakage during Unity engine updates. It is a specialized tool for game development rather than a general-purpose library.