Effects Releases
Effects / Reference / Releases

Nosmai Effects SDK releases and compatibility

Updated October 16, 2026

Choose the current Android, iOS, Flutter, React Native, or Web release and avoid duplicate or mismatched native SDK binaries.

Current releases

ComponentVersionDistribution
Android native SDK3.0.7Public GitHub release AAR
iOS CocoaPod3.0.7NosmaiCameraSDK
iOS framework archivev3.0.7Public GitHub release ZIP used by the 3.0.7 podspec
Flutter package2.0.2nosmai_effects_sdk on pub.dev and GitHub release v2.0.2
React Native2.0.1@nosmai/react-native-effects-sdk on npm and GitHub release v2.0.1
Web0.2.0 developer previewAuthorized 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

  1. Keep exactly one Nosmai native binary per platform target.
  2. Replace an old AAR instead of keeping both filenames in app/libs.
  3. With Flutter 2.0.2, let the plugin resolve Android 3.0.7; remove any manually copied Nosmai AAR and its app-level Gradle dependency.
  4. Use CocoaPods or manual framework embedding on iOS, not both.
  5. Keep Android on Java 11, compile SDK 35, API 24 or later, and at least one supported ABI: arm64-v8a or armeabi-v7a.
  6. Use a physical arm64 iPhone on iOS 15 or later; the current framework has no Simulator slice.
  7. 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

SymptomCauseFix
Duplicate classes or native symbolsTwo SDK versions are packagedKeep only one AAR, pod, or framework source
INSTALL_FAILED_NO_MATCHING_ABISThe device or build includes neither arm64-v8a nor armeabi-v7aTest on a supported ARM device and keep at least one supported ABI in the app
Simulator linker errorThe iOS framework is device-onlySelect a physical iPhone or generic device archive target
Flutter cannot resolve com.nosmai:nosmai-sdk:3.0.7The build machine cannot reach the official release repository and the AAR is not cachedRestore access to GitHub Releases and refresh Gradle dependencies; do not add a duplicate manual AAR

Next steps

References

Nosmai

An AR and AI company. Founded on the idea that the next decade of software will be visual, and that the tools for it should be within reach of anyone building.

Newsletter

Product updates and release notes. No spam.

© 2026 nosmai, inc · all rights reserved