aws-amplify/amplify-flutter
30.6
Weak · 17 November 2026
180.3k
lines of production code
Dart
with Swift
5
measurements over time
What this system is
Features
Add AFT CLI entry point
The \packages/aft/bin/aft.dart\ file has been added as the executable entry point for the AFT CLI tool. It initializes the command runner and handles standard error reporting for usage exceptions and other errors, ensuring the process exits with the correct status code.
packages/aft/bin · high confidence
Add Android native wrapper for legacy Amplify authentication
This change introduces the Android-side implementation for the \amplify\_native\_legacy\_wrapper\ package, providing a bridge between Flutter and the legacy Amplify Android SDK. The new \AmplifyNativeLegacyWrapperPlugin\ registers with Flutter via Pigeon and exposes methods to configure the Amplify instance, perform sign-in and sign-out operations, and remember the device using the \AWSCognitoAuthPlugin\. This enables Flutter applications to interact with legacy Amplify authentication flows on Android through a standardized native interface.
_packages/amplify\_native\_legacy\wrapper/android · high confidence
Add Cognito configuration models for Gen 2 outputs
This change introduces a new set of serializable configuration classes in the \amplify\_core\ package to support Amplify Gen 2 outputs. The diff adds data models for Cognito User Pools (\CognitoUserPoolConfig\), OAuth Hosted UI settings (\CognitoOAuthConfig\), and AppSync API configurations (\CognitoAppSyncConfig\), along with supporting types for credentials providers, MFA settings, password policies, and social providers. These classes include JSON serialization logic and factory methods (e.g., \fromAuthOutputs\) to parse and manage Cognito-specific configuration data required by the updated authentication and API categories.
_packages/amplify\core/lib/src/config/auth/cognito · high confidence
Add Gen 2 infrastructure for analytics and user management extensions
This change introduces new infrastructure components in the \infra-gen2/infra-common\ library to support Gen 2 backend capabilities. For analytics, it provisions an Amazon Pinpoint app, a Kinesis Data Stream, and an AppSync GraphQL API to capture and store events. For user management, it adds a dedicated AppSync API and associated Lambda functions to enable programmatic user creation, deletion, and SMS MFA configuration via Cognito triggers. It also implements custom email and SMS senders that decrypt verification codes and broadcast them to the user management API, along with a pre-sign-up trigger to auto-verify accounts.
infra-gen2/infra-common · high confidence
Add Gen 2 storage backend configurations for single and multi-bucket scenarios
The storage backend infrastructure now includes Gen 2 Amplify backend definitions for both single-bucket and multi-bucket test scenarios. The 'main' configuration introduces support for multiple S3 buckets (a default and a secondary bucket), enabling users to deploy and manage storage across distinct buckets within the same application. The 'dots-in-name' configuration provides a single-bucket setup with a bucket name containing dots, ensuring compatibility with non-standard naming conventions. Both configurations include pre-sign-up authentication triggers and custom CORS settings to support cross-origin requests.
infra-gen2/backends/storage · high confidence
Add Gen 2 storage configuration models for S3
New configuration classes (S3PluginConfig, StorageConfig) and their JSON serialization logic have been added to the core package to support Amplify Gen 2 outputs. These files define how S3 storage settings (bucket and region) are parsed from configuration JSON and provide a conversion method to the internal StorageOutputs model, enabling the application to read and utilize Gen 2 storage configurations.
_packages/amplify\core/lib/src/config/storage · high confidence
Add ISO-8601 temporal scalar types for AppSync compatibility
New classes have been added to the core library to handle temporal data in formats compatible with AWS AppSync scalars. This includes TemporalDate, TemporalTime, TemporalDateTime, and TemporalTimestamp, which provide strict parsing and formatting of ISO-8601 strings (including timezone offsets and nanosecond precision) and conversion to/from Dart DateTime objects. A helper class, Temporal, provides utility methods for duration and offset conversions, while a DateTime extension simplifies basic ISO-8601 string serialization.
_packages/amplify\core/lib/src/types/temporal · high confidence
Add Kinesis and Firehose backend templates with Amplify auth integration
New backend templates for Kinesis Data Streams and Kinesis Data Firehose have been added to the infrastructure library. These templates use the AWS Amplify backend framework to provision the respective streaming services and configure an Amazon S3 bucket as the delivery destination for Firehose. Both templates integrate with Amplify Auth, setting up a pre-sign-up trigger and granting authenticated users IAM permissions to write records to the streams.
infra-gen2/backends/kinesis · high confidence
Add Swift Package Manager support for the Darwin native legacy wrapper
The Darwin platform implementation of the amplify\_native\_legacy\_wrapper now includes Swift Package Manager support. This change introduces the necessary Swift source files (AmplifyNativeLegacyPlugin.swift and AmplifyNativeLegacyWrapperPlugin.swift) and a .gitignore configuration to facilitate integration via SPM, enabling Flutter apps on iOS and macOS to consume the legacy wrapper through the Swift Package Manager ecosystem.
_packages/amplify\_native\_legacy\wrapper/darwin · high confidence
Add WebAssembly support to Analytics Pinpoint app info provider
The app info provider in the Analytics Pinpoint package now supports WebAssembly targets. This is achieved by splitting the implementation into platform-specific files: the HTML target uses \package\_info\_plus\'s platform interface to avoid pulling in \dart:io\, while the IO target uses the standard \package\_info\_plus\ entrypoint. This change ensures that analytics data collection works correctly in WebAssembly environments without build errors caused by unsupported IO dependencies.
_packages/analytics/amplify\_analytics\_pinpoint/lib/src/device\_context\_info\_provider/app\_info\provider · high confidence
Add configuration models for AWS Pinpoint Push Notifications
New configuration classes have been added to the Notifications category to support AWS Pinpoint push notifications. Users can now access structured configuration data via \NotificationsConfig\ and \NotificationsPinpointPluginConfig\, which expose the Pinpoint app ID and region. These models include JSON serialization support and provide a \toNotificationsOutputs\ method to convert the configuration into the standard outputs format, enabling better integration with Gen 2 outputs.
_packages/amplify\core/lib/src/config/notifications · high confidence
Add core utility helpers for serialization, UUIDs, and enums
New utility files have been added to the core library to support internal serialization and data handling. This includes a centralized UUID generator for creating unique identifiers, helper functions for converting enums to and from strings, and a set of global JSON serialization configurations (including a custom map type) that standardize how Amplify models are serialized to and from JSON.
_packages/amplify\core/lib/src/util · high confidence
Add device information provider for Pinpoint analytics
The Pinpoint analytics plugin now includes a new device context info provider that collects and exposes device metadata (manufacturer, model, platform, and OS version) to AWS Pinpoint endpoints. This change introduces platform-specific implementations for web, mobile (Android/iOS), and desktop (Linux/macOS/Windows) targets using the \device\_info\_plus\ package, ensuring that analytics data accurately reflects the user's environment.
_packages/analytics/amplify\_analytics\_pinpoint/lib/src/device\_context\_info\_provider/device\_info\provider · high confidence
Add iOS canary runner project scaffolding
The iOS canary location now includes the complete Xcode project and Flutter runner scaffolding (including the project file, workspace, app delegate, storyboards, assets, and Info.plist with the app name 'Amplified Todo'). This establishes the buildable iOS application structure required for the canary tests, complementing the CI migration to GitHub Actions.
canaries/ios · high confidence
Add iOS example app scaffolding for Amplify Datastore
The iOS example application for the Amplify Datastore package has been scaffolded, providing the necessary native iOS project files to run the example on iOS devices. This includes the AppDelegate implementing Flutter's implicit engine delegate, standard launch screens and app icons, and the Info.plist configured with modern iOS settings such as scene management and indirect input event support.
_packages/amplify\datastore/example/ios/Runner · high confidence
Add legacy Pinpoint endpoint ID retrieval for iOS and Android
The Pinpoint analytics plugin now includes a mechanism to retrieve the legacy endpoint ID stored by the native iOS and Android SDKs. On Android, this is implemented via a Pigeon-generated bridge to the native layer, while on iOS it reads the ID from secure storage using a specific keychain namespace. A platform-aware factory class selects the appropriate provider, enabling the Flutter analytics module to access this legacy identifier.
_packages/analytics/amplify\_analytics\_pinpoint/lib/src/legacy\_native\_data\provider · high confidence
Add macOS example app scaffolding
The macOS example application for amplify\_flutter is now included in the repository, providing a complete Xcode project structure. This enables developers to build, run, and debug the example app directly on macOS, with native plugin registration configured for amplify\_auth\_cognito, amplify\_secure\_storage, connectivity\_plus, device\_info\_plus, package\_info\_plus, and path\_provider\_foundation.
_packages/amplify\_native\_legacy\wrapper/example/android · high confidence
Add multi-auth backend with custom REST API and granular data permissions
The \api-multi-auth\ backend now includes a custom REST API (\multiAuthRest\) integrated with a Lambda function, allowing access via IAM policies for both authenticated and unauthenticated users. The data layer defines a schema with models like Blog, Post, and Comment, enforcing granular authorization rules that support public API keys, guest access, identity pool authentication, user pool authentication, and owner-based permissions.
infra-gen2/backends/api · high confidence
Add paginated list query support for GraphQL
The core library now includes \PaginatedResult\ and \PaginatedModelType\ classes to handle paginated list queries. Users can decode GraphQL list responses into typed, paginated results that include items, a next token, and a request object for fetching subsequent pages, simplifying the implementation of infinite scroll or pagination UI patterns.
_packages/amplify\core/lib/src/types/api/types/pagination · high confidence
Add support for running pub commands via the CLI
Users can now execute Dart or Flutter pub commands (such as get, upgrade, or bootstrap) directly through the Amplify CLI. This change introduces a new \pubAction\ extension and a \runPub\ helper in the \pub\_runner.dart\ file, which spawns the appropriate \pub\ process for the target package flavor. The implementation respects the \--fail-fast\ option to control error handling behavior and supports verbose logging.
packages/aft/lib/src/pub · high confidence
Added Linux and Windows native runners for the Pinpoint analytics example app
The example application for the Pinpoint analytics package now includes full native support for Linux and Windows desktop platforms. This change introduces the necessary CMake build configurations, application entry points, and window management code for both platforms, enabling developers to build and run the analytics example as a native desktop application on Linux (GTK) and Windows (Win32).
_packages/analytics/amplify\_analytics\pinpoint/example/windows · high confidence
Added PushNotificationException class
A new \PushNotificationException\ class has been introduced to serve as the base class for push notification errors. This allows users to catch and handle specific failures related to push notification services separately from other Amplify exceptions.
_packages/amplify\core/lib/src/types/exception/push · high confidence
Added Windows and Linux native runner support for the example app
The example application now includes native project scaffolding for Windows and Linux, enabling users to build and run the app on these desktop platforms. This adds the necessary CMake build configurations, native entry points, and window management code for both platforms, along with generated plugin registrants that register the \amplify\_db\_common\ and \connectivity\_plus\ plugins on Windows.
_packages/amplify/amplify\flutter/example/windows · high confidence
Added iOS Flutter framework configuration files for the DataStore example app
The iOS example project for Amplify DataStore now includes the standard Flutter framework configuration files: AppFrameworkInfo.plist, Debug.xcconfig, and Release.xcconfig. These files establish the necessary bundle identifiers, build configurations, and CocoaPods integration settings required to run the example app on iOS.
_packages/amplify\datastore/example/ios/Flutter · high confidence
Added iOS Xcode scheme for DataStore example app
The iOS example application for Amplify DataStore now includes a defined Xcode scheme (Runner.xcscheme). This configuration enables the project to be built, run, tested, profiled, and archived directly within Xcode, specifically configuring the test action to execute the \unit\_tests.xctest\ target alongside the main app.
_packages/amplify\datastore/example/ios/Runner.xcodeproj/xcshareddata · high confidence
Added macOS example app scaffolding for Amplify Analytics Pinpoint
The macOS example application for the \amplify\_analytics\_pinpoint\ package is now available, providing a complete native project structure. This includes the Xcode project configuration, build settings, and a \GeneratedPluginRegistrant.swift\ that registers dependencies such as \amplify\_auth\_cognito\, \amplify\_secure\_storage\, \connectivity\_plus\, \device\_info\_plus\, and \package\_info\_plus\. Users can now run and test the analytics example on macOS.
_packages/amplify/amplify\_flutter/example/macos, packages/analytics/amplify\_analytics\pinpoint/example/macos · high confidence
Added template scaffolding for Dart and Flutter example apps
The \aft create\ command now generates initial project structures for both Dart and Flutter packages. For Dart, it adds a basic library file and an Amplify configuration stub. For Flutter, it provides a complete Android example app scaffold, including the main activity, AndroidManifest files for debug/profile/main builds, and standard launch theme resources, allowing users to immediately run and debug their new package examples.
(repo-wide) · high confidence
Added tooling for provisioning DataStore integration test backend resources
New scripts and configuration files have been added to the example tool directory to automate the setup of the AWS backend required for DataStore integration tests. This includes a shell script to initialize the Amplify project with Flutter frontend settings, a GraphQL schema defining models for testing relationships and custom types, and a Lambda trigger script to auto-verify user sign-ups during testing.
_packages/amplify\datastore/example/tool · high confidence
Canaries project scaffolded with Flutter and Amplify Gen 2 configuration
The canaries directory now contains a new Flutter application scaffold (\amplified\_todo\) configured to support Amplify Gen 2 outputs. This includes a \.gitignore\ file that explicitly excludes Amplify Gen 2 specific files such as \amplify\_outputs.dart\, \amplifyconfiguration.dart\, and \amplify\_outputs.json\, alongside standard Flutter build artifacts. The project also includes an \.eslintignore\ to exclude generated code models and an \analysis\_options.yaml\ that applies \amplify\_lints\ for code analysis.
canaries · high confidence
Initial Android scaffolding for the DataStore example app
The Android portion of the amplify\_datastore example application has been scaffolded, providing the necessary structure to run the Flutter app on Android devices. This includes the main AndroidManifest.xml with Flutter v2 embedding configuration, a Kotlin MainActivity extending FlutterActivity, standard launch splash screens for light and dark modes, and debug/profile manifest permissions for internet access. Additionally, a basic Android instrumented test (MainActivityTest) is included to support integration testing.
_packages/amplify\datastore/example/android/app · high confidence
Initial Dart analytics plugin implementation
The Dart analytics plugin package is introduced, providing the core entry point for Amplify Analytics Pinpoint on Dart platforms. This change adds the main library file which exports the analytics plugin implementation, plugin options, and the AWS Pinpoint user profile endpoint client, establishing the foundational structure for analytics functionality in Dart applications.
_packages/analytics/amplify\_analytics\_pinpoint\dart/lib · high confidence
Initial package scaffolding and configuration for amplify\_core
The amplify\_core package is introduced as the foundational library for amplify-flutter, providing base types and utilities shared across the framework. This release establishes the package's structure with a comprehensive changelog documenting support for features like Wasm, multi-bucket storage, and passwordless login, alongside a platform support matrix indicating full compatibility across Android, iOS, Web, Windows, and MacOS (with DataStore and Notifications limited to mobile and web). The package is configured with standard Flutter/Dart tooling, including .gitignore and .pubignore files to manage build artifacts, analysis options for linting, build configurations for web compilation, and dartdoc settings to organize API documentation by category.
_packages/amplify/amplify\_flutter, packages/amplify\core · high confidence
Initial release of amplify\_core package
The amplify\_core package is introduced as a new foundational component for the amplify-flutter library, providing base types and utilities shared across all categories. This release includes the core library source code, a comprehensive changelog documenting history from version 0.0.1-dev.2 through 2.15.1, and a platform support matrix confirming availability on Android, iOS, Web, Windows, macOS, and Linux (with DataStore and Notifications limited to mobile and web). The package is configured with standard Flutter/Dart tooling, including analysis options, build configurations for web compilers, and test overrides.
_packages/amplify\_native\_legacy\wrapper · high confidence
Initial release of amplify\_datastore\_plugin\_interface package
This change introduces the \amplify\_datastore\_plugin\_interface\ package, which provides the platform interface for the DataStore module of Amplify Flutter. The commit adds the foundational package structure, including the Apache 2.0 license, a changelog documenting versions from 1.0.0-next.0 through 2.16.0, a README, analysis options, and Flutter-specific metadata and gitignore files.
_packages/amplify\_datastore\_plugin\interface · high confidence
Initial release of the AWS Signature V4 signing library
Introduces the \aws\_signature\_v4\ package, providing an HTTP request signer for AWS Signature Version 4. This library enables Dart, Flutter, and Web applications to sign requests for AWS services, supporting features such as configurable service settings (e.g., S3 chunked encoding), credential scoping, and pre-signed URL generation. The release includes a comprehensive example demonstrating S3 bucket creation and file uploads, along with Web-specific implementations using \dart:js\_interop\ for browser-based file handling.
_packages/aws\_signature\v4 · high confidence
Initial release of the Dart Analytics Pinpoint plugin
This change introduces the initial implementation of the AWS Pinpoint Analytics plugin for Dart/Flutter. It provides the core plugin infrastructure, including configuration via \AmplifyAnalyticsPinpointDart\, support for plugin options such as \autoFlushEventsInterval\ (defaulting to 30 seconds), and the underlying client logic for managing sessions, events, and endpoint updates. The package is released at version 0.4.21.
_packages/analytics/amplify\_analytics\_pinpoint\dart/lib/src · high confidence
Initial release of the amplify\_authenticator package
The \amplify\_authenticator\ package is now available, providing a fully customizable authentication flow for Flutter applications. It simplifies user authentication and session management by allowing developers to wrap their app's authenticated routes in an \Authenticator\ widget. The package includes prebuilt widgets for forms and buttons that automatically integrate with the authenticator's state, and it supports platform-specific autofill hints for a better user experience on iOS, Android, and Web.
packages/authenticator · high confidence
Initial scaffolding of the DataStore example app
The \amplify\_datastore/example\ directory has been initialized with a new Flutter application that demonstrates the DataStore plugin. The entry includes a \.gitignore\ file configured to exclude generated Amplify configuration files (such as \amplifyconfiguration.dart\ and \aws-exports.js\) and build artifacts, a \.metadata\ file tracking the Flutter project version, and a \README.md\ that outlines how to run the app in local mode or configure it for cloud sync using a Blog/Post/Comment schema.
_packages/amplify\datastore/example · high confidence
Initial scaffolding of the amplify\_datastore package
The amplify\_datastore package has been added to the repository, providing the foundational structure for the Flutter DataStore category. This initial commit includes the package's changelog, license, and a README that documents platform support (noting that DataStore is currently supported on Android and iOS but not on Web, Windows, macOS, or Linux). It also sets up the example iOS workspace configuration and a Makefile for generating native plugin bindings, establishing the baseline for the library's integration with the native Amplify SDKs.
_packages/amplify\datastore · high confidence
Introduce Amplify Connect client for Amazon Connect Customer Profiles
Added the \amplify\_connect\_client\ Flutter package, enabling developers to identify users and manage device push tokens against the Amazon Connect Customer Profiles endpoint. The client exposes \identifyUser\, \registerDevice\, and \removeDevice\ methods, reading its configuration from the \notifications.amazon\_connect\ section of \amplify\_outputs.json\. This release also includes a macOS example app for manual testing and integration tests to verify authenticated and guest user flows.
_packages/amplify\_connect\client · high confidence
Introduce Auth Hub events for sign-in, sign-out, session expiry, and user deletion
The Auth category now exposes structured hub events that allow applications to react to key authentication lifecycle changes. A new \AuthHubEvent\ class and \AuthHubEventType\ enum define four specific event types: \signedIn\ (emitted when a user successfully signs in or is already signed in at app start), \signedOut\ (emitted on explicit sign-out or implicit sign-out via user deletion), \sessionExpired\ (emitted when Cognito tokens or AWS credentials expire and cannot be refreshed), and \userDeleted\ (emitted when a user is deleted). These events carry the relevant \AuthUser\ payload where applicable, enabling developers to listen for and handle these state transitions within the Amplify hub system.
_packages/amplify\core/lib/src/types/auth/hub · high confidence
Introduce Dart analytics client and session management for Pinpoint
Added the core implementation files for the Dart Pinpoint analytics plugin, including the \AnalyticsClient\ which initializes and exposes the \EventClient\ and \EndpointClient\ for interacting with AWS Pinpoint, and the \SessionManager\ which tracks app lifecycle events (foreground/background) to automatically manage user sessions and their associated metadata.
_packages/analytics/amplify\_analytics\_pinpoint\_dart/lib/src/impl/analytics\client · high confidence
Introduce Dart analytics event client with local caching and retry logic
The Pinpoint analytics plugin for Dart now includes a new \EventClient\ that manages analytics events by caching them locally (via \EventStorageAdapter\ and \QueuedItemStore\) before flushing them to AWS Pinpoint. This change introduces robust event handling: events are persisted to device storage to survive app restarts, and the client implements retry logic for recoverable failures (such as \PayloadTooLargeException\ or non-202 status codes) without discarding events from the cache on authentication exceptions. It also supports registering global custom properties (attributes and metrics) that are automatically attached to all new events, with validation for event type length and size limits.
_packages/analytics/amplify\_analytics\_pinpoint\_dart/lib/src/impl/analytics\_client/event\client · high confidence
Introduce Dart-based GitHub Actions interop library
This change adds a new Dart library in actions/lib that provides a JavaScript interop layer for GitHub Actions Node.js modules. It exposes Dart wrappers for core action utilities (inputs, outputs, logging, state), execution, HTTP requests, tool caching, and the GitHub context. It also includes an Android tooling layer (SDK manager, AVD manager) for emulator setup and a ChromeDriver download resolver, enabling CI workflows to run these operations directly in Dart instead of relying on separate Node.js scripts.
actions/lib · high confidence
Introduce Hub event system for real-time notifications
The Amplify Core package now includes a Hub mechanism that allows applications to subscribe to real-time events from various categories. Users can listen to events from Auth, DataStore, and API channels using the new \AmplifyHub\ interface, which manages stream subscriptions and provides a centralized way to react to state changes or actions within the Amplify ecosystem.
_packages/amplify\core/lib/src/hub · high confidence
Introduce Swift Package Manager support and iOS 27 compatibility for DataStore
The DataStore plugin for Darwin platforms now supports installation via Swift Package Manager, accompanied by updated build configurations to target iOS 27. This change introduces the core Swift implementation for the DataStore plugin, including the \AWSDataStorePlugin\ class, configuration structures, and internal behaviors for saving, querying, and subscribing to model changes. It also adds support for lazy-loading model associations through new decoder and provider classes, and implements database migrations to handle schema updates for sync metadata.
_packages/amplify\datastore/darwin · high confidence
Introduce \`aft\` CLI for repository management
The \aft\ tool is now available as a dedicated command-line interface for managing the Amplify Flutter repository. It provides a suite of commands for package lifecycle and code generation, including \aft run\, \aft constraints\, \aft version-bump\, \aft publish\, \aft exec\, \aft create\, \aft clean\, and \aft review\. The tool handles dependency graph resolution, topological sorting for publishing, and Git-based change detection to automate versioning and release notes.
packages/aft/lib/src · high confidence
Introduce amplify\_db\_common Flutter plugin and example app
This change adds the \amplify\_db\_common\ package, a new Flutter plugin providing common utilities for database operations such as SQLite via the Drift library. The diff introduces the full plugin structure, including the Android plugin implementation (\AmplifyDbCommonPlugin.kt\), platform-specific configurations, and a comprehensive example application (\amplify\_db\_common\_example\) that demonstrates usage with integration tests. The package includes a changelog tracking versions from 0.1.2+8 up to 0.4.21, reflecting support for features like WASM, iOS 27, and various SDK and dependency updates.
packages/common · high confidence
Introduce amplify\_foundation\_dart package with logging, credentials, and result types
The new \amplify\_foundation\_dart\ package provides common types and utilities for Amplify packages, including a centralized logging system (\AmplifyLogging\) with configurable sinks, AWS credential models (\StaticCredentials\, \TemporaryCredentials\), and a \Result\ type for handling success/failure states. It also includes platform detection constants (\zIsWeb\, \zIsWasm\, etc.) for compile-time tree-shaking and supports both \dart2js\ and \dart2wasm\ compilation targets.
_packages/amplify\foundation · high confidence
Introduce aws\_common package with AWS configuration and HTTP foundations
The new \aws\_common\ package provides the shared types and utilities used across AWS and Amplify packages. It introduces a configuration system (\AWSConfigValue\) that reads settings like region and max attempts from environment variables, zone overrides, and defaults, alongside an \AWSPathProvider\ to resolve local file paths for AWS config and credentials files. The package also includes an \AWSService\ enumeration for SigV4 signing, an \AWSProfileFile\ model for parsing AWS configuration profiles, and a foundational HTTP client layer (\AWSBaseHttpClient\, \AWSHttpRequest\, \AWSHttpResponse\) with logging and cancellation support.
_packages/aws\common · high confidence
Introduce core Datastore model types and sorted list implementation
This change adds the foundational data structures for the Datastore API, including \QuerySnapshot\ for holding sorted, filtered model results with sync status, \SortedList\ for efficient ordered item management, \ObserveQueryThrottleOptions\ to control event emission frequency during sync, \SubscriptionEvent\ to represent backend mutations, and \AuthModeStrategy\ to define authorization handling. These types provide the underlying mechanics for observing and managing local data state in sync with the cloud.
_packages/amplify\core/lib/src/types/datastore/models · high confidence
Introduce example\_common package with web UI components
The new \example\_common\ package provides a shared library of lightweight, web-based UI components (such as Button, Text, Form, and Flex layouts) and utilities for building example applications. It includes a minimal component framework with lifecycle hooks, a \renderApp\ utility for mounting components to the DOM, and a web example demonstrating these components in action.
_packages/example\common · high confidence
Introduce internal DataStore plugin interface package
A new internal interface package, \amplify\_datastore\_plugin\_interface\, has been added to expose the core DataStore types (including model definitions, temporal types, sync expressions, subscription events, and conflict-handling primitives) used by the \amplify\_datastore\ plugin. This package serves as a platform interface layer, allowing application code to depend on the main \amplify\_datastore\ package while keeping the underlying type definitions centralized and consistent across platforms.
_packages/amplify\_datastore\_plugin\interface/lib · high confidence
Introduce native legacy wrapper for authentication operations
Added a new \AmplifyNativeLegacyWrapper\ component that bridges Flutter to native authentication capabilities (configure, sign-in, sign-out, and remember-device) using Pigeon for platform channel communication. This wrapper delegates to the underlying native SDKs (Java on Android, v1 plugins on iOS), enabling legacy authentication flows to be invoked from Dart code through a standardized interface.
_packages/amplify\_native\_legacy\wrapper/lib · high confidence
Introduce new \`amplify\_push\_notifications\` package with WorkManager-based background handling
The \packages/notifications\ area now includes a new \amplify\_push\_notifications\ package that implements push notification handling for Flutter. On Android, this package replaces the deprecated \JobIntentService\ with \WorkManager\ to process notifications in the background, ensuring reliable delivery even when the app is in a killed state. The implementation introduces a dedicated background Flutter engine to execute Dart callbacks, manages lifecycle events to refresh tokens and clear launch notifications, and exposes event channels for token updates, notification opens, and foreground/background message delivery.
packages/notifications · high confidence
Introduce new amplify\_secure\_storage package with Android implementation
A new \amplify\_secure\_storage\ package is added to the repository, providing a Flutter plugin for secure key-value storage. This entry introduces the Android native implementation, including the \AmplifySecureStoragePlugin\ and \EncryptedKeyValueRepository\ classes which utilize Android's \EncryptedSharedPreferences\ for data protection. The package also includes the necessary project scaffolding (AndroidManifest, build configs, analysis options) and unit tests for the Android storage layer.
_packages/secure\storage · high confidence
Introduce structured types for user attribute updates and verification
The \amplify\_core\ package now exposes a dedicated set of types to manage the user attribute update flow. This includes \AuthUserAttributeKey\ and \CognitoUserAttributeKey\ (with standard and custom support) to identify attributes, \AuthUserAttribute\ to represent key-value pairs, and \AuthUpdateAttributeStep\ to define the state of the update process. The update operation now returns an \UpdateUserAttributeResult\ containing an \AuthNextUpdateAttributeStep\ (which references the \AuthUpdateAttributeStep\ enum) and an \isUpdated\ flag, allowing users to handle multi-step verification flows explicitly. Supporting types include \SendUserAttributeVerificationCodeResult\ for code delivery details and dedicated options classes for \confirmUserAttribute\, \fetchUserAttributes\, \sendUserAttributeVerificationCode\, \updateUserAttribute\, and \updateUserAttributes\.
_packages/amplify\core/lib/src/types/auth/attribute · high confidence
Introduces a common authentication provider abstraction for API requests
Adds a new \AmplifyAuthProvider\ interface and supporting types in \amplify\_core\ to standardize how authentication is applied to HTTP requests. This change introduces a repository pattern (\AmplifyAuthProviderRepository\) for managing auth providers and defines specific implementations for IAM (\AWSIamAmplifyAuthProvider\), API Key (\ApiKeyAmplifyAuthProvider\), and Token-based authentication (\TokenAmplifyAuthProvider\, \TokenIdentityAmplifyAuthProvider\). Users can now register and retrieve typed auth providers to authorize requests, providing a unified mechanism for handling different authentication modes across the SDK.
_packages/amplify\core/lib/src/types/common · high confidence
Introduces category-specific plugin interfaces for core Amplify services
The \amplify\_core\ package now exposes abstract plugin interfaces for each Amplify category (Auth, API, Storage, DataStore, Analytics, and Push Notifications) within the \lib/src/plugin\ directory. These interfaces define the contract for category-specific operations—such as authentication flows, GraphQL/REST requests, file uploads/downloads, data synchronization, event tracking, and push notification handling—allowing category implementations to register and be retrieved via a unified plugin system.
_packages/amplify\core/lib/src/plugin · high confidence
Introduces core state machine infrastructure and dependency management
This change adds the foundational classes for the new state machine architecture within \amplify\_core\. It introduces a \DependencyManager\ service locator (with scoped support and lifecycle management) to handle plugin dependencies like \AmplifyUserAgent\ and HTTP clients. It also defines the core state machine primitives: \StateMachineEvent\ and \StateMachineState\ base classes, \PreconditionException\ for validation errors, \EventCompleter\ for tracking async event processing across zones, and \StateMachineManager\ to coordinate event dispatching and state transitions. These components provide the underlying mechanism for managing plugin states and configurations.
_packages/amplify\_core/lib/src/state\machine · high confidence
Introduces the \`aft\` CLI tool for monorepo management
Adds the \aft\ command-line interface to the Amplify Flutter repository, providing a suite of commands to manage the monorepo. This includes \bootstrap\ to link packages and run dependency resolution, \constraints\ to check and update dependency versions across packages, \create\ to scaffold new packages using standard templates, \docs\ to build and serve API documentation, \exec\ to run shell commands across all packages, \link\ to generate local dependency overrides, and \publish\ workflows. The tool also includes utilities for cleaning build artifacts, locating packages, and extracting release notes.
packages/aft/lib/src/commands · high confidence
Introduction of AppPathProvider interface for cross-platform path resolution
The \amplify\_core\ package now exposes an \AppPathProvider\ interface that abstracts access to application-specific directories, specifically providing methods to retrieve the application support path and the temporary path. This interface is exported from the main library barrel, allowing developers to resolve file system locations in a platform-agnostic way within the Amplify ecosystem.
_packages/amplify\core/lib · high confidence
Introduction of push notification type definitions and exports
The \notification\_types.dart\ file has been added to the \amplify\_core\ package, serving as the central export hub for push notification-related types. This change introduces exports for platform-specific options (APNs, FCM), callback definitions, Pinpoint event sources and types, push notification messages, permission status enums, and the \PushNotificationException\. Users can now import this single file to access the foundational types required for implementing push notification functionality within the Amplify framework.
_packages/amplify\core/lib/src/types/notifications · high confidence
New API authorization type definitions and provider interfaces
The core library now exposes explicit type definitions for API authorization modes (none, API key, IAM, OIDC, Cognito User Pools, and Lambda) and abstract interfaces for authentication providers. This introduces \APIAuthorizationType\ to represent the supported authorization strategies for AppSync and API Gateway, along with \APIAuthProvider\, \OIDCAuthProvider\, and \FunctionAuthProvider\ classes that handle token retrieval for third-party and custom function integrations.
_packages/amplify\core/lib/src/types/api/auth · high confidence
New Amplify Firehose library for streaming data to Amazon Data Firehose
The \amplify\_firehose\ package is introduced, providing a Flutter implementation for streaming data to Amazon Data Firehose with offline support. This new capability allows developers to create a client, record data to a delivery stream, and flush it, with the package automatically handling storage paths via \path\_provider\. The release also includes an example application and integration tests to demonstrate usage.
packages/kinesis · high confidence
New Amplify configuration example app added
An example Flutter application has been added to demonstrate how to initialize and configure the Amplify SDK. The app initializes the configuration asynchronously in the main state and displays a boolean status indicating whether the configuration was successful, providing a basic template for integrating Amplify into a Flutter project.
_packages/amplify/amplify\flutter/example/lib · high confidence
New AuthConfig and CognitoPluginConfig classes for Gen 2 outputs
The auth configuration layer now includes new \AuthConfig\ and \CognitoPluginConfig\ classes (with generated serialization code) that support the Amplify Gen 2 outputs format. \AuthConfig\ provides a \cognito()\ factory helper to construct configuration from specific Cognito settings (user pool, identity pool, OAuth, social providers, MFA, etc.) and includes a \toAuthOutputs()\ method to convert the configuration into the Gen 2 \AuthOutputs\ structure. \CognitoPluginConfig\ acts as the internal plugin configuration container, holding references to user pool, auth, AppSync, Pinpoint, and S3 transfer utility settings, and is registered via \CognitoPluginConfigFactory\.
_packages/amplify\core/lib/src/config/auth · high confidence
New Dart-based GitHub Actions for Android and iOS emulator management
This change introduces a new Dart-based GitHub Action package located in \actions/bin\ that provides dedicated actions for launching and managing mobile emulators. Specifically, it adds \launch\_android\_emulator\ and \launch\_ios\_simulator\ actions, which allow CI workflows to configure API levels, targets, and ABIs for Android, and iOS versions and device types for iOS. These actions include built-in retry logic with configurable timeouts and automatic cleanup between attempts to improve reliability. Additionally, a \log\_cw\_metric\ action is added to report test outcomes to CloudWatch with detailed dimensions (such as framework, platform, and test type), and a \setup\_chromedriver\ action is included to automatically detect the local Chrome version and install the matching ChromeDriver. A build tool (\actions/tool/build.dart\) is also provided to compile these Dart entrypoints into distributable GitHub Actions.
actions/bin · high confidence
New DataStore Hub event types and payload classes
The \amplify\_core\ package now exposes a structured set of types for DataStore Hub events, allowing users to subscribe to specific lifecycle and sync notifications. This includes the \DataStoreHubEventType\ enum (covering states like \ready\, \networkStatus\, \modelSynced\, \outboxMutationEnqueued\, and \subscriptionDataProcessed\) and corresponding payload classes such as \ModelSyncedEvent\, \NetworkStatusEvent\, \OutboxMutationEvent\, \OutboxStatusEvent\, \SubscriptionDataProcessedEvent\, and \SyncQueriesStartedEvent\. Helper classes \HubEventElement\ and \HubEventElementWithMetadata\ are also provided to access model instances and metadata (version, lastChangedAt, deleted status) within these events.
_packages/amplify\core/lib/src/types/datastore/hub · high confidence
New DataStore conflict resolution and sync expression types
The DataStore API now exposes explicit types for handling sync conflicts and configuring data filtering. Users can define custom conflict handlers using the new \DataStoreConflictHandler\ typedef, which receives \ConflictData\ containing local and remote model instances and returns a \ConflictResolutionDecision\ (either \applyRemote\, \retryLocal\, or \retry\ with a custom model). Additionally, the \DataStoreSyncExpression\ class allows users to specify query predicates for selectively persisting subsets of data to the local device, with built-in support for serializing these expressions for native platforms.
_packages/amplify\_core/lib/src/types/datastore/conflict\handler · high confidence
New Gen 2 backend deployment tool for example apps
A new Dart-based CLI tool (\deploy\_gen2.dart\) has been added to the \infra-gen2/tool\ directory to automate the deployment of Amplify Gen 2 backends. This tool reads a configuration list covering API, Auth, Storage, Analytics, Kinesis, and Firehose categories, builds the respective backend projects, and generates the corresponding \amplify\_outputs.dart\ and \amplifyconfiguration.dart\ files into the example app directories for each category.
infra-gen2/tool · high confidence
New Mason brick templates for Dart and Flutter packages
Added new Mason brick templates (\dart-package\ and \flutter-package\) that provide a standardized starting point for generating Amplify Dart and Flutter packages. These templates include pre-configured project structures with Apache 2.0 licenses, analysis options using \amplify\_lints\, example applications (including a web example for Dart), and a post-generation hook that automatically links packages and runs \dart pub upgrade\ to streamline the initial setup process.
templates · high confidence
New \`aft generate\` subcommands for SDK, workflows, goldens, and Amplify Swift
The \aft\ CLI now includes a \generate\ command with four new subcommands: \sdk\ generates AWS SDK code from Smithy models, \workflows\ generates GitHub Actions and Dependabot configurations for repository packages, \goldens\ generates Smithy protocol test models, and \amplify-swift\ generates Swift DataStore plugin code. These commands automate the creation and maintenance of generated code and CI/CD configurations across the repository.
packages/aft/lib/src/commands/generate · high confidence
New build-support scripts for canary, integration testing, and cross-platform timeouts
This change introduces a suite of new shell and PowerShell scripts in the build-support directory to standardize and enhance the build and test infrastructure. The build\_canary.sh script automates the creation of a temporary Flutter project, adds core Amplify packages, and configures the Android toolchain (Gradle 8.14, Kotlin 2.2.20, Java 17) and iOS platform for canary builds. New integration test runners (integ\_test.sh, integ\_test\_ios.sh) support retry logic, cloud sync toggles, and WebAssembly compilation for web-server tests. Cross-platform timeout and retry capabilities are added via linux\_timeout\_attempts.sh, windows\_timeout\_attempts.ps1, and linux\_like\_timeout.ps1, enabling robust handling of flaky or long-running tests on Linux and Windows. Additional utilities include lint\_android.sh for background linting, codecov.sh for coverage reporting, and pull\_backend\_by\_app\_id.sh for backend synchronization.
build-support · high confidence
New changelog parsing and generation logic
The AFT tool now includes a new internal library for parsing and generating CHANGELOG.md files. This change introduces a \Changelog\ class that parses markdown into a structured representation of versions and commits, and provides methods to update changelog entries with commit messages. It supports semantic versioning, including a 'NEXT' tag for unreleased changes, and groups commits by type (features, fixes, breaking changes, etc.) for structured output.
packages/aft/lib/src/changelog · high confidence
New configuration model for Amplify Gen 2 outputs
The \amplify\_core\ package introduces a new set of configuration classes in \packages/amplify\_core/lib/src/config\ to support Amplify Gen 2 outputs. This includes \AmplifyConfig\ as the root configuration, \AmplifyPluginRegistry\ for managing plugin factories, and category-specific configs like \ApiConfig\ and \AWSApiPluginConfig\. These classes provide a structured way to parse and serialize configuration data, enabling better integration with Gen 2 output formats.
_packages/amplify\core/lib/src/config · high confidence
New core storage type definitions and interfaces
The \amplify\_core\ package now exposes the foundational type definitions for the Storage category, including request, response, and operation interfaces for all supported actions (upload, download, copy, move, remove, list, getUrl, getProperties). This introduces a new \StoragePath\ abstraction that supports both static paths and dynamic paths resolved from the user's identity ID, as well as a \StorageBucket\ type that can be resolved from the Amplify Outputs configuration to support multi-bucket scenarios. Users can now interact with storage operations using these strongly-typed core models, which include support for transfer progress tracking, data payloads, and configurable plugin options.
_packages/amplify\core/lib/src/types/storage · high confidence
New integration test infrastructure for Auth category
The \infra\ directory now contains a new AWS CDK project designed to provision backend environments for integration testing the Amplify Flutter packages. This infrastructure supports multiple Auth configurations, including full Cognito User and Identity Pools, custom authorizers (both IAM and User Pools), and custom authentication flows with and without SRP. It provides specific test capabilities such as device tracking, MFA (SMS and software token), user/device management, and custom SMS/email code interception via AppSync subscriptions.
infra · high confidence
New internal tooling scripts for versioning, licensing, and testing
Added a suite of new scripts in the \tool/\ directory to support internal release and quality processes. \bump\_version.dart\ automates updating version numbers in pubspec files, the main \amplify.dart\ entry point, and changelog headers. \license.sh\ manages Apache 2.0 license headers across the repository. \test\_all\_plugins.sh\ standardizes the execution of unit tests for Flutter, Android, and iOS plugins, outputting JUnit XML reports. Additional utilities include \create\_test\_profile.sh\ for configuring AWS credentials, \provision\_integration\_test\_resources.sh\ for deploying test infrastructure, \send\_metric\_data.dart\ for reporting canary metrics to CloudWatch, and \license.txt\ as a header template.
tool · high confidence
New model schema and type definitions in amplify\_core
The \amplify\_core\ package now includes a comprehensive set of new types for defining and representing data models, including \Model\, \ModelSchema\, \ModelField\, \ModelFieldType\, \ModelAssociation\, \AuthRule\, and \ModelIndex\. These classes provide the foundational structures for model schemas, field definitions, associations (HasMany, HasOne, BelongsTo), and authorization rules, enabling code generation and runtime model handling within the core library.
_packages/amplify\core/lib/src/types/models · high confidence
New provider interfaces for analytics context and lifecycle
The Pinpoint analytics plugin introduces a set of new abstract provider interfaces in the \flutter\_provider\_interfaces\ directory to decouple platform-specific logic. These include \AppLifecycleProvider\ for monitoring foreground/background state, \CachedEventsPathProvider\ for locating the local Drift database, \DeviceContextInfoProvider\ and \DeviceContextInfo\ for gathering and sanitizing device metadata (such as model, OS version, and locale) for Pinpoint endpoints, and \LegacyNativeDataProvider\ for retrieving stored Pinpoint Endpoint IDs. These interfaces define the contracts for how the analytics layer interacts with the underlying Flutter environment.
_packages/analytics/amplify\_analytics\_pinpoint\_dart/lib/src/impl/flutter\_provider\interfaces · high confidence
New push notification data types and service provider interface
The \amplify\_core\ package now includes new type definitions and an abstract interface to support push notifications. Users can now access \PushNotificationMessage\ for handling notification payloads (including title, body, deep links, and platform-specific options for APNS and FCM), \PushNotificationPermissionStatus\ to check permission states, and \PinpointEventType\/\PinpointEventSource\ for analytics events. Additionally, the \ServiceProviderClient\ abstract class is introduced, defining the contract for service providers (like FCM or APNS) to initialize, register devices, record events, and identify users.
_packages/amplify\core/lib/src/types/notifications/push · high confidence
New query field and predicate types for DataStore and API
The \amplify\_core\ package now exposes a new set of types in \packages/amplify\_core/lib/src/types/query\ to support model-based querying. This includes \QueryField\ for defining filter operations (such as equality, comparison, and containment), \QueryPredicate\ and \QueryPredicateGroup\ for composing complex query conditions, \QuerySortBy\ for ordering results, and \QueryPagination\ for managing result sets. Additionally, \QueryModelIdentifier\ provides a way to query models by their unique identifiers, and \ModelQueryException\ is introduced to handle errors specific to query operations.
_packages/amplify\core/lib/src/types/query · high confidence
New sign-in type definitions and options for the Auth API
The \amplify\_core\ package introduces a new set of types in \packages/amplify\_core/lib/src/types/auth/sign\_in\ to support the sign-in flow. This includes \AuthSignInStep\ and \AuthNextSignInStep\ to represent the current and next steps in authentication (such as MFA selection, TOTP setup, or password confirmation), \AuthFactorType\ to identify first-factor mechanisms like password or OTP, and \AuthProvider\ to handle social and federated identity providers (Google, Facebook, Apple, etc.). Additionally, dedicated options classes (\SignInOptions\, \ConfirmSignInOptions\, \SignInWithWebUIOptions\) are added to allow plugin-specific configuration for \Amplify.Auth.signIn\, \confirmSignIn\, and \signInWithWebUI\ calls.
_packages/amplify\_core/lib/src/types/auth/sign\in · high confidence
Smithy Dart goldens testbed infrastructure added
The \packages/smithy/goldens\ directory now includes the foundational project structure for the Smithy Dart golden testbed, containing the Apache 2.0 license, a README, Gradle wrapper scripts and configuration, and analysis options. It also introduces the initial generated Dart source code for the \awsJson1\_0\ protocol, including the \JsonRpc10Client\, \JsonRpc10Server\, endpoint resolution logic, and model serializers, providing a baseline for testing the code generator's output.
packages/smithy · high confidence
Support for Amplify Gen 2 configuration outputs
The core library now includes a new configuration schema (\AmplifyOutputs\) and associated data classes for all backend categories (Auth, Data, Storage, Analytics, Notifications, and REST API). This change enables the SDK to parse and utilize the new Gen 2 output format generated by the Amplify backend, allowing users to configure their apps using the modern Gen 2 configuration structure.
_packages/amplify\_core/lib/src/config/amplify\outputs · high confidence
API
AFT library exposes public API for command integration
The \packages/aft/lib\ package now provides a consolidated public entry point (\aft.dart\) that exports the library's core commands and utilities. This allows external consumers to import and use specific AFT functionalities—such as \run\, \exec\, \create\, \constraints\, and \version\_bump\—without needing to reference internal implementation paths, effectively establishing the public interface for the AFT tooling.
packages/aft/lib · high confidence
Architecture
Amplify Flutter adopts a federated plugin architecture with hybrid platform support
Amplify Flutter has been restructured into a federated plugin model, introducing a new \AmplifyHybridImpl\ that routes plugin registration to native iOS/Android method channels on mobile devices while falling back to pure Dart implementations on web. This change centralizes the \addPlugin\ logic, ensuring that Auth, Analytics, Storage, DataStore, API, and Push Notifications plugins are correctly wired to their respective platform-specific implementations during configuration.
_packages/amplify/amplify\flutter/lib/src · high confidence
Behavioural changes
12 commits (2 fixes) modifying packages/amplify\_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify\_datastore/pigeons
A change to existing behaviour in packages/amplify\_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify\_datastore/pigeons — 12 commits (2 fixs), 1 file: “chore: move native bridge impl to DataStore”; “chore: add package name to generated kt code”; “Chore(): dependency version bumps (\#6165)”; and 9 more (refs \#6165, \#4962, \#4279, \#3642, \#3250, …).
_packages/amplify\_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify\datastore/pigeons · medium confidence · unverified
28 commits (6 fixes) modifying packages/amplify\_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify\_datastore/types/model
A change to existing behaviour in packages/amplify\_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify\_datastore/types/model — 28 commits (6 fixs), 11 files: “chore: upgrade amplify-android to 1.19.0 (\#650)”; “Datastore support read only (\#1024)”; “chore(repo): standardize license headers (\#2501)”; and 25 more (refs \#650, \#1024, \#2501, \#4665, \#190, …).
_packages/amplify\_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify\datastore/types/model · medium confidence · unverified
5 commits (1 fix) modifying packages/amplify\_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify\_datastore
A change to existing behaviour in packages/amplify\_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify\_datastore — 5 commits (1 fix), 1 file: “fix(datastore): corrected getToken return value for oidc”; “chore: move native bridge impl to DataStore”; “chore: add package name to generated kt code”; and 2 more (refs \#4279).
_packages/amplify\_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify\datastore · medium confidence · unverified
65 commits (21 fixes) modifying packages/amplify\_datastore/android/src/main
A change to existing behaviour in packages/amplify\_datastore/android/src/main — 65 commits (21 fixs), 32 files: “feat(datastore): Add QueryPredicate.all (\#1310)”; “chore: upgrade amplify-android to 1.19.0 (\#650)”; “fix: UninitializedPropertyAccessException crash on Android when amplify\_datastore is included but not used”; and 62 more (refs \#1310, \#650, \#811, \#2501, \#1113, …).
_packages/amplify\datastore/android/src/main · medium confidence · unverified
7 commits (0 fixes) modifying packages/analytics/amplify\_analytics\_pinpoint/example
A change to existing behaviour in packages/analytics/amplify\_analytics\_pinpoint/example — 7 commits, 4 files: “chore(analytics): update analytics example app”; “feat: Support Amplify Gen 2 outputs (\#5073)”; “chore: Update lints”; and 4 more (refs \#5073, \#7285, \#1378, \#2634).
_packages/analytics/amplify\_analytics\pinpoint/example · medium confidence · unverified
AFT configuration model and loader migrated to pubspec.yaml
The AFT tool now reads its configuration from the \aft\ section within \pubspec.yaml\ files instead of a separate \aft.yaml\. This change introduces a new config model (\AftConfig\) and loader that parse global dependency constraints, environment settings, component definitions, and package selectors directly from the project's pubspec hierarchy, merging configurations from child directories into the root.
packages/aft/lib/src/config · high confidence
API exceptions are now sealed and structured hierarchically
The API category's exception types have been refactored to use Dart's sealed classes, introducing a strict hierarchy where \ApiException\ is the sealed base class. Two specific subclasses have been added: \HttpStatusException\ for REST API calls returning non-2xx status codes (which now exposes the raw HTTP response), and \ApiOperationException\ for in-process processing errors. This change aligns exception handling across the API category and may require updates to existing error-catch logic that relied on the previous, less structured exception types.
_packages/amplify\core/lib/src/types/exception/api · high confidence
Add Flutter-specific device context provider for Pinpoint analytics
The Pinpoint analytics plugin now includes a new Flutter implementation of the device context info provider. This change introduces a dedicated provider that collects app metadata (name, package name, version) and device details (make, model, platform, locale) from the Flutter environment to populate the Pinpoint EndpointDemographic object, replacing or supplementing previous platform-agnostic or native-specific logic with Flutter-native data sources.
_packages/analytics/amplify\_analytics\_pinpoint/lib/src/device\_context\_info\provider · high confidence
Added native API helper utilities for DataStore-Swift bridge
A new \native\_api\_helpers.dart\ utility file has been added to the DataStore package to facilitate communication with the native Amplify Swift layer. This file introduces functions for converting between native and Dart GraphQL request/response types, mapping authorization modes (such as API Key, IAM, OIDC, and User Pools) to their corresponding API types, and handling subscription lifecycle events (connecting, start\_ack, data, error, complete). It also includes logic to transform exceptions into error payloads, specifically tagging unauthorized errors to allow DataStore sync to continue silently.
_packages/amplify\datastore/lib/src/utils · high confidence
Amplify core restructured with new configuration and plugin registration logic
The \amplify\_core\ package has been refactored to introduce a new \AmplifyClass\ abstraction and its Dart implementation, \AmplifyClassImpl\. This change updates how plugins are registered and how the SDK is configured: the \configure\ method now explicitly supports both Gen 2 (\AmplifyOutputs\) and Gen 1 (\AmplifyConfig\) JSON formats, providing clearer error messages if decoding fails. Plugin registration has been enhanced to pass an \authProviderRepo\ to category-specific add methods, enabling better auth provider management. Additionally, the core version has been bumped to 2.15.1.
_packages/amplify\core/lib/src · high confidence
Analytics backend now supports configurable unauthenticated identity access
The analytics infrastructure backend has been updated to provide three distinct deployment configurations for handling unauthenticated users: a default setup that includes both authenticated and unauthenticated roles, a restricted setup that excludes unauthenticated roles entirely, and a secure setup that explicitly disables unauthenticated identities in the Cognito Identity Pool. These changes allow users to tailor the analytics backend's security posture regarding anonymous access without modifying the core Amplify Gen2 auth resource definitions.
infra-gen2/backends/analytics · high confidence
Analytics events now persist on Web using IndexedDB
The Pinpoint analytics plugin now stores queued analytics events locally on web platforms using IndexedDB, ensuring that events are preserved across page reloads and browser restarts. On non-web platforms (VM), the implementation continues to use the Drift SQL database for persistence. If IndexedDB is unavailable on the web, the system automatically falls back to an in-memory store, which means queued events will be lost when the page is closed.
_packages/analytics/amplify\_analytics\_pinpoint\_dart/lib/src/impl/analytics\_client/event\_client/queued\_item\store · high confidence
Analytics exceptions are now sealed with a dedicated base class
The analytics module now uses a sealed \AnalyticsException\ base class, replacing the previous abstract implementation. This change introduces a specific \InvalidEventException\ for cases where event data is invalid, and provides a \fromException\ factory method to automatically map generic exceptions (including \AWSHttpException\ and existing \AmplifyException\ instances) to appropriate analytics error types, ensuring more precise error handling for analytics operations.
_packages/amplify\core/lib/src/types/exception/analytics · high confidence
Analytics types consolidated into a single entry point
The analytics module now exposes its core types through a unified \analytics\_types.dart\ file. This change consolidates the public API by exporting the analytics-specific exception classes (such as \AnalyticsException\, \InvalidEventException\, \NetworkException\, and \UnknownException\) alongside the primary API types (\AnalyticsEvent\, \CustomProperties\, \UserProfile\, and \UserProfileLocation\). Users importing this module will now access these components from a single location rather than scattered paths.
_packages/amplify\core/lib/src/types/analytics · high confidence
Android legacy data migration for Pinpoint Endpoint ID
The Android implementation for the Pinpoint analytics plugin now includes support for migrating legacy endpoint data. A new Pigeon-generated interface and Kotlin plugin implementation allow the Flutter side to retrieve the legacy Pinpoint Endpoint ID from Android shared preferences, ensuring continuity for existing users during the transition to new data structures.
_packages/analytics/amplify\_analytics\pinpoint/android · high confidence
Android push notification event stream handling refactored
The Android implementation for push notifications has been refactored to use a new \PushNotificationEventsStreamHandler\ class. This change introduces a dedicated event queue mechanism that buffers notification events (such as token received, notification opened, and foreground messages) when the Flutter binary messenger is not yet ready, ensuring no events are lost during initialization. It also standardizes how events are flushed to the Dart side once the channel is active, replacing previous ad-hoc handling logic.
_packages/notifications/push/amplify\_push\notifications/android · high confidence
Android push notification host API bindings regenerated
The Android-side interface for communicating between the Flutter app and native push notification services has been regenerated. This update, produced by Pigeon v26.1.2, refreshes the \PushNotificationsHostApiBindings\ class to ensure correct serialization and deserialization of notification permissions and configuration options, addressing potential issues with platform message handling.
_amplify\_push\notifications · medium confidence
Auth exceptions are now sealed with specific subclasses
The Auth category's exception hierarchy has been restructured: the base \AuthException\ is now a sealed class, and specific error conditions (such as \InvalidStateException\, \AuthNotAuthorizedException\, \AuthServiceException\, \SessionExpiredException\, \SignedOutException\, \UserCancelledException\, and \AuthValidationException\) are now distinct, concrete types. This change improves type safety and allows developers to handle specific authentication errors more precisely rather than relying on generic exception handling.
_packages/amplify\core/lib/src/types/exception/auth · high confidence
Canaries project backend configuration migrated to Amplify CLI v3.1
The canaries project's Amplify backend configuration has been updated to version 3.1, introducing a new project structure that includes an AppSync API with automatic merge conflict resolution, a Cognito authentication setup with a PreSignup Lambda trigger, and Pinpoint analytics. This change adds the necessary CloudFormation templates and configuration files to define these resources, ensuring the canaries environment is provisioned with the correct infrastructure dependencies.
canaries/amplify, canaries/amplify/backend/function/canaries741cf74ePreSignup, canaries/tool · high confidence
Canary app now uses Amplify Authenticator and plugin options
The canary application in canaries/lib has been updated to integrate the Amplify Authenticator UI component, wrapping the main application to provide built-in sign-in and sign-out flows. Additionally, the Amplify configuration now passes the model provider via the APIPluginOptions constructor, aligning with the new plugin options pattern for optional parameters.
canaries/lib · high confidence
Centralized API type exports in amplify\_core
The \api\_types.dart\ file has been introduced to serve as a central export hub for API-related types within the \amplify\_core\ package. This change consolidates and exposes key components for users, including retry options, various exception types (such as \ApiException\ and \NetworkException\), authorization providers and types, GraphQL operation and response models, WebSocket options, Hub event structures, and REST/Pagination utilities. This simplifies imports for consumers needing access to these foundational API definitions.
_packages/amplify\core/lib/src/types/api · high confidence
DataStore example app now uses Authenticator and custom error handling
The DataStore example application has been updated to integrate the Amplify Authenticator for user sign-in flows and implements a custom error handler within the DataStore plugin options. This change ensures that the example app properly manages authentication state and provides feedback when DataStore operations encounter errors, reflecting current best practices for integrating DataStore with other Amplify plugins.
_packages/amplify\datastore/example/lib · high confidence
DataStore example models updated to use custom primary keys and new serialization formats
The generated model classes in the DataStore example app have been regenerated to support custom primary keys (CPK). This change introduces a \modelIdentifier\ getter on all models, deprecating the legacy \getId()\ method. Models with composite keys (such as \CpkHasManyChildBidirectionalExplicit\) now require multiple fields for their identifier. Additionally, the JSON serialization logic has been updated to handle nested model relationships via a \serializedData\ field, and required fields are now enforced with explicit runtime checks during deserialization.
_packages/amplify\datastore/example/lib/models · high confidence
DataStore exception handling and messaging refactored
The DataStore category's error handling has been restructured to improve clarity and serialization support. A new \DataStoreException\ class now extends \AmplifyException\ and includes a \fromMap\ factory method, allowing exceptions to be instantiated from serialized data maps. Additionally, a dedicated \DataStoreExceptionMessages\ class has been introduced to centralize common error messages, specifically providing detailed guidance for scenarios where a required, non-nullable field is accessed but was not initialized.
_packages/amplify\core/lib/src/types/datastore/exception · high confidence
DataStore observeQuery now supports configurable throttling
The DataStore observeQuery API now includes built-in throttling to prevent excessive event emissions during rapid sync changes. This change introduces a new ObserveQueryThrottleOptions configuration (allowing limits on count and duration) and implements the underlying stream transformation logic in the Dart package. Users will see smoother, rate-limited updates from observeQuery streams, reducing unnecessary processing when the local database is syncing heavily.
_packages/amplify\datastore/lib · high confidence
DataStore plugin architecture migrated to native method channels
The DataStore plugin implementation has been restructured to communicate with native iOS and Android backends via Flutter method channels. This change introduces a new \DataStoreStreamController\ to handle hub events (such as sync status and mutations) and a \DataStorePluginOptions\ class to centralize configuration like sync expressions, conflict handlers, and error handling. The core logic now resides in \method\_channel\_datastore.dart\, which serializes model data and delegates operations to the native layer, replacing the previous direct integration approach.
_packages/amplify\datastore/lib/src · high confidence
Datastore types consolidated into a single barrel file
The datastore type exports have been consolidated into a single \datastore\_types.dart\ file. This change reorganizes how users import core Datastore components—such as models, query fields, temporal types, conflict handlers, exceptions, hub events, and sync expressions—by providing a unified entry point instead of scattered individual paths.
_packages/amplify\core/lib/src/types/datastore · high confidence
Example app now supports multi-auth DataStore scenarios
The DataStore example application has been refactored to demonstrate multi-auth capabilities. A new \AuthView\ widget allows users to create and manage \MultiAuthTodo\ items alongside standard \PrivateTodo\ items, with real-time event streaming for both types. The app's navigation has been updated to include a tabbed interface (\NavigatorScaffold\) separating public data views from protected, authenticated views, enabling users to test DataStore operations under different authorization contexts.
_packages/amplify\datastore/example/lib/widgets · high confidence
Example app scaffold updated for Flutter 3.47 and linting standards
The amplify\_flutter example application has been regenerated to align with Flutter 3.47, introducing a new .metadata file to track project migration state and a .gitignore file that excludes generated artifacts like amplify\_outputs.dart. Additionally, the project now includes a README and an analysis\_options.yaml configuration that enforces the amplify\_lints package, ensuring consistent code quality checks for the example app.
_packages/amplify/amplify\flutter/example · high confidence
Example app updated to Flutter V2 embedding and Android API 32+ compatibility
The Android example application has been migrated to the Flutter V2 embedding model, which is required for modern Flutter versions and ensures compatibility with Android API 32 and above. This update includes new AndroidManifest files for debug and profile builds to grant internet permissions, a MainActivity implementation extending FlutterActivity, and updated theme resources to support the V2 embedding and dark mode.
_packages/amplify/amplify\flutter/example/android/app · high confidence
Flutter-specific analytics implementation and lifecycle management
The Pinpoint analytics plugin now includes a dedicated Flutter implementation layer that wires platform-specific providers into the core analytics logic. This introduces a Flutter app lifecycle observer to accurately track foreground and background state changes for session handling, and utilizes Flutter's secure storage and path providers to manage endpoint information and legacy data. These changes ensure the analytics service correctly integrates with Flutter's native environment for data persistence and lifecycle awareness.
_packages/analytics/amplify\_analytics\pinpoint/lib/src · high confidence
GraphQL API types and subscription status tracking
The GraphQL API type definitions have been restructured to support advanced request handling and subscription management. GraphQLRequest now includes support for custom headers, explicit authorization modes, and a copyWith method for request modification. Subscription connectivity is now observable via Hub events that expose detailed network and intended states, allowing applications to track connection status (connected, connecting, disconnected, failed) and implement custom reconnection or error-handling logic.
_packages/amplify\core/lib/src/types/api/graphql · high confidence
Introduce new Auth session and user type definitions
The auth core types have been restructured with new classes to model authentication state and user information. AuthSession now provides a simple isSignedIn flag, while AuthUser exposes userId, username, and SignInDetails. New option classes (FetchAuthSessionOptions, GetCurrentUserOptions) and their plugin-specific counterparts allow for configurable behavior in fetchAuthSession and getCurrentUser operations, including a forceRefresh option for credentials.
_packages/amplify\core/lib/src/types/auth/session · high confidence
Introduce new analytics type definitions for events, user profiles, and custom properties
The analytics core types have been restructured with the introduction of new model classes: \AnalyticsEvent\ now encapsulates event names and associated \CustomProperties\, while \CustomProperties\ provides a typed API for storing and retrieving string, double, boolean, and integer attributes. Additionally, \UserProfile\ and \UserProfileLocation\ classes have been added to support user-specific data, including location details like latitude, longitude, and city, enabling more granular user tracking and attribute management within the analytics system.
_packages/amplify\core/lib/src/types/analytics/analytics · high confidence
Introduce structured sign-out options and result types
The Auth category now exposes explicit \SignOutOptions\ and \SignOutResult\ types to manage sign-out behavior. Users can configure sign-out via a \globalSignOut\ flag to sign out the user from all devices, and pass plugin-specific options through \SignOutPluginOptions\. The sign-out operation now returns a dedicated \SignOutResult\ object, providing a structured response instead of an implicit or void return.
_packages/amplify\_core/lib/src/types/auth/sign\out · high confidence
Introduce structured types for the sign-up flow
The sign-up API now uses dedicated, serializable types to provide clearer structure and better type safety. \SignUpResult\ now exposes a \nextStep\ field of type \AuthNextSignUpStep\ (which contains an \AuthSignUpStep\ enum with \confirmSignUp\ and \done\ states) instead of a generic step description, and includes an optional \userId\. New options classes (\SignUpOptions\, \ConfirmSignUpOptions\, \ResendSignUpCodeOptions\) and result types (\ResendSignUpCodeResult\) are introduced to handle plugin-specific options and API responses consistently across the Auth category.
_packages/amplify\_core/lib/src/types/auth/sign\up · high confidence
Introduction of AmplifyLogger with hierarchical namespace support
The core logging system now uses a dedicated AmplifyLogger class that extends AWSLogger, establishing a strict namespace hierarchy rooted at 'aws\_common.Amplify'. This change ensures that all loggers created via the public API or internal mixins are automatically prefixed with the correct root namespace, preventing namespace collisions and providing consistent log level behavior across the Amplify framework. Additionally, a new AmplifyLoggerPlugin abstract class and AmplifyLoggerMixin are introduced to allow plugins to handle log entries and provide easy logger access to Amplify classes respectively.
_packages/amplify\core/lib/src/logger · high confidence
Introduction of RestOperation to handle non-streamed REST responses
A new RestOperation class has been added to the core API types to wrap AWSHttpOperation specifically for REST requests. This change ensures that REST responses are not streamed by default; if a response is identified as AWSStreamedHttpResponse, it is automatically read and converted into a standard AWSHttpResponse before being returned to the caller, simplifying the handling of REST API responses for users.
_packages/amplify\core/lib/src/types/api/types/rest · high confidence
Migrate Gen 2 auth backends to support Email OTP MFA
The Gen 2 authentication infrastructure backends have been updated to support Email OTP multi-factor authentication (MFA). This change introduces new backend configurations for various MFA scenarios, including optional and required modes for email, SMS, and TOTP factors. Specifically, it adds support for Email OTP MFA alongside existing SMS and TOTP options, allowing for more flexible authentication flows. The migration also includes adjustments to account recovery settings to comply with MFA requirements, such as disabling self-service recovery when email is used for MFA.
infra-gen2/backends/auth · high confidence
Modernized Android toolchain and project structure
The Android canary project has been updated to use Gradle 8.14, Kotlin Gradle Plugin 2.2.20, and Android Gradle Plugin 8.11.1. This includes adding a \.gitignore\ to exclude build artifacts and keystore files, creating standard Android manifest files for debug, profile, and main builds (including the required INTERNET permission for development), and setting up the necessary resource files for launch themes and splash screens. The main activity is now implemented in Kotlin as a standard FlutterActivity.
canaries/android · high confidence
New configuration models for AWS Pinpoint analytics
The analytics configuration layer now includes dedicated data models for AWS Pinpoint, specifically \AnalyticsConfig\, \PinpointPluginConfig\, \PinpointAnalytics\, and \PinpointTargeting\. These classes, generated with JSON serialization support, allow the SDK to parse and manage Pinpoint-specific settings such as the application ID and AWS region from configuration outputs, enabling more granular control over analytics plugin parameters.
_packages/amplify\core/lib/src/config/analytics · high confidence
New native plugin bridge definitions for DataStore
The DataStore package now includes a new Pigeon-based native bridge definition (native\_plugin.dart) that establishes the interface for communication between the Flutter DataStore plugin and native iOS/Android code. This file defines the specific API contracts for Auth (fetching sessions, updating current user), API (mutating, querying, subscribing, unsubscribing, handling offline states), and general Amplify configuration, along with the necessary data classes for GraphQL requests/responses and authentication credentials. This change introduces the structural bindings required for the native implementation, effectively moving the native bridge implementation details into the DataStore package.
_packages/amplify\datastore/pigeons · high confidence
Pinpoint SDK regenerated with mockable HTTP client support
The Amazon Pinpoint Dart SDK has been regenerated using smithy-dart 0.3.2, introducing a new \WrappedPinpointClient\ that delegates to the standard \PinpointClient\ while allowing the underlying HTTP client to be injected via the dependency manager. This change enables the analytics plugin to use a mockable HTTP client, which improves testability and allows for better control over network interactions during unit testing.
_packages/analytics/amplify\_analytics\_pinpoint\dart/lib/src/sdk · high confidence
Pinpoint analytics now throws standardized AnalyticsException
The Pinpoint analytics plugin now converts AWS SDK errors (such as BadRequestException and ForbiddenException) into the unified Amplify AnalyticsException type. This ensures that errors from Pinpoint are handled consistently with other analytics operations, providing users with standardized recovery suggestions and underlying exception details.
_packages/analytics/amplify\_analytics\_pinpoint\dart/lib/src/exception · high confidence
Platform detection now supports web browsers via user-agent parsing
The core platform abstraction has been updated to include a web-specific implementation that identifies the operating system and version by parsing the browser's user-agent string. This change allows the SDK to correctly report platform details (such as identifying Edge, Opera, Chrome, Firefox, or Safari) when running in a browser environment, complementing the existing native OS detection for IO-based platforms.
_packages/amplify\core/lib/src/platform · high confidence
Platform-specific path provider for cached events
The Pinpoint analytics plugin now uses a platform-aware path provider to locate the application support directory for storing cached events. On native platforms (iOS/Android/Desktop), it leverages the \path\_provider\ package to return the actual support directory path, while on Web it returns an empty string, effectively disabling local caching in the browser environment. This change ensures that event caching behaves correctly across all supported Flutter targets without throwing errors on unsupported platforms.
_packages/analytics/amplify\_analytics\_pinpoint/lib/src/flutter\_path\provider · high confidence
Redefines the public API surface for the Pinpoint analytics plugin
The main entry point for the \amplify\_analytics\_pinpoint\ package has been restructured to explicitly control which symbols are exposed to consumers. The library now re-exports the core implementation from the \amplify\_analytics\_pinpoint\_dart\ package while explicitly hiding the internal \AmplifyAnalyticsPinpointDart\ class, ensuring that only the intended public interface is available to users. Additionally, the \src/analytics\_plugin\_impl.dart\ file is now part of the public export list, making the plugin implementation details accessible to external code that depends on this specific package.
_packages/analytics/amplify\_analytics\pinpoint/lib · high confidence
Refactor password reset flow to use explicit step enumeration
The password reset workflow in the core Auth types has been restructured to use a dedicated \AuthResetPasswordStep\ enum (\confirmResetPasswordWithCode\, \done\) instead of previous generic or string-based step indicators. This change introduces new, clearly defined types for the reset and confirm-reset operations (\ResetPasswordOptions\, \ConfirmResetPasswordOptions\, \ResetPasswordResult\, \UpdatePasswordOptions\, \UpdatePasswordResult\) and their corresponding plugin-specific option abstractions, providing a more structured and type-safe API for handling password reset states and configurations.
_packages/amplify\core/lib/src/types/auth/password · high confidence
Refactor storage exceptions into a sealed hierarchy
The storage exception types in the core package have been restructured into a sealed class hierarchy. A new base \StorageException\ class now serves as the parent for specific error types, including \StorageAccessDeniedException\, \StorageHttpStatusException\, \InvalidStorageBucketException\, \StorageLocalFileNotFoundException\, \StorageNotFoundException\, \StorageOperationCanceledException\, and \StoragePathValidationException\. This change standardizes how storage-related errors are handled and reported within the application.
_packages/amplify\core/lib/src/types/exception/storage · high confidence
Refactored Pinpoint endpoint client with local storage and legacy migration
The Pinpoint analytics implementation now manages endpoint data (ID, global attributes, and metrics) locally using secure storage, replacing the previous approach. This change introduces a migration path that automatically transfers the existing Endpoint ID from the legacy native data provider to the new store, ensuring continuity for existing users. The new architecture includes an \EndpointClient\ that handles user profile updates and attribute management, an \EndpointGlobalFieldsManager\ for persisting attributes and metrics with enforced length limits, and an \EndpointInfoStoreManager\ to coordinate initialization and storage access.
_packages/analytics/amplify\_analytics\_pinpoint\_dart/lib/src/impl/analytics\_client/endpoint\client · high confidence
Regenerated AWS Pinpoint Dart SDK
The internal Pinpoint SDK implementation in the Amplify Analytics package has been regenerated using smithy-dart 0.3.2. This update refreshes the generated endpoint resolution logic to include FIPS-compliant endpoints for supported AWS regions and partitions, and rebuilds the data model classes (such as AttributeDimension and BadRequestException) with updated serialization and builder patterns to align with the latest AWS API specifications.
_packages/analytics/amplify\_analytics\_pinpoint\dart/lib/src/sdk/src · high confidence
Restructured public API exports in amplify\_flutter
The main library entry point has been reorganized to explicitly re-export the core Amplify singleton and specific serializers from amplify\_core and amplify\_secure\_storage. This change ensures that internal serialization types remain accessible to preserve backward compatibility while hiding implementation-specific classes like Amplify and WebSocketOptions from the public barrel, effectively tightening the public surface area of the package.
_packages/amplify/amplify\flutter/lib · high confidence
Reworked Auth Core Types and MFA Support
The \amplify\_core\ package has been refactored to provide a more structured and type-safe authentication API. This change introduces a new \AuthCodeDeliveryDetails\ class to explicitly track where confirmation codes are sent (email, SMS, TOTP, etc.) and replaces the previous \UserAttributeKey\ with \AuthUserAttributeKey\ for attribute updates. It also adds comprehensive support for TOTP Multi-Factor Authentication (MFA), including new types for setup (\TotpSetupDetails\, \TotpSetupOptions\), verification (\VerifyTotpSetupOptions\), and user preference management (\UserMfaPreference\, \MfaPreference\). Additionally, the \AuthNextStep\ hierarchy has been simplified to use specific enum-based step types for sign-in, sign-up, and password reset flows, improving clarity for developers handling multi-step authentication flows.
_packages/amplify\core/lib/src/types/auth · high confidence
Reworked exception and error type hierarchy
The exception handling in amplify\_core has been restructured to provide a clearer separation between recoverable exceptions and non-recoverable errors. A new \AmplifyError\ base class (with \ConfigurationError\ and \PluginError\ subclasses) now handles non-recoverable issues, while \AmplifyException\ serves as the base for recoverable errors across categories like API, Auth, Storage, and Analytics. Specific exception types such as \AmplifyAlreadyConfiguredException\, \NetworkException\, \UnknownException\, and \UrlLauncherException\ have been introduced or reorganized to improve type safety and debugging.
_packages/amplify\core/lib/src/types/exception · high confidence
Structured user-agent tracking for Amplify API calls
The HTTP layer now automatically enriches outgoing request headers with detailed user-agent information. A new \AmplifyHttpClient\ intercepts requests to append a scoped user-agent string that includes the base platform identifier (e.g., \amplify-flutter\ or \amplify-dart\), the OS, and the specific originating category and method (e.g., \auth/fetchCurrentDevice\). This is achieved via a new \AmplifyCategoryMethod\ enum system and zone-based context propagation, allowing backend services to distinguish traffic by the specific Amplify API being invoked.
_packages/amplify\core/lib/src/http · high confidence
Unified category API with multi-plugin support
The \amplify\_core\ library now exposes a consolidated category interface (\amplify\_categories.dart\) that manages plugin registration and dispatch for Analytics, API, Auth, DataStore, Notifications, Push Notifications, and Storage. This change introduces support for multiple plugins per category (e.g., \Auth\ and \Storage\ now allow \getPlugin\ to select specific providers), while maintaining backward compatibility by routing default calls to the first registered plugin. DataStore remains single-plugin with explicit configuration steps, and the Notifications category now delegates to a dedicated Push Notifications interface.
_packages/amplify\core/lib/src/category · high confidence
Updated Analytics example app with plugin options and secure storage configuration
The example application in the analytics Pinpoint package has been updated to demonstrate the new plugin options pattern and secure storage integration. The app now configures the \AmplifyAnalyticsPinpoint\ plugin using \AnalyticsPinpointPluginOptions\ to set the \autoFlushEventsInterval\, and passes a custom \secureStorageFactory\ to both the Auth Cognito and Analytics Pinpoint plugins to handle platform-specific secure storage requirements.
_packages/analytics/amplify\_analytics\pinpoint/example/lib · high confidence
Updated Android example app configuration for Flutter v2 embedding
The Android example app for the Pinpoint analytics plugin has been updated to use the Flutter v2 embedding. This includes migrating the MainActivity to extend FlutterActivity, adding the required flutterEmbedding meta-data to the AndroidManifest.xml, and introducing standard launch themes and splash screen resources to support modern Android development practices and API 32+ compatibility.
_packages/analytics/amplify\_analytics\pinpoint/example/android/app · high confidence
Updated Auth documentation with comprehensive sign-in flow examples
The \packages/amplify\_core/doc/lib/auth.dart\ file has been updated to provide detailed code excerpts for the Auth category. This includes new and expanded examples for handling various sign-in steps, such as MFA selection, TOTP setup and verification, email OTP, and passwordless flows, ensuring the documentation reflects the current API capabilities for user authentication.
_packages/amplify\core/doc/lib · high confidence
Updated iOS example app to support modern Flutter engine initialization
The iOS configuration for the Amplify Flutter example app has been updated to align with modern Flutter standards. The \AppDelegate\ now implements \FlutterImplicitEngineDelegate\ to support implicit engine initialization, and the \Info.plist\ has been configured with \UIApplicationSceneManifest\ and \CADisableMinimumFrameDurationOnPhone\ to support iOS 13+ scene lifecycle and modern display behavior. Additionally, the Xcode project structure has been refreshed to include standard Flutter build configurations and workspace settings.
_packages/amplify/amplify\flutter/example/ios · high confidence
Updated iOS example app to use the implicit Flutter engine
The iOS example app for the Pinpoint analytics plugin has been regenerated to support the implicit Flutter engine. This update introduces a new \AppDelegate.swift\ that implements \FlutterImplicitEngineDelegate\ to handle plugin registration, and updates the \Info.plist\ to configure the \FlutterSceneDelegate\ for modern iOS scene management. These changes ensure the example app remains compatible with current Flutter iOS standards.
_packages/analytics/amplify\_analytics\pinpoint/example/ios · high confidence
Updated web assets for the Flutter example app
The web entry point for the amplify\_flutter example has been updated to align with modern Flutter standards. The index.html file now includes a dynamic base href placeholder ($FLUTTER\_BASE\_HREF) to support non-root deployment paths, and the manifest.json has been refreshed to define the app as a standalone PWA with updated icon assets and theme colors.
_packages/amplify/amplify\flutter/example/web · high confidence
Updated web entry point for the Pinpoint analytics example app
The web entry point for the amplify\_analytics\_pinpoint example app has been updated to align with modern Flutter web standards. The index.html file now uses the $FLUTTER\_BASE\_HREF placeholder for the base path, ensuring correct asset resolution when the app is served from non-root paths. Additionally, a new manifest.json file has been added to define the app as a standalone PWA, specifying the app name, theme colors, and icon assets for mobile and desktop browsers.
_packages/analytics/amplify\_analytics\pinpoint/example/web · high confidence
iOS example app scaffolded with Flutter 3 multi-scene support
The iOS example project for the Amplify Native Legacy Wrapper has been initialized with a standard Flutter 3 template. This adds full support for the iOS 13+ multi-scene lifecycle (via UISceneConfiguration in Info.plist) and updates the AppDelegate to implement FlutterImplicitEngineDelegate, ensuring plugins are correctly registered when the implicit Flutter engine starts. The change also includes the necessary Xcode project structure, CocoaPods workspace configuration, and asset catalogs to allow the example app to build and run on modern iOS versions.
_packages/amplify\_native\_legacy\wrapper/example/ios · high confidence
iOS example workspace configuration added
The iOS example app for the Amplify DataStore package now includes the necessary Xcode workspace configuration files. This adds the workspace definition, enables the 32-bit warning check, and disables SwiftUI Previews by default, ensuring the example project builds correctly in Xcode without unnecessary preview compilation overhead.
_packages/amplify\datastore/example/ios/Runner.xcodeproj/project.xcworkspace · high confidence
Fixes
Fix Hosted UI exception names preserved under Android R8
The Android release build configuration now includes ProGuard rules to prevent R8 from renaming the \HostedUiException\ class and its subclasses. This ensures that error codes (such as "CANCELLED") sent to the Dart layer via the platform channel remain intact, fixing issues where obfuscation would otherwise corrupt exception handling during Hosted UI sign-in and sign-out flows.
packages/auth · high confidence
Test coverage
Add Worker Bee end-to-end test suites for Dart and Flutter; Add integration tests for the S3 storage plugin example app; Added Android unit tests for DataStore plugin and hub events; Added WASM smoke test for Analytics Pinpoint example; Added common test mocks for Pinpoint analytics; Added iOS unit test resources for Datastore model serialization and schema definitions; Added iOS unit tests for DataStore plugin; Added integration test driver entry point for Flutter example app; Added integration test for Amplify Flutter canary app; Added integration tests for DataStore query operations; Added integration tests for DataStore query predicates; Added placeholder test for AmplifyAnalyticsPinpoint; Added snapshot tests for the \aft version-bump\ command; Added test coverage for AFT changelog, constraints, and repository logic; Added test data for Amplify CLI configuration compatibility; Added test fixtures for Gen 2 outputs mapping; Added test resource for fake stream controller; Added test snapshots for \aft version-bump\ validation; Added tests for AFT command version resolution and release note extraction; Added tests for AWSEquatable equality logic; Added tests for Amplify Gen 2 outputs configuration parsing; Added tests for Amplify configuration parsing; Added tests for AmplifyConfig to AmplifyOutputs mapping; Added tests for Auth, DataStore, Storage, and TOTP types; Added tests for Hub channel listening and stream availability; Added tests for User-Agent header construction and propagation; Added tests for config loading and package selection logic; Added tests for plugin registration and auth provider interdependencies; Added tests for state machine dependency management and event handling; Added unit tests for Amplify Core configuration, auth providers, and temporal types; Added unit tests for Android DataStore query builders; Added unit tests for DataStore operations and configuration; Added unit tests for Datastore plugin interface models and queries; Added unit tests for Pinpoint Analytics client and storage components; Added widget smoke test for the canary application; Amplify API example app restructured for multi-platform integration testing; Expanded DataStore integration tests for custom primary keys and auth models; New DataStore integration test utilities for the Flutter example app; New integration test packages for Auth and general Amplify testing; New snapshot script for version-bump testing; Updated Chrome for Testing download manifest; iOS example app adds DataStore unit test infrastructure.
Dependencies
Update Gradle wrapper to version 8.14
The Android example project now uses Gradle 8.14 for building, ensuring the build toolchain is up to date with the latest distribution.
_packages/amplify\datastore/example/android/gradle · high confidence
Update infrastructure and example apps to modern toolchains and SDKs
This change updates the project's infrastructure and example applications to use modern development toolchains and SDK versions. The Dart SDK requirement is raised to ^3.11.0 across the monorepo, and the Flutter minimum version is set to 3.41.0. On the Android side, the Gradle Plugin is upgraded to 8.11.1, Kotlin to 2.2.20, and the compile SDK to 36, with Java compatibility set to version 17. The infrastructure (infra-gen2) dependencies are also updated, including aws-cdk-lib to ^2.265.0 and various AWS SDK packages.
(dependencies) · high confidence
Updated Gradle wrapper to version 8.14
The example app's Gradle wrapper has been updated to use Gradle 8.14. This ensures that the build environment for the Android example project uses this specific version of the Gradle build tool, which may affect build performance and compatibility with the Android Gradle Plugin.
_packages/amplify/amplify\_flutter/example/android/gradle, packages/amplify\_datastore/android/gradle, packages/analytics/amplify\_analytics\pinpoint/example/android/gradle · high confidence
Housekeeping
Initial package scaffolding for Amplify Analytics Pinpoint; Initial repository scaffolding and documentation.
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 47.2 → 30.6 (-16.6)
- Rubric changed (rubric-2026.11.2 → rubric-2026.11.4) — scores are not directly comparable.
Lenses
- Code Health 50.4 → 38.4 (-12.0)
- Architecture 87.0 → 86.5 (-0.5)
- Maturity 69.6 → 81.1 (+11.5)
- Readiness 38.9 → 41.3 (+2.4)
- Security 62.1 → 62.1 (0.0)
- Domain Modelling 100.0 → 100.0 (0.0)
- Event-Driven 80.0 → 80.0 (0.0)
- Event Sourcing 48.6 → 10.0 (-38.6)
- Performance 60.0 → 60.0 (0.0)
Resolved (623)
- Concentrated knowledge decay
- Duplicated block (10 lines × 2) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/DataStoreHubEventStreamHandler.swift)
- Duplicated block (10 lines × 2) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift)
- Duplicated block (10 lines × 3) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift)
- Duplicated block (10 lines × 4) (packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart)
- Duplicated block (10–11 lines × 3) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/DataStoreHubEventStreamHandler.swift)
- Duplicated block (11 lines × 2) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Core/Support/AmplifyTaskGateway.swift)
- Duplicated block (11 lines × 2) (packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart)
- Duplicated block (11–12 lines × 2) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSDataStorePluginInternal/Configuration/DataStoreConfiguration+Helper.swift)
- Duplicated block (12 lines × 2) (packages/auth/amplify_auth_cognito_dart/lib/src/flows/hosted_ui/hosted_ui_platform_io.dart)
- Duplicated block (13 lines × 3) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageDownloadDataRequest.swift)
- Duplicated block (14 lines × 2) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AmplifyInternal/Categories/Storage/Operation/Request/StorageDownloadFileRequest.swift)
- Duplicated block (16 lines × 2) (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart)
- Duplicated block (16 lines × 24) (packages/auth/amplify_auth_cognito_dart/lib/src/sdk/sdk_bridge.dart)
- Duplicated block (17 lines × 3) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/SwiftAmplifyDataStorePlugin.swift)
- Duplicated block (18 lines × 2) (packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt)
- Duplicated block (19 lines × 2) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/FlutterOutboxMutationEnqueuedEvent.swift)
- Duplicated block (20 lines × 2) (packages/smithy/smithy/lib/src/serialization/xml/xml_built_list_serializer.dart)
- Duplicated block (20 lines × 3) (packages/amplify_datastore/darwin/amplify_datastore/Sources/amplify_datastore/AWSPluginsCoreInternal/Model/GraphQLDocument/GraphQLMutation.swift)
- Duplicated block (27 lines × 2) (packages/amplify_datastore/android/src/main/kotlin/com/amazonaws/amplify/amplify_datastore/AmplifyDataStorePlugin.kt)
- …and 603 more
New (276)
- Critical vulnerability: [GHSA redacted] (packages/worker_bee/worker_bee/example/tool/example_web_tester/requirements-lock.txt)
- Documentation: no build, run or usage example (actions/README.md)
- Documentation: no build, run or usage example (packages/amplify/amplify_flutter/README.md)
- Documentation: no build, run or usage example (packages/amplify_connect_client/amplify_connect_client_dart/README.md)
- Documentation: no build, run or usage example (packages/amplify_core/README.md)
- Documentation: no build, run or usage example (packages/amplify_datastore/README.md)
- Documentation: no build, run or usage example (packages/amplify_datastore_plugin_interface/README.md)
- Documentation: no build, run or usage example (packages/amplify_foundation/amplify_foundation_dart/README.md)
- Documentation: no build, run or usage example (packages/amplify_foundation/amplify_foundation_dart_bridge/README.md)
- Documentation: no build, run or usage example (packages/amplify_lints/README.md)
- Documentation: no build, run or usage example (packages/analytics/amplify_analytics_pinpoint/README.md)
- Documentation: no build, run or usage example (packages/analytics/amplify_analytics_pinpoint_dart/README.md)
- Documentation: no build, run or usage example (packages/api/amplify_api/README.md)
- Documentation: no build, run or usage example (packages/api/amplify_api_dart/README.md)
- Documentation: no build, run or usage example (packages/auth/amplify_auth_cognito/README.md)
- Documentation: no build, run or usage example (packages/auth/amplify_auth_cognito_dart/README.md)
- Documentation: no build, run or usage example (packages/aws_common/README.md)
- Documentation: no build, run or usage example (packages/common/amplify_db_common/README.md)
- Documentation: no build, run or usage example (packages/common/amplify_db_common_dart/README.md)
- Documentation: no build, run or usage example (packages/kinesis/amplify_firehose_dart/README.md)
- …and 256 more
Changes since last survey
- 6 commits — 3 feature/other, 3 fixes
By area
- packages/aft — 2 commits
- .github/workflows — 1 commit
- build-support/linux_timeout_attempts.sh — 1 commit
- packages/analytics — 1 commit
- packages/smithy — 1 commit
Notable commits
- fix: fix(aft): Catch dependabot.yaml, new and stale workflows in --set-exit-if-changed (#7558)
- fix: fix(aft): Dedupe Dependabot entries, gate E2E jobs on platform dirs, detect darwin/ (#7557)
- fix: fix(ci): Capture timeout exit code in linux_timeout_attempts.sh (#7555)
- change: chore(deps): Pin os_detect below 2.0.4 (#7556)
- change: chore(deps): Pin source_helper below 1.4.0 for Dart 3.11.0 builds (#7549)
- change: test(analytics): Remove Pinpoint integration tests (#7550)
Architecture
- Containers 0 added · 0 removed · contexts 3 added · 3 removed · edges 0 added · 0 removed
Added bounded contexts (3)
- packages/amplify_datastore/android
- packages/auth/amplify_auth_cognito/android
- packages/notifications/push/amplify_push_notifications/android
Removed bounded contexts (3)
- packages/amplify_datastore/android
- packages/auth/amplify_auth_cognito/android
- packages/notifications/push/amplify_push_notifications/android
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
aws-amplify/amplify-flutter was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 17 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit f418245a021706bb977b0a2d1a56b7a42659a7d4 — the exact code this score is about.
- Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.85+preprod-eba6548ac50f.