awesome_notifications_fcm

Breaking changes

• licenseKeys parameter removed: deprecated and ignored since 0.11.0, the licenseKeys argument of initialize(...) has now been removed — delete it from your call.

Added

• Swift Package Manager support (iOS): the plugin ships a Package.swift and installs through Swift Package Manager, keeping CocoaPods support during the transition. The Notification Service Extension is Flutter-free — it extends IosAwnFcmCore's AwesomeServiceExtension directly and links the core through SwiftPM, with Firebase resolved once via firebase-ios-sdk.

Changed

• Native cores updated to 0.12.0. The Android cores me.carda:AndroidAwnCore and me.carda:AndroidAwnFcmCore are now published on Maven Central instead of JitPack (resolved through mavenCentral()), and the iOS cores IosAwnCore/IosAwnFcmCore are consumed through Swift Package Manager from their published 0.12.0 tags.
• Requires awesome_notifications, IosAwnCore and IosAwnFcmCore 0.12.0.

Merge branch 'main' into development

Breaking changes

• licenseKeys parameter deprecated: License keys are no longer required. The license validation has been completely removed from the native core libraries (AndroidAwnFcmCore and IosAwnFcmCore). The licenseKeys parameter in initialize() is now ignored and will be removed in a future version.
• iOS minimum deployment target raised to 15.0: The minimum iOS deployment target has been increased from iOS 13 to iOS 15, aligning with the awesome_notifications core plugin requirements.
• Android minimum SDK raised to 23: The minimum Android SDK has been increased from 21 to 23, matching the core plugin.
• firebase_crashlytics dependency removed: The plugin no longer depends on or integrates with Firebase Crashlytics. Internal exceptions are now logged via the standard platform logger. Apps that need crash reporting should integrate Crashlytics independently.
• firebase_core minimum version raised to 4.0.0: Required to support Firebase iOS SDK 12.x and Firebase Android BOM 33.x, which are needed by IosAwnFcmCore 0.11.0 and AndroidAwnFcmCore 0.11.0. Update your firebase_core dependency to ^4.0.0.
• Build system updated: AGP 8.1.0 → 8.1.4, Gradle 8.3 → 8.13, compileSdk 34 → 36, dependencies updated (guava 33.5.0, annotation 1.9.1).

Removed

• License key validation removed: The entire license validation system has been removed, making the plugin fully open source and free to use without restrictions.
• Firebase Crashlytics integration removed: The FirebaseCrashlytics.recordException() call and the firebase_crashlytics dependency have been removed from all layers (Dart, Android, iOS).

Updated

• Native libraries updated: AndroidAwnCore and AndroidAwnFcmCore updated to 0.11.0, IosAwnCore and IosAwnFcmCore updated to 0.11.0.
• Dependencies updated: All project dependencies have been upgraded to their latest versions, ensuring compatibility with awesome_notifications 0.11.0.

Fixed

• Updated Android native library to fully support Flutter 3.27: Removed deprecated Flutter V1 libraries on Android, ensuring compatibility with Flutter 3.27.

We are thrilled to announce the release of Version 0.10.0 of our software, which includes several critical updates and changes that enhance functionality and compatibility with the latest platform standards. This version introduces breaking changes necessary for modernizing our setup, improves compatibility with the latest Flutter release, and updates various project components to ensure peak performance and security.

Breaking Changes

• Pod Modifications: The installation of flutterfire_cli is now required to configure Firebase with the latest features. This ensures that the project remains aligned with Firebase best practices.
• iOS Minimum Deployment Target Increased to 13: Updated the minimum deployment target for iOS to 13 to accommodate the latest Firebase Core library restrictions.
• Minimum Android SDK Increased to 23: This change leverages modern Android capabilities and security features, aligning with the best resources for Android platform security.

Improvements

• Flutter 3.24.0 Compatibility: Fully supports the latest Flutter 3.24.0 release, ensuring compatibility and optimal performance across all platforms.

Deprecations

• Deprecation of sendPushNotification Method: The sendPushNotification method has been deprecated and will be removed in version 1.0.0. This decision aligns with Google's decommissioning of FCM upstream messaging. Developers are encouraged to use a REST API and the Firebase Admin SDK for device communications and notifications.
  • Migration Guide: Detailed documentation is provided to aid developers in migrating to the new messaging approach, with examples and best practices outlined in our updated Javadoc.

Enhancements

• Dependencies Updated: All project dependencies have been upgraded to their latest versions to ensure the most secure, stable, and efficient operation.
• Refreshed Documentation: Comprehensive updates to our documentation enhance developer experience, making integrating and using Awesome Notifications clearer and more straightforward.

We encourage all users to update to version 0.10.0 to take advantage of these improvements and adjustments. This update aligns with the latest development standards and ensures that your application is built on a secure and compliant foundation.

Breaking Changes

• Pod Modifications: Installation of flutterfire_cli is now necessary to configure Firebase with the latest features, ensuring the project is up-to-date with Firebase best practices.
• iOS Minimum Deployment Target Increased to 13: AUpdated the minimum deployment target for iOS to 13 to comply with the latest Firebase Core library restrictions.
• Minimum Android SDK Increased to 23: Elevated to utilize modern Android capabilities and security features, aligning with best security resources for Android platform.

Improvements

• Flutter 3.24.0 Compatibility: Fully supporting the latest Flutter 3.24.0, ensuring compatibility and optimal performance across all platforms.

Deprecations

• Deprecation of sendPushNotification Method:
  • As part of our transition to modern messaging patterns, the sendPushNotification method has been marked as deprecated. This change follows Google's announcement to decommission FCM upstream messaging in June 2024.
  • Developers are now encouraged to implement a REST API on their server to handle communication from devices and use the Firebase Admin SDK to send notifications.
  • The deprecated method now triggers a NotImplementedError with a clear message and detailed Javadoc documentation to guide developers in migrating to the new approach. This method will be removed in version 1.0.0.

Enhancements

• Dependencies Updated: All project dependencies have been upgraded to their latest versions, ensuring the most secure, stable, and efficient operation.
• Refreshed Documentation: Comprehensive updates to our documentation make integrating and using Awesome Notifications clearer and more straightforward, enhancing developer experience and facilitating easier integration.

Customization Over Firebase:

• In our ongoing effort to deliver a powerful notification experience, we've made a crucial update to the Awesome FCM interpreter. This version now gives preference to remote Awesome Notifications customizations over Firebase remote configurations, unlocking the full potential of notification features regardless of Firebase's limitations.

Dependency Updates:

• To maintain the highest standards of stability and compatibility, we've updated all core dependencies to version 0.9.3. This ensures that awesome_notifications_fcm is aligned with the latest enhancements, security patches, and performance improvements available in the ecosystem.

Enhancements

• Enhanced the Awesome FCM interpreter logic to prioritize Awesome Notifications customizations over Firebase remote configurations. This change allows developers to fully utilize Awesome Notifications features without being constrained by Firebase's configuration settings.

Dependency Updates

• Updated all core dependencies to version 0.9.3, ensuring the package remains robust against the latest software environment changes and continues to provide a secure, efficient notification service.

Transition Support from Github to Discord Community

• GitHub Issues Closure: Effective immediately, GitHub issues will no longer be open for new support requests. Existing issues will remain accessible as an archive and resource.
• Discord Community Support: All support for Awesome Notifications has transitioned to our Discord community. This move aims to provide a more dynamic, interactive, and efficient support experience.
• Reasons for Change:
  • Community Rules Respect: Numerous issues posted on GitHub have not adhered to our community guidelines, impacting heavily on support efficiency and effectiveness.
  • Efficiency and Effectiveness: Managing support through GitHub has become exceedingly time-consuming, particularly when posts omit critical information or disregard guidelines.
  • Quality of Support: Our Discord community allows for real-time engagement, resource sharing, and a closer-knit user and developer interaction, which wasn't true for GitHub.
• Next Steps for Users: We encourage all users to join our Discord community https://discord.awesome-notifications.carda.me/ for ongoing support, updates, and to connect with fellow users and the development team.

Enhancements & Fixes

• Refined Notification ID Handling for Stringify and Legacy Data Standards: Altered the priority logic for push notification IDs in cases using stringify and legacy data standards. Now, Awesome IDs take precedence over Firebase IDs. This change enables more effective management of push notifications, allowing new notifications to replace or update previous ones with the same ID. It brings a higher level of control and dynamism to notification behavior.

[0.9.1] - 01/04/2024

Enhancements & Fixes

• iOS Target Extension Deployment Flexibility: Updated the iOS pod script to enable manual adjustments of the minimum target deployment. This improvement offers greater control and customization to developers in line with their specific iOS deployment needs.
• Expanded Documentation on Data Standards: Enhanced the documentation to provide comprehensive guidance on the three distinct data standards available for crafting push notifications via FCM. This update aims to clarify and streamline the notification creation process for developers.

Enhancements & Fixes

• iOS Target Extension Deployment Flexibility: Updated the iOS pod script to enable manual adjustments of the minimum target deployment. This improvement offers greater control and customization to developers in line with their specific iOS deployment needs.
• Expanded Documentation on Data Standards: Enhanced the documentation to provide comprehensive guidance on the three distinct data standards available for crafting push notifications via FCM. This update aims to clarify and streamline the notification creation process for developers.

• Remote Procedure Calls (RPC): Introducing advanced remote procedure calls in our FCM services. You can now dismiss, cancel schedules, or cancel notifications remotely. This feature works with both standard notifications and silent pushes, giving you greater control over your notification management.

• Flattened Data Standard for Push Notifications: We're proud to roll out a new flattened data standard. This enhancement allows for sending push notifications using the V1 protocol or directly through the Firebase console while retaining access to all the awesome notification features our users love.

• Full Firebase Console Support: Leverage all features of Awesome Notifications directly via the Firebase console using the new flattened data standard, enhancing flexibility and control.

Breaking Changes

• Pod Modifications: It's now necessary to add the Awesome Notifications pod modification inside the Podfile in the iOS folder.
• Receive Port and Send Port: The methods sendPort.send() and receivePort!.listen() now only accept serialized data, not objects. Convert your data to map format and reconstruct it later from this format.
• License Key (Year 2): With the start of year 2 support for the Awesome Notifications suite, updating your license keys is required. If your purchase was made less than 1 year ago, you're still under the 1-year purchase support and simply need to reply to the license email requesting a free update.

Improvements

• Flutter 3.16.0 Compatibility: Fully supporting the latest Flutter 3.16.0, ensuring compatibility and optimal performance.
• Flattened Data Standard: Introducing a new method for sending notifications using the V1 protocol without the need for Stringify. This streamlined approach simplifies the notification-sending process.
• Full Firebase Console Support: Leverage all features of Awesome Notifications directly via the Firebase console using the new flattened data standard, enhancing flexibility and control.
• Postman Examples Updated with Flattened Standard: All Postman examples have been updated to incorporate the new flattened data standard, while maintaining support for all other previous push patterns.

Enhancements

• Dependencies Updated: All project dependencies have been upgraded to their latest versions, ensuring the most secure, stable, and efficient operation.
• Refreshed Documentation: Comprehensive updates to our documentation make integrating and using Awesome Notifications clearer and more straightforward.

Added

• Full support for Flutter 3.13
• Support for Android 14
• Support for iOS 17
• Compatibility with AGP 8

Improved

• Project dependencies upgraded to the latest version available
• Documentation updated

Improved

• Android core dependencies moved to new repository
• Added new native module switcher to avoid the folder copy at example/android folder.
• Subtitle added to iOS notifications
• Fcm token order switched to get called after APNs token return
• native fromMap methods switched to convenient initializers

Added

• Asset and resource media files to push notifications.
• A new method to delete FCM token and reset all topics.
• Translation feature to push notifications.
• AwnAppGroupName parameter to info.plist for setting a fixed App Group name (iOS).

Merge pull request #6 from rafaelsetragni/broadcast-events-lifecycle

## [0.7.4]
* Fixed labels for silent handle and action handle
* Added option to send multiple license keys, dismissing the necessity to switch it to each bundle ID