-
Notifications
You must be signed in to change notification settings - Fork 34
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
Fatal exception when I push notification from Advance REST Client #28
Comments
I have solved the following error by changing the payload and URL to the following : URL : https://android.googleapis.com/gcm/send But now however, another problem arise When I push when my app is opened, I get this empty notification : When I push when my app is closed, I get 2 notifications. 1 is showing the correct text, one is empty, just like the one i got when my app is open In both cases, when my app is closed and is opened, in the log file i am getting the correct data in the callback : Why is the notification come in differently when the app is opened and closed? |
hi @junweimah. Please check the documentation when sending the payload. It seems like a malformed payload. I tried sending notifications both with the app closed and with it opened before the release and they worked. I'll make some other tests just in case |
@progress44 Ok I'll do some changes accordingly. thanks. |
@junweimah anytime. Let me know if it's fixed |
I have checked everything and honestly I am not sure whether it's the payload problem. I pushed using this payload, which is almost the same as the previously try in my second comment in this post:
But now I am getting no notification, but a blank alert in the middle of the screen when the app is opened : For when app is closed, the same still happens, I am getting 2 notifications, one is showing the correct text, one is empty |
Latest update Everything is fixed. There are some problems in my other module and I fixed them. Thanks. |
Fixes a crash that happens when you don't send a `data` object. Stack trace: ``` [INFO] I/ti.goosh.IntentService: Not showing notification cause missing data.alert [ERROR] AndroidRuntime: FATAL EXCEPTION: AsyncTask caffeinalab#5 [ERROR] AndroidRuntime: Process: com.fanhero.floridacup, PID: 32621 [ERROR] AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.google.gson.JsonObject.has(java.lang.String)' on a null object reference [ERROR] AndroidRuntime: at ti.goosh.IntentService.parseNotification(IntentService.java:122) [ERROR] AndroidRuntime: at ti.goosh.IntentService.onMessageReceived(IntentService.java:54) [ERROR] AndroidRuntime: at com.google.android.gms.gcm.GcmListenerService.zzq(Unknown Source) [ERROR] AndroidRuntime: at com.google.android.gms.gcm.GcmListenerService.zzp(Unknown Source) [ERROR] AndroidRuntime: at com.google.android.gms.gcm.GcmListenerService.zzo(Unknown Source) [ERROR] AndroidRuntime: at com.google.android.gms.gcm.GcmListenerService.zza(Unknown Source) [ERROR] AndroidRuntime: at com.google.android.gms.gcm.GcmListenerService$1.run(Unknown Source) [ERROR] AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) [ERROR] AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) [ERROR] AndroidRuntime: at java.lang.Thread.run(Thread.java:818) ```
also had this problem here. Sending the payload with data.data.alert as shown above worked for me as well. This syntax seems really odd... Can you release this soon? |
We kept this syntax to maintain the same data structure with iOS so it will most probably remain the same. |
Yeah definitely |
This is how I pushed it from REST Client
to : https://fcm.googleapis.com/fcm/send
Content-Type: application/json
Authorization:key=my_key
payload : { "data": {
"alert": "Testing",
"title": "This is title test",
"tag":"this is tag",
},
"to" : my_device_token
}
I received the notification on my phone, but my application crashed. This is the log
What is the problem? Thanks
The text was updated successfully, but these errors were encountered: