Get and apply a Nosmai Effects license key

Prerequisites

• A Nosmai Console account
• The final Android application ID, iOS bundle identifier, or Web origin
• A valid payment card for project creation
• The installed Nosmai Effects package for the target platform

An app-bound licence key is a project credential created for one specific application identity. Android calls that identity the application ID, iOS calls it the bundle identifier, and Web uses the site's origin.

Create a project

1. Start project creation

Sign in to Nosmai Console, open Projects, and select Create project.

2. Choose Nosmai Effects

Select Nosmai Effects, then select Next. A Console project is created for one Nosmai product.

3. Choose the project plan

Enter a recognizable project name. Select the expected monthly active users and billing cycle. A promo code is optional. Review the current plan, included features, and price shown in Console, then select Continue to payment.

Plan availability, pricing, trials, and included features can change. The values and terms displayed in Nosmai Console during checkout are the current source of truth.

4. Add a payment card

A valid payment card is required to create the project and start an available trial, even when Console shows no payment due on that day. Review the trial period, first payment date, renewal price, and cancellation terms before confirming.

Create an app-bound key

Open the new project and select Create new key. Choose the platform, then enter the exact identity of the application that will use the key:

• iOS: Use the target's Bundle Identifier from Xcode Signing & Capabilities. See Apple's official bundle ID guidance.
• Android: Use the app module's applicationId. See Android's official application ID guidance.
• Web: Use the licensed website origin, including the scheme and any port required by the project.

Do not copy the example identifier shown in the screenshot. Select Generate key only after the platform and application identity are correct.

Copy the generated key immediately and store it in private build configuration. For security, Console does not show the complete key again.

Do not paste a real key into a public repository, issue, screenshot, analytics event, or support message.

Match the application identity

Android and iOS normally use separate keys even when they share one Flutter or React Native codebase.

Initialize once

Initialize at the application or camera-session boundary. Do not initialize in a widget build, render function, list item, or frame callback.

Use the platform quickstart for the exact released method:

• iOS quickstart
• Android quickstart
• Flutter quickstart
• React Native quickstart
• Web quickstart

An accepted initialization starts the native session. Final online verification can complete asynchronously, so observe the license-status callback where the platform exposes it.

Understand each state

The current native enforcement keeps the host application alive. It does not intentionally crash the process after a delay.

The Web preview remains watermarked until verification succeeds, but its current visual enforcement is not identical to native invalid-key blur.

Native 3.0.4 also renders a short enforcement message inside the processed output. LICENSE_EXPIRED shows Nosmai Effects license has expired. Please contact your administrator. MAU_LIMIT_EXCEEDED is treated as an invalid state and shows Monthly usage limit reached. Please contact your administrator. Other confirmed invalid states show Nosmai Effects unavailable. Please contact your administrator. Keep any additional product UI outside the camera preview concise and consistent with the SDK state.

Diagnose a rejection

DNS failures, timeouts, and other transport errors are temporary UNVERIFIED conditions, not proof that a key is invalid.

Plan for offline use

The first successful verification requires the Nosmai licensing service. A signed cached state can support a limited offline period where current account policy allows it. Retry when connectivity returns; never run a tight loop or reuse one key's cached validity for another key.

Keep environments separate

Use different Console projects and identities for development, staging, and production. Inject the selected key through build or runtime configuration and redact it from release logs.

Verify it worked

1. Start with an active network connection.
2. Confirm initialization is accepted.
3. Confirm the final status becomes VALID.
4. Open the camera and confirm there is no enforcement watermark or blur.
5. Repeat with the final signed application identity.
6. Confirm logs and analytics do not contain the complete key.

Common errors

Next steps

• Install Nosmai Effects
• Open the platform quickstart
• Review licensing and MAU
• Troubleshoot initialization

References

• Nosmai Console
• Nosmai Effects pricing
• Platform support
• Troubleshooting