Current releases
| Component | Version | Distribution |
|---|---|---|
| Android native SDK | 3.0.5 | Public GitHub release AAR |
| iOS CocoaPod | 3.0.5 | NosmaiCameraSDK |
| iOS framework archive | v3.0.5 | Public GitHub release ZIP used by the 3.0.5 podspec |
| Flutter package | 1.0.3 | nosmai_effects_sdk on pub.dev and GitHub release v1.0.3 |
| React Native | 1.0.0 | @nosmai/react-native-effects-sdk on npm and GitHub release 1.0.0 |
| Web | 0.2.0 developer preview | Authorized preview package |
Flutter 1.0.3 is the current public package and is compatible with Android Effects SDK 3.0.5. Its iOS dependency range accepts the current NosmaiCameraSDK 3.0.5 release. Its public GitHub tag points to the same commit used for the verified pub.dev archive. The iOS 3.0.5 pod downloads the verified framework archive published under GitHub tag v3.0.5.
Official public repositories
React Native 1.0.0 is the current stable public npm release. The Web preview remains available directly from Nosmai.
Verify native downloads
Download the binary and SHA256SUMS from the same GitHub release, then run:
A binary is the ready-to-use SDK file added to the app. A checksum is a digital fingerprint used to confirm that this file is complete and unchanged; SHA-256 is the method used to create that fingerprint.
shasum -a 256 -c SHA256SUMS
The current public assets have these checksums:
c1474da6106926ab1fb152e404a02666456da7bed92c2aefa6e275b356b2f58f nosmai-sdk-3.0.5.aar 2386b45e5a251ea15ad5d576cc370e11f49a19e4e0b8e643b6dc76f3fcccb418 nosmai.framework.zip
Do not integrate a file when verification fails.
Compatibility rules
- Keep exactly one Nosmai native binary per platform target.
- Replace an old AAR instead of keeping both filenames in
app/libs. - Use CocoaPods or manual framework embedding on iOS, not both.
- Keep Android on Java 11, compile SDK 35, API 24 or later, and at least one supported ABI:
arm64-v8aorarmeabi-v7a. - Use a physical arm64 iPhone on iOS 15 or later; the current framework has no Simulator slice.
- Test the exact effect packages and final signed application identity.
Upgrade checklist
- Read the release notes for every changed layer.
- Verify new native artifacts before replacing the previous version.
- Clean the native or Flutter build after binary changes.
- Resolve CocoaPods again and inspect
Podfile.lock. - Test license status, camera lifecycle, effects, Cloud Filters, capture, recording, and streaming on physical devices.
- Compare the signed release size and performance with the previous build.
Common errors
| Symptom | Cause | Fix |
|---|---|---|
| Duplicate classes or native symbols | Two SDK versions are packaged | Keep only one AAR, pod, or framework source |
INSTALL_FAILED_NO_MATCHING_ABIS | The device or build includes neither arm64-v8a nor armeabi-v7a | Test on a supported ARM device and keep at least one supported ABI in the app |
| Simulator linker error | The iOS framework is device-only | Select a physical iPhone or generic device archive target |
| Flutter Android compiles but fails at runtime | The host did not include the proprietary AAR | Add the verified 3.0.5 AAR once in the application module |
