- Forum posts: 6
May 24, 2019, 3:47:07 PM via Website
May 24, 2019 3:47:07 PM via Website
Hey Guys!
i have an app that i implemented fcm from a tutorial (AndroidHive)
its cause it works with the fcm web site test section to send messages
i get this:
2019-05-24 09:37:26.389 23610-23731/com.media.box.winner W/FirebaseMessaging: Missing Default Notification Channel metadata in AndroidManifest. Default value will be used.
2019-05-24 09:37:26.403 23610-23731/com.media.box.winner W/Notification: Use of stream types is deprecated for operations other than volume control
2019-05-24 09:37:26.403 23610-23731/com.media.box.winner W/Notification: See the documentation of setSound() for what to use instead with android.media.AudioAttributes to qualify your playback use case
2019-05-24 09:37:26.412 23610-23666/com.media.box.winner D/FA: Logging event (FE): notification_receive(_nr), Bundle[{firebase_event_origin(_o)=fcm, message_device_time(_ndt)=0, message_name(_nmn)=test, message_time(_nmt)=1558705046, message_id(_nmid)=1010204384068189970}]
2019-05-24 09:37:26.474 23610-23666/com.media.box.winner V/FA: Connecting to remote service
2019-05-24 09:37:26.515 23610-23666/com.media.box.winner D/FA: Connected to remote service
2019-05-24 09:37:26.520 23610-23666/com.media.box.winner V/FA: Processing queued up service tasks: 1
2019-05-24 09:37:31.563 23610-23666/com.media.box.winner V/FA: Inactivity, disconnecting from the service
i also have a web PHP script that i use to send Notifications and in this one it works also but does not notify? i see that the app got the information:
2019-05-24 09:38:26.717 23610-24021/com.media.box.winner E/MyFirebaseMessagingService: From: 352312559305
2019-05-24 09:38:26.719 23610-24021/com.media.box.winner E/MyFirebaseMessagingService: Data Payload: {data={"image":"http:\/\/api.androidhive.info\/images\/minion.jpg","is_background":true,"payload":{"score":"5.6","team":"India"},"title":"iptv web player","message":"dddd","timestamp":"2019-05-24 13:38:26"}}
2019-05-24 09:38:26.719 23610-24021/com.media.box.winner I/System.out: Data Payload: {data={"image":"http:\/\/ .
api.androidhive.info\/images\/minion.jpg","is_background":true,"payload":{"score":"5.6","team":"India"},"title":"iptv web player","message":"dddd","timestamp":"2019-05-24 13:38:26"}}
2019-05-24 09:38:26.729 23610-24021/com.media.box.winner E/MyFirebaseMessagingService: push json: {"data":{"image":"http:\/\/api.androidhive.info\/images\/minion.jpg","is_background":true,"payload":{"score":"5.6","team":"India"},"title":"iptv web player","message":"dddd","timestamp":"2019-05-24 13:38:26"}}
2019-05-24 09:38:26.730 23610-24021/com.media.box.winner E/MyFirebaseMessagingService: title: test
2019-05-24 09:38:26.730 23610-24021/com.media.box.winner E/MyFirebaseMessagingService: message: dddd
2019-05-24 09:38:26.730 23610-24021/com.media.box.winner E/MyFirebaseMessagingService: isBackground: true
2019-05-24 09:38:26.731 23610-24021/com.media.box.winner E/MyFirebaseMessagingService: payload: {"score":"5.6","team":"Mike"}
2019-05-24 09:38:26.731 23610-24021/com.media.box.winner E/MyFirebaseMessagingService: imageUrl: http: // . api.androidhive.info/images/minion.jpg
2019-05-24 09:38:26.731 23610-24021/com.media.box.winner E/MyFirebaseMessagingService: timestamp: 2019-05-24 13:38:26
2019-05-24 09:38:27.514 23610-24021/com.media.box.winner D/skia: --- Failed to create image decoder with message 'unimplemented'
2019-05-24 09:38:27.587 23610-24021/com.media.box.winner W/Notification: Use of stream types is deprecated for operations other than volume control
2019-05-24 09:38:27.587 23610-24021/com.media.box.winner W/Notification: See the documentation of setSound() for what to use instead with and
Why do i get a different result with one that does not show the debug info but works and the other shows the debug info but does not notify?
Recommended editorial content
With your consent, external content is loaded here.
By clicking on the button above, you agree that external content may be displayed to you. Personal data may be transmitted to third-party providers in the process. You can find more information about this in our Privacy Policy.