sorisdk_flutter 0.5.1
sorisdk_flutter: ^0.5.1 copied to clipboard
Add SORI-powered audio recognition, campaign discovery, and action-link handling to Flutter apps on Android, iOS, and Web.
0.5.1+6 #
Changed #
- Bundle the published iOS SDK 5.2.1
(release),
a patch release with five server recognition fixes. Public headers and NADA
0.7.0 (
a3aaf73) are unchanged; Android stays at 5.2.0. The provenance manifest records the new artifact and file hashes.
Fixed (iOS) #
startRecognition(repeat: false)withSORIRecognitionMode.servernow ends after the first delivered campaign: the event stream reports therecognitionResult, thenstateChangedSTOPPEDwithout an error. Before, the session kept recognizing untilstopRecognition(). A LIVE-only reply or a recorded match without a campaign does not end it. On-device and on-device-with-periodic-server sessions already behaved this way. Android ignoresrepeatand keeps recognizing (sorisdk-ios #142).- After
updateDatabase()refreshes the token, the next server query in either server mode is sent with the refreshed token instead of the one the session started with. The query in flight keeps its request and is not cancelled (sorisdk-ios #143). - Three further native fixes have no effect reachable through the plugin's API,
because the bridge never calls a standalone
prepare(), its metadata provider only reads the map set bysetMetadata, and anaudiomarkerchange stops and reconfigures the session: a window whose metadata provider stopped recognition is no longer sent (#140); an on-device start after a server-modeprepare()loads the audio packs (#141); a pending server start no longer fails whenaudiomarkeris enabled for the next start (#144).
0.5.0+5 #
Compatibility with 0.4.2 #
An app written against 0.4.2 compiles without changes and gets the 0.4.2
behaviour and results. The default SORIRecognitionConfig is on-device
recognition with no server traffic. SORIRecognitionEventType has exactly the
0.4.2 values in the 0.4.2 order, and the events stream of an on-device app
carries the 0.4.2 events in the 0.4.2 order (channel state has its own stream).
configure() again stores the configuration for the next start synchronously.
The Android foreground notification is the 0.4.2 one unless an app opts in to
visibleChannel; iOS reports native failures of an on-device session as
error, as before. Two additive differences remain: a stateChanged STOPPED
payload carries stopReason: user_notification_action when the user stopped
recognition with the notification's stop action (an extra key in
SORIRecognitionEvent.payload; the 0.4.2 parser gives it no meaning), and a class that implements SorisdkFlutterPlatform instead of extending
it must add pauseRecognition, resumeRecognition and
getRecognitionCapabilities (classes that extend it inherit non-throwing
defaults).
Added #
- Server recognition with one mode selector:
SORIRecognitionConfig.recognitionMode(SORIRecognitionMode.onDeviceby default,server,onDeviceWithPeriodicServer) andserverRecognition(SORIServerRecognitionOptions(intervalMillis: 0, burstMillis: 0, delayMillis: 750)).SORIRecognitionConfig.validate()(also run bytoMap,configureandstartRecognition) throwsArgumentErrorwith the rules of the native SDKs: interval0or3250..maxIntervalMillis(INT64_MAX / 1000000); burst0or3250 <= burst < interval; delay0..60000; no options withonDevice; a positive interval withonDeviceWithPeriodicServer; noaudiomarkerwith either server mode. Web and iOS bridges withoutrecordedServerRecognitionreject both server modes withUnsupportedError. - A recognition mode or server options set with
configure()on a running session are applied by the nextstartRecognition()(or, on Android,resumeRecognition()), in place for a tuning-only change and without restarting capture. Android applies a new mode at that call by restarting its session; iOS uses it at the next start after a stop. Any other configuration change replaces the session, as in 0.4.2. - Channel state of server recognition:
SORIAudioRecognizer.channelStates, a broadcastStream<SORIChannelSnapshot>on its own channel that replays the current state to each new listener, andgetCurrentChannelState(), withSORIChannelSnapshot(includingclearReason),SORIChannelIdentity,SORIChannelProgramandSORIProgramEpisode. Web has none. - Caller metadata for server recognition:
SORIAudioRecognizer.setMetadata()andSORICallerMetadatawith the Console limits and reserved keys (Android and iOS;UnsupportedErroron Web). pauseRecognition({notificationTitle, notificationBody})andresumeRecognition(), completing with aSORIRecognitionControlOutcome, andgetRecognitionCapabilities()withSORIRecognitionCapabilities.supportsPause. Android releases the microphone and reportsstateChangedPAUSED(only after a pause); iOS and Web answerunsupportedand keep recognition running.SORIRecognitionConfig.continueRecognitionOnEngineDetach(Android): keep the native service running when the Flutter engine detaches. iOS and Web reject it.SORIAndroidNotificationOptions.stopAction(SORIAndroidNotificationAction) andvisibleChannel(default false: the 0.4.2IMPORTANCE_MINchannel; true: a silent but visibleIMPORTANCE_LOWchannel).- iOS reports a transient network or server failure of a running server-mode
session as
networkError, as Android does. - The example selects a mode with
--dart-define=SORI_RECOGNITION_MODE.
Changed #
- Bundle the published Android and iOS SDK 5.2.0 artifacts on NADA 0.7.0
(
a3aaf73). The provenance manifest records the native release tags, artifact checksums and vendored file hashes. - The example ignores the Flutter 3.47 deprecation of
package:flutter/material.dart, sincematerial_uineeds Flutter 3.47.
0.4.2+5 #
- SDK security hardening with published Android and iOS SDK 5.1.2.
- Update the shared native core to matcher 0.6.13.
- Increase the Flutter patch version exactly once from 0.4.1+5 to 0.4.2+5.
- Record the published native artifacts and verified vendored file hashes.
0.4.1+5 #
- Adopt the published Android and iOS SDK 5.1.1 artifacts, built from NADA
7ce1c67be631b30d63c47e52faa2bf787f720d82with matcher 0.6.11. - Fix multi-segment file recognition positions when the second query window wins: normalize the query-window offset before selecting the segment and calculating its position. Native matching owns this correction; Dart APIs and event mappings remain unchanged.
- Increase the Flutter patch version exactly once from 0.4.0+5 to 0.4.1+5. Web bridge 0.1.5, Web Audio ^0.6.10, and npm locks remain unchanged.
- Include the iOS 5.1.1 rejected-authentication and cancellation fixes without changing the Flutter bridge API.
- Verify public Maven/CDN archives, tagged sources and all vendored files. See
doc/release-0.4.1.mdandrelease/native-sdk-provenance.jsonfor source, artifact checksums, validation and release boundaries.
0.4.0+5 #
- Adopt verified public Android and iOS 5.1.0 artifacts. Native AudioPack refresh prepares and validates a candidate while recognition uses the working database, then publishes at a safe query boundary without restarting capture.
- Preserve Android's native
UpdateResultand the four-field Dart API. iOS still requests a refresh, but now returnssuccess: falsewith an outcome-unavailable diagnostic instead of unconditional success. This does not mean native failure; do not retry on that value alone. No native completion API exists to map. - Do not add the stale request ID, terminal outcome or replay APIs from #39; they are outside the released native 5.1.0 contract. Add a native example refresh action and document the available semantics.
- Keep Web behavior, bridge 0.1.5, Web Audio ^0.6.10 and npm locks unchanged. Package source is 0.4.0+5; podspec and eventual pub.dev version are 0.4.0.
- See
doc/release-0.4.0.mdfor provenance, validation and physical-device gaps.
0.3.8+4 #
- Adopt verified public Android 5.0.13 and iOS 5.0.12 artifacts with the shared level-robust marker policy as the default when marker recognition is selected. Fingerprint-only defaults, capture/cadence and existing Dart APIs are preserved.
- Release Web bridge 0.1.5 with minimum Web SDK 0.6.10 and a verified dependency lock. Existing Dart app source remains compatible. Update npm dependencies, regenerate the bridge assets, rebuild and deploy to adopt the new runtime.
- Record native/Web release provenance and enforce robust native policy evidence. Verify the real Dart/Chrome bridge, three WASM modules and model.pack with marker opt-in and synthetic low-input/negative PCM regression fixtures.
- Android improvement is user-reported; no new physical acoustic measurements
or full NADA #154 acceptance are claimed. See
doc/release-0.3.8.md.
0.3.7+4 #
- Adopt verified public Android 5.0.12 and iOS 5.0.11 artifacts with continuous material run deduplication. Intervening materials, inactivity and hard capture or session boundaries allow fresh native recognition immediately.
- Preserve distinct activity callbacks within the same campaign and existing marker/refinement and lifecycle mappings. Native hour-long material and five-minute callback suppression no longer hide a new run.
- Record exact native release commits, archive checksums and vendored file hashes
in
release/native-sdk-provenance.json; seedoc/release-0.3.7.md. - Web SDK 0.6.8, companion bridge 0.1.3, ABI 2 and legacy marker defaults are unchanged. This native artifact update does not establish physical acoustic or real Console field acceptance.
0.3.6+4 #
- Preserve recognition lifecycle ownership across Android, iOS and Web: coalesce repeated starts, cancel obsolete startup and permission work, and keep queued events tied to their original session and subscription.
- Handle scoped iOS startup/recovery failures once, retain ownership during recovery, and preserve final recognition results before STOPPED.
- Wait for Web controller creation and entered starts during cleanup, propagate cleanup failures, and retry disposal before replacement.
- Adopt verified public Android 5.0.11 and iOS 5.0.10 artifacts. Web SDK 0.6.8,
companion bridge 0.1.3, ABI 2 and legacy marker defaults remain unchanged.
See
doc/release-0.3.6.mdfor provenance and validation boundaries.
0.3.5+4 #
- Bridge SDK-owned current marker state, explicit clear events and native snapshots on Android/iOS without a Dart expiry timer or network lifecycle.
- Add typed accepted activity results with exact activity identity and Console-resolved marker metadata. Preserve legacy discovery semantics.
- Provide a presentation reducer for ordered state and historical result updates; simplify the example to render those SDK values.
- Adopt the published Android 5.0.10 and iOS 5.0.9 artifacts from merged native
PRs #63 and #107. Verify versioned public archives and every vendored file;
preserve legacy detector defaults. See
doc/release-0.3.5.mdfor provenance and the separate physical acoustic/real Console validation limits. - Preserve Web 0.6.8 discovery/refinement compatibility. Current-state and state-driven native enrichment parity are not claimed for Web.
- Physical acoustic and real Console field acceptance remain pending.
0.3.4+4 #
- Bundle published Android SDK 5.0.9 and iOS SDK 5.0.8 with the merged shared marker implementation, preserving legacy marker defaults. The new policy remains an explicit native SDK build-time option.
- Verify public native archive provenance and complete vendored file hashes before publication.
- Keep the Web bridge and its published Web SDK dependency unchanged.
0.3.3+3 #
- Add nonblank
SORIAudioMarkerIdentityvalues and emit structuredaudioMarkerFoundevents only after Android, iOS, or Web activity resolution. - Stop mapping local codebook,
trait.marker, and detector payloads across platform events; retain deprecated legacy String APIs without a private-code fallback. - Preserve ordered campaign segments while keeping marker-first, refinement, and campaign-less marker delivery independently observable.
- Adopt the published Android SDK 5.0.8 Maven artifact and iOS SDK 5.0.7 XCFramework release archive, replacing the locally built candidates.
- Prepare
@sorisdk/flutter-web-bridge0.1.3 with an exact registry pin and integrity lock for the published@sorisdk/web-audio0.6.8 contract, and increment the bridge ABI so stale String-marker bundles fail explicitly.
0.3.2+2 #
- Reconcile campaign callbacks only inside the current ordered material segment, with sticky marker evidence, stale exact-id suppression after an intervening material, and a current-segment-only legacy fallback.
- Preserve Android, iOS, and Web activity/material identities through their bridge payloads and cover all three event styles with shared sequence tests.
- Adopt published Android SDK 5.0.7 and iOS SDK 5.0.6 artifacts, whose native activity lifecycles keep first-observation recognition metadata immutable while renewing continuity with a separate observation timestamp.
- Prepare
@sorisdk/flutter-web-bridge0.1.2 with the published exact@sorisdk/web-audio0.6.7 pin.
0.3.1+1 #
- Normalize optional
activityId/activity_idevent identity without breaking older payloads, and refine example campaign rows by that identity. - Prepare
@sorisdk/flutter-web-bridge0.1.1 with an exact@sorisdk/web-audio0.6.5 pin for the released Web refinement transport. - Refresh the bundled iOS XCFramework to SORI SDK 5.0.4 so activity refinement
responses retain
activity_idand resolved audio-marker metadata. - Refresh the bundled Android payload to SORI SDK 5.0.5 and map its additive campaign activity id into the Flutter event stream.
0.3.0+8 #
- Add Flutter Web registration and a
dart:js_interopadapter for@sorisdk/web-audio. - Add
SORIAudioRecognizer.weband server-backed ephemeral authentication so browser builds never need the long-lived SORI secret. - Add the independently versioned
@sorisdk/flutter-web-bridgecompanion source and build command without embedding npm JS/WASM/model artifacts in the pub.dev package. - Map Web ready, lifecycle, match, audiomarker, campaign, and error events to the existing Dart event stream.
0.2.6+7 #
- Replace the bundled Android and iOS artifacts with clean release builds from
the final stable SORI SDK
5.0.3commits. - Correct the embedded iOS framework version from the earlier prerelease label
to stable
5.0.3while preserving the NADA0.6.3AudioPack hardening.
0.2.5+6 #
- Refresh bundled Android and iOS SDK artifacts for NADA 0.6.3 AudioPack load budgets, transactional pack application, and serialized database updates.
- Preserve the Flutter API and event payloads while the native SDK bridges reject invalid zero-sized configurations and keep the active recognition database intact after a failed pack load.
0.2.3+4 #
- Refresh bundled Android and iOS SDK artifacts for Nada matcher
leading-gap normalization with source-time
matcherSegments, including the final Nada v0.6.2 matcher follow-up that excludes trailing partial hops from the inferred warmup gap. - Keep the multi-segment AudioPack contract unchanged while relying on the native matcher to infer the stored AFP warmup gap internally.
0.2.2+3 #
- Refresh bundled Android and iOS SDK artifacts for segment-aware Nada matcher results.
- Preserve segment-local match duration from native SDK recognition results so bundled materials do not appear as one long exposure.
0.2.1+2 #
- Publish Android consumer R8 rules for the native-bound
afplibJNI surface and the SDK Parcelize annotation warning, so minified Flutter host apps do not need temporary app-level SORI workarounds.
0.2.0+1 #
- Refresh native Android and iOS SDK artifacts for near-ultrasonic audiomarker recognition.
- Add
SORIRecognitionConfig.audiomarkerand expose marker results through recognition events and campaign traits. - Emit iOS audiomarker-only state changes as
audioMarkerChangedevents.
0.1.0 #
- Initial Flutter plugin release for adding SORI audio recognition, campaign results, and action-link handling to Android and iOS apps.