-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[firebase_messaging 6.0.1] W/FirebaseMessaging(11255): Missing Default Notification Channel metadata in AndroidManifest. Default value will be used. #1478
Comments
Hi @jayvasantjv |
logs from flutter doctor Sorry for limited data in --verbose output since my shell can list only that much data. I hope all the requried details are captured. |
I got same issue even i add meta data in manifest and create strings.xml that contain default channel id still get same error. I use flutter sdk stable version.... |
Any update for this issue..? |
this is a bug in firebase messging plugin .. as they dont provide default notification channel id ..
Next Add this to AndroidManifest file
also define value in string.xml but this did'nt work... Add Same Above in firebase_messaging plugins .. AndroidManifest.xml That worked for me .. |
i already try Missing Default Notification Channell was not appears... |
@ankii9600 onResume and onLoad works on your android device? |
Que debo agregar en el String? |
Describe the bug
During onLaunch & onMessage background messages the following error has been thrown:
W/FirebaseMessaging(11255): Missing Default Notification Channel metadata in AndroidManifest. Default value will be used.
To Reproduce
Steps to reproduce the behavior:
[project]/android/build.gradle file.
and apply plugin to[project]/android/app/build.gradle
.android\app\src\main\java\com\example\appdev\MainActivity.java
androidmanifest.xml
as follows:Expected behavior
The messages for
onMessage
is recieved but, theonResume
andonLaunch
should be called upon receiving notification. Although the error has been thrown.Additional Context
I've referenced for the same from #1478 #88 #343 #1357 , but none seemed to work.
The text was updated successfully, but these errors were encountered: