I tried to send a push notification, but none of them is received. None of the registered device can get notification.
APPLICATION_ID 161CA8CE-7AC3-2596-FF77-73632D3ED600
API_KEY 7ABCB71F-AE97-0E17-FFD6-5943634E8F00
I even tried to send from the console, nothing happen.
Tried channels
userwCF3H4FNrmWQ5IshvmyAGUToDhf2
userSLC99TT5ekhCQZSUrQT6fIioBZh2
userbooUWZwoxNZUuLQuNctPJvu0uMZ2
userlGL4ahlFlxTlEhBuBzeoyHDdS5b2
It was working before lunch, and I come back from lunch, it’s not working.
Nothing has changed on my end.
There’s another question, my table “DeviceRegistion” should have a column channelName, but I can’t see it from the console, but when I tried to create one, it said channelName already exist.
I have the similar problem. I cannot receive notification in my application. It is a working application but as seen in the screenshot, push notification feature suddenly stopped. I got every response after I scheduled or sent the notification but I cannot receive any notifications at all
Hi Vladimir. My App ID is : 706226DA-3A4D-829E-FF92-9733231F4600
Besides, I was using a custom Push Service class. Today, I deleted everything from my app and started the whole implementation process from the beginning as mentioned in the tutorials. I can register the device, get device ID and token and see them in Backendless console. But when I try to send notification from the console! (Not using the API), I cannot receive the message at all. I debug it from my app but it does not step into onMessage() callback.
Thank you for your support by the way. I’ll be waiting your response.
The issue still persist. Already tried to send from android, ios and the console, but no push notification recieved. The column “ChannelName” is still not visible.
I tried sending notification using Backendless console and it worked! I do not have much time right now but I quickly tried to use REST API to send delayed push notification and it did not work. But I will test again for the RESt API tomorrow as soon as possible and write here the results.
It seems to be that your issues are related to the broken schema of your DeviceRegistration table. We’re looking into it and will get back to you with results ASAP.
Mehmet Aktas, I’ve just checked delayed publishing via Android SDK and it’s working on my side. Some additional information required to reproduce the problem.
Has it been working before or you’ve just started integrating push notifications to your project?
Could you please provide the code of how are you scheduling delayed pushes?
It is an active application that is on the market for a while. So I did not integrate push notification recently. I am setting delayed pushes as shown below:
DeliveryOptions deliveryOptions = new DeliveryOptions();
deliveryOptions.setPublishAt(checkDate /* valid java.util.Date object*/ );
List<String> deviceId = new ArrayList<>();
deviceId.add(myDeviceID);
deliveryOptions.setPushSinglecast(deviceId);
PublishOptions publishOptions = new PublishOptions();
HashMap<String, String> headers = new HashMap<>();
headers.put(PublishOptions.ANDROID_TICKER_TEXT_TAG, ticker);
headers.put(PublishOptions.ANDROID_CONTENT_TITLE_TAG, title);
headers.put(PublishOptions.ANDROID_CONTENT_TEXT_TAG, text);
publishOptions.setHeaders(headers);
/*Below code is in AsyncTask*/
MessageStatus publishResponse = Backendless.Messaging.publish( myPushMessage, publishOptions, deliveryOptions );
Could you please check your DeviceRegistration table again? ChannelName should already be there. If not - clear cache and reload the page.
When done - please check messaging functionality for your application again. If the problems will still persist let us know in this topic
