Current releases
| Component | Version | Distribution |
|---|---|---|
| Android native SDK | 3.0.7 | Public GitHub release AAR |
| iOS CocoaPod | 3.0.7 | NosmaiCameraSDK |
| iOS framework archive | v3.0.7 | Public GitHub release ZIP used by the 3.0.7 podspec |
| Flutter package | 2.0.2 | nosmai_effects_sdk on pub.dev and GitHub release v2.0.2 |
| React Native | 2.0.1 | @nosmai/react-native-effects-sdk on npm and GitHub release v2.0.1 |
| Web | 0.2.0 developer preview | Authorized preview package |
Flutter 2.0.2 is the current public package and is compatible with Android Effects SDK 3.0.7. It resolves the Android AAR from the official GitHub release and declares NosmaiCameraSDK 3.0.7 for iOS. Flutter applications do not download or link a second AAR manually. React Native 2.0.1 uses the same native baseline; its Android host owns one verified AAR, while its iOS pod resolves NosmaiCameraSDK 3.0.7. The iOS pod downloads the verified framework archive published under GitHub tag v3.0.7.
Official public repositories
React Native 2.0.1 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:
8e72c0b7a95fd477c3256d67f1c6721fecd3d3cde43d1ca9078eee895425faa8 nosmai-sdk-3.0.7.aar a6355f72886391caccbf05141f49d38edd82aeec436434e1f206d329f56b13a4 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. - With Flutter
2.0.2, let the plugin resolve Android3.0.7; remove any manually copied Nosmai AAR and its app-level Gradle dependency. - 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 cannot resolve com.nosmai:nosmai-sdk:3.0.7 | The build machine cannot reach the official release repository and the AAR is not cached | Restore access to GitHub Releases and refresh Gradle dependencies; do not add a duplicate manual AAR |