Firebase Messaging - v8.0.0 dev channel feedback.

[Salakar]

This discussion is for providing feedback for the upcoming v8.x.x release line of the firebase_messaging plugin.

General guidelines when posting;

• If you have a general question about the dev release, ask here.
• If you have feedback on documentation, post it here.
• If you want to contribute a feature or bug fix to the dev release line and need help, ask here.
• If you have come across a bug or crash, please raise a new issue first with as much detail as possible, and then post a link to the issue here in this discussion.

Current dev version: 8.0.0-dev.6

See the migration guide for help on upgrading and for the changelog.

Thanks everyone 🤓

[Salakar]

#3991

[chen965]

🔥

[joniaiuser]

@Salakar For Android v2 embedding to work, there is a need to modify the incoming notification payload to remove click_action. Otherwise, we will end up with /FirebaseMessaging: Notification pending intent canceled error. This is the case even when we remove the corresponding click_action reference in AndroidManifest.xml.. Might want to consider mentioning this in the migration doc.

Also, I notice that while onMessageOpenedApp works well for android, it seems that getInitialMessage does not read the data message unlike in iOS. Not sure if it's because of the simulator lag. Will test more thoroughly tomorrow.

[Salakar]

Good spot re the click action - will get this added for the migration guide.

I fixed a couple of Android things so please try getInitialMessage again with 8.0.0-dev.6. I wasn't able to reproduce and had it working when opening an app from a closed state via pressing a notification.

[joniaiuser]

I haven't been able to get the navigator when opening from a closed state. But I observe the same issue for local notifications currently. I suspect it may be a simulator lag issue; some kind of race condition.. Will try again with actual devices when deployed to Alpha test track.

[PcolBP]

#4054

Does iOS platform needs something more than current migration guide?

[Salakar]

Yes, you need to follow the installation guide, integrate with APNs and use a real iOS device; https://firebase.flutter.dev/docs/messaging/overview

[jdeltoft]

Thanks for the update and guide link @Salakar. I started following the guide but when I got to the final sections I didn't really see much help on how to change my code to deal with the fact that Firebase Messaging deprecated the configure() function. I used to have this but now configure is gone and there is no mention even of the onIosSettingsRegistered being deprecated. Is there any help for this?

[Pcol10]

Configure was replaced with static methods such as:

 FirebaseMessaging.onMessage
          .listen((message) =>_yourMethodToCall() );

FirebaseMessaging.onMessageOpenedApp
          .listen((message) => _yourMethodToCall() );

onBackgroundMessage has to be top level function (example below)

Future<void> _firebaseMessagingBackgroundHandler(RemoteMessage message) async {
  // If you're going to use other Firebase services in the background, such as Firestore,
  // make sure you call `initializeApp` before using other Firebase services.
  await Firebase.initializeApp();

  print("Handling a background message: ${message.messageId}");
}

void main() {
  FirebaseMessaging.onBackgroundMessage(_firebaseMessagingBackgroundHandler);
  runApp(MyApp());
}

About IosNotificationSettings everything is in changelog =>

You have to just await for result of requestPermission which returns NotificationSettings.

[jdeltoft]

Ah, ok. thank you very much for the help @Pcol10 !

[timosturm]

Adding missing features: the issue triage and API review has highlighted a number of missing features which will be implemented as part of the plugin updates. In general if the underlying platform Firebase SDK supports a feature cross-platform then so should FlutterFire.

Will the new version support setting the firebase config manually instead of requiring a google-services.json? This is supported by the native libraries on android and iOS but was missing from this plugin before.

[jdeltoft]

Ok, I used https://stackoverflow.com/a/57789633/559525 .

This helped me a lot to know about this way to get gradle log directly, but I still had a hard time (and had to get lucky I think in a sense) to know what version to use for my top level dependency.

For me the fix was:
implementation 'com.google.android.gms:play-services-vision:20.1.0'

but I wasn't sure where to find what versions were even available for play-services-vision (20.1.2 was the latest I think?? but 20.1.0 worked). I got this from https://developers.google.com/android/guides/setup

[pinpong]

Hi,

I've added the service notification extension as it is described in the apple integration guide and I got following error:

Multiple targets match implicit dependency for linker flags -framwork googl utilities.

It's not possible to link messaging pod from runner target?

[ncuillery]

I believe I have something similar. I have added the Notification Service Extension to my project according to this guide, faced a couple of hurdles I managed to fix but now, I'm stuck with errors relative to duplicate dependencies between my 2 targets Runner and ImageExtension:

Multiple targets match implicit dependency for linker flags '-framework FBLPromises'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'Runner' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework FirebaseCore'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'Runner' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework FirebaseCoreDiagnostics'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'Runner' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework FirebaseInstallations'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'Runner' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework FirebaseInstanceID'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'Runner' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework FirebaseMessaging'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'Runner' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework GoogleDataTransport'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'Runner' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework GoogleUtilities'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'Runner' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework Protobuf'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'Runner' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework nanopb'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'Runner' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework FBLPromises'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ImageNotification' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework FirebaseCore'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ImageNotification' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework FirebaseCoreDiagnostics'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ImageNotification' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework FirebaseInstallations'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ImageNotification' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework FirebaseInstanceID'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ImageNotification' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework FirebaseMessaging'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ImageNotification' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework GoogleDataTransport'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ImageNotification' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework GoogleUtilities'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ImageNotification' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework Protobuf'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ImageNotification' from project 'Runner')
Multiple targets match implicit dependency for linker flags '-framework nanopb'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ImageNotification' from project 'Runner')

So it seems that there are 10 packages that causing the build issues, I believe they are FirebaseMessaging and its transitive dependencies.

Immediately after, I have the real errors, one for each of the 10 packages:

error: Multiple commands produce '/Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Protobuf.framework':
error: Multiple commands produce '/Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/FBLPromises.framework':
error: Multiple commands produce '/Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/FirebaseMessaging.framework':
error: Multiple commands produce '/Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/nanopb.framework':
error: Multiple commands produce '/Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/FirebaseInstanceID.framework':
error: Multiple commands produce '/Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/GoogleDataTransport.framework':
error: Multiple commands produce '/Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/GoogleUtilities.framework':
error: Multiple commands produce '/Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/FirebaseInstallations.framework':
error: Multiple commands produce '/Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/FirebaseCoreDiagnostics.framework':
error: Multiple commands produce '/Users/vagrant/Library/Developer/Xcode/DerivedData/Runner-fvdlvfvunbwmbcgkbjykdeexifra/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/FirebaseCore.framework':

I made a bit of investigation and found this issue: firebase/firebase-ios-sdk#4087 that refers a problem with CocoaPods: CocoaPods/CocoaPods#8206

It seems that there is a breaking change in Xcode causing both targets to output their files at the same location. The workaround consists in declaring the pods used by both targets explicitly, but after several tries, I didn't manage to find the right combination of pods to declare in Runner and ImageExtension. I'm not even sure it's possible given the fact that Flutter handles the main target dependencies based on the content of pubspec.yml...

Does anyone succeeded in archiving a Flutter app correctly with a Notification Service Extension? If so, I'd be more than happy to take a look at your Podfile!

[AjayrajSingh]

#4522 Kindly help.

[alexanderchmielewski]

Does the Android Foreground Notification has something like an OnClick mechanism?
Original question

[Salakar]

If the application is currently in the foreground, a visible notification is not presented on Android (this is the behaviour of the Firebase Android SDK - you need to subscribe to onMessage and create your own notification using the Flutter Local Notifications package and use that packages API for handling press events.

[alexanderchmielewski]

Thanks for your answer :-)

[fedotxxl]

Hello. I've got an issue with overriding android channel id for background messages - its not working. I've tried:

1. Use meta-data to specify default channel id
2. Send a message without android.notification.channel_id
3. Send a message with android.notification.channel_id

Message banner is not displayed, the default icon is used (banner correctly displayed for foreground messages with flutter_local_notifications plugin).
Finally, I run the example app from the source code, and the banner is still not displayed.

Device: XIAOMI MIUI Global 11.0.2

[fedotxxl]

Tested on a plain Android - works as expected. Not clear why it's not working and Xiaomi. Provided full access to the app

[fedotxxl]

Added displaying notification by flutter_local_notifications in _firebaseMessagingBackgroundHandler - it's correctly displayed on Xiaomi

[GyuriMajercsik]

I tested version ^8.0.0-dev.11 with Flutter web. I received the following error when calling getToken.

Error: [firebase_messaging/failed-service-worker-registration] Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker for scope ('http://localhost:56057/firebase-cloud-messaging-push-scope') with script ('http://localhost:56057/firebase-messaging-sw.js'): The script has an unsupported MIME type ('text/html'). .
    at Object.throw_ [as throw] (http://localhost:56057/dart_sdk.js:5287:11)
    at firebase_messaging_web.FirebaseMessagingWeb.new.getToken (http://localhost:56057/packages/firebase_messaging_web/firebase_messaging_web.dart.lib.js:70:21)
    at getToken.throw (<anonymous>)
    at http://localhost:56057/dart_sdk.js:38536:38
    at _RootZone.runBinary (http://localhost:56057/dart_sdk.js:38392:58)
    at _FutureListener.thenAwait.handleError (http://localhost:56057/dart_sdk.js:33389:48)
    at handleError (http://localhost:56057/dart_sdk.js:33941:51)
    at Function._propagateToListeners (http://localhost:56057/dart_sdk.js:33967:17)
    at _Future.new.[_completeError] (http://localhost:56057/dart_sdk.js:33813:23)
    at async._AsyncCallbackEntry.new.callback (http://localhost:56057/dart_sdk.js:33852:31)
    at Object._microtaskLoop (http://localhost:56057/dart_sdk.js:38645:13)
    at _startMicrotaskLoop (http://localhost:56057/dart_sdk.js:38651:13)
    at http://localhost:56057/dart_sdk.js:34178:9

After quite a while researching on internet, I managed to solve this by adding the following file /web/firebase-messaging-sw.js:

if ('serviceWorker' in navigator) {
  navigator.serviceWorker.register('../firebase-messaging-sw.js')
  .then(function(registration) {
    console.log('Registration successful, scope is:', registration.scope);
  }).catch(function(err) {
    console.log('Service worker registration failed, error:', err);
  });
}

Also, I wonder why multiple Firebase projects are not yet supported like for other plugins:

[Salakar]

Also, I wonder why multiple Firebase projects are not yet supported like for other plugins:

The native SDKs for iOS/macOS/Android don't yet fully support multiple Firebase apps for messaging other than the default app

[GyuriMajercsik]

Also, I wonder why multiple Firebase projects are not yet supported like for other plugins:

The native SDKs for iOS/macOS/Android don't yet fully support multiple Firebase apps for messaging other than the default app

Thanks. Is there any plan to add this in the future ?

[Salakar]

Thanks. Is there any plan to add this in the future ?

Yes, definitely - once it's fully supported by the underlying SDKs we wrap.

[GyuriMajercsik]

Thanks. Is there any plan to add this in the future ?

Yes, definitely - once it's fully supported by the underlying SDKs we wrap.

sorry, I meant if the Firebase team is planning to add this in the underlying SDK's or not...

[yamarkz]

#4521
Not working

[pete-cth]

Hi

I've found the new dev versions much easier to use so far, thanks for all the great work!

I have one issue with data messages not being passed to my background message handler while the Android device is in doze (idle). As soon as the device comes out of doze the handler is called. It looks like it is nearly working as I can see a log message from FLTFireMsgReceiver at the correct time, and the app appears to be briefly given network access again, however the background message handler is not called until later.

I have raised a ticket #4718

Thanks

[NaviWojciech]

Hello! Do you plan to support push notifications on iOS emulator? I believe it's more than expected...

[Salakar]

How would you propose we support it?

[NaviWojciech]

You are this library developers, not me. Previous version somehow worked on iOS simulator... Everything works on Android simulator...

[Salakar]

See #4097 (comment).

[NaviWojciech]

Understood! Thank you for the clarification!

[EgHubs]

Hey, thanks for the great achievement, from your comment, can you explain more how can we achieve custom notification sound, also is there is a duration limit on both ios and android?

[EgHubs]

Thanks for your answer :).I will try that, one more question please, is there is duration limitation in any of IOS or android?

[diegogarciar]

The official iOS docs say 30 seconds.

[afl-dev]

setSound(tone) {
message.android.notification.default_sound = false;

Hi, still not working, what am I doing wrong? 8.0.0-dev.15, thanks

[chen965]

3333

[chen965]

3333

3333

[diegogarciar]

@Salakar I have released my app with the latest messaging-dev release and everything is looking smooth.

[Salakar]

Thank you for the positive feedback 👍

[yosus]

Is it possible to receive notifications sent by APN server (instead of FCM)? My iOS notification works if I send FCM-token to FCM server, but if I send APN-token to APN server, I only get notification without the onMessage called. Any ideas on how to get this to work with APN ?

[diegogarciar]

I believe didReceiveRemoteNotification checks if the notification was originated from FCM before calling OnMessage, if you also want to receive from APNS you would need to override and remove this condition. I can't guarantee you won't break some things by doing this. Maybe you need to create a separate channel for that.

[diegogarciar]

https://github.com/FirebaseExtended/flutterfire/blob/6d21f44dff4b711bff1034202df97a83c60632ba/packages/firebase_messaging/firebase_messaging/ios/Classes/FLTFirebaseMessagingPlugin.m#L286

[aytunch]

@diegogarciar Do you know why they added a condition like that? I have a 3rd party chat service and firebase sending the client push notifications. But in iOS as @yosus stated, the chat service notifications can not be grabbed by Firebase Messaging since they are sent with APNS tokens instead of FCM tokens.

@Salakar It would be really helpful if you could give us developers a way to at least optionally ignore the above mentioned condition. I don't see any reason we should be forced to be limited with FCM tokens with iOS.

[diegogarciar]

Hello @aytunch , sorry for not seeing this before. I'm just a user so I don't know why they have that, I guess they expect certain values that are always present in a Firebase notification. Anyways, that line would not pass using APNS directly, if you're using firebase messaging, that condition should not be a problem.

[RusKryzhanovskiy]

Hi, #5039, can you help me?

[daadu]

@Salakar Since dev channel version (8.X.X-dev.X) is available that works with firebase_core: ^0.7.0, should we correct the docs (https://firebase.flutter.dev/docs/messaging/overview/#1-add-dependency and https://firebase.flutter.dev/docs/migration/#2-update-firebase-plugins) that specifies to use firebase_messaging: "^7.0.3" which does not work with firebase_core: ^0.7.0.

It would be better if the docs are updated, indicating the correct working version.

Related to: #5104 #4786

[daadu]

@Salakar Looks like the docs have been update.

[Purvik]

I'm following guides from here https://firebase.flutter.dev/docs/migration#3-platform-setup to remove all specified firebase packages from dependancies section.
When I run my app on Android device, it is throwing errors as below,

Note: Recompile with -Xlint:deprecation for details.
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/Application.kt: (6, 27): Unresolved reference: firebasemessaging
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/Application.kt: (8, 27): Unresolved reference: firebasemessaging
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/Application.kt: (14, 9): Unresolved reference: FlutterFirebaseMessagingService
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/Application.kt: (20, 13): Unresolved reference: FirebaseMessagingPlugin
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/MainActivity.kt: (23, 21): Expecting ')'
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/MainActivity.kt: (23, 22): Unexpected tokens (use ';' to separate expressions on the same line)
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/MainActivity.kt: (33, 1): Expecting a top level declaration
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/MainActivity.kt: (22, 77): Unresolved reference: CHANNEL
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/MainActivity.kt: (22, 86): None of the following functions can be called with the arguments supplied: 
@UiThread public final fun setMethodCallHandler(@Nullable p0: ((MethodCall, MethodChannel.Result) -> Unit)?): Unit defined in io.flutter.plugin.common.MethodChannel
@UiThread public open fun setMethodCallHandler(@Nullable p0: MethodChannel.MethodCallHandler?): Unit defined in io.flutter.plugin.common.MethodChannel
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/MainActivity.kt: (23, 9): Unresolved reference: call
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/MainActivity.kt: (23, 15): Unresolved reference: result
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/MainActivity.kt: (24, 17): Unresolved reference: call
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/MainActivity.kt: (25, 17): Unresolved reference: result
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/MainActivity.kt: (26, 24): Unresolved reference: call
e: /Users/sunflowerlab/Documents/SFLProjects/BaseProjectFlutter/SflFlutterBaseProject/android/app/src/main/kotlin/com/sfl/is/baseproject/MainActivity.kt: (29, 17): Unresolved reference: result

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDevelopDebugKotlin'.
> Compilation error. See log for more details

[daadu]

The error is about you doing additonal thing in Application.kt and MainActivity.kt

[davidAg9]

I simply wish there was a step by step video of this new version especially for iOS and how to use it to pass data