How can this be an issue from our side? My device is not having any push notification issues from other applications. The issue exists only when the push notification is sent from backendless side. Also this is not a certificate issue. All the devices whose version is below 13 are receiving the push notifications. Also this is not a code related issue. I tested the push notification in your code generated project and still my device didn’t receive the notifications.If this was an issue in our project, then my device should have received the push notifications when i tested in your code generated project. So this is not an issue because of my device, certificate or the project.
When you send a push notification you receive a message status of that message. Could you please provide that status info?
Message Id : B448132B-08BE-4CBB-A29C-336AE0F25E7F
Status : SCHEDULED
Error Message : nil
Please see the screenshot below:
@Kevin_McClain when you send the message, the server always return the result as SCHEDULED because push notification is async job on the server. So to get the status you should follow the doc Get Message Status - Backendless REST API Documentation
I was not able to find the method for swift or ios, and not sure that is is present, all message with prefix in your case is:
message:B448132B-08BE-4CBB-A29C-336AE0F25E7F
and use curl to get the status. If you receive SCHEDULED then server still process the message and you should call getMessageStatus one more time with the same message id
Both iOS-SDK and Swift-SDK have this method getMessageStatus in Messaging Service.
This is the code used to get the message status after sending the push notification
MessageStatus *result = [backendless.messagingService publish:@"default" message:message
publishOptions:publishOptions deliveryOptions:deliveryOptions];
NSLog(@"MessageStatus = %@ <%@>", result.messageId, result.status)After you received MessageStatus *result you should call
MessageStatus *info = [backendless.messaging getMessageStatus:result.messageId];
and provide what does the info says about status - messageId, errorMessage and status.
I called the getMessageStatus method and result is as shown below:
status : UNKNOWN
message iD: BDB68D6C-8DAE-4D50-BBE1-6863154DB8EF2
Well,
the only thing a see right now is to ask to add me to your team in Apple Development Program.
I want to create an empty app with only my and yours device registered there.
and use your certificate in my test project (that’s why I ask about adding me to your team).
If it will work fine, I’ll share his test project with you to check it with yours device.
Unfortunately I don’t see the the other way right now - I can’t reproduce even this issue with status and receive
"errorMessage":null,"messageId":"message:3157B723-E94E-42FA-92CF-76B76A56ED43","status":"published"
Please let me know if its possible to connect me to your team and use your certificate in my project.
Okay .Please send me your email id so that I can add you to the apple developer team.
Please provide me a provisioning profile and .p12 certificate to use in tests.
Thank you
okay . I have added you to our Apple Developer program and have sent you the required certificates and profiles to your email id.
1 Like
Ah, google decided to block my new account and I have no idea why.
I can convert my mbox archive to accept your invitation, thank you!
Not to wait until Google restores my mail, could you please resend me the attachments on my main address olga@themidnightcoders.com or send them as direct message here?
Sorry for inconvenience.
I have tested the push notifications in your project and my device is receiving push notifications. But when i use my certificate , my device is not receiving push notifications. Can you please test push notifications in your device in production mode using my certificate. I have shared the certificate to you by email.
@Kevin_McClain, we have already gone above and beyond with this issue. What you’re asking now is outside of the support charter. We have done numerous validations to make sure the problem is not with Backendless. If you would like us to further assist you with this issue, we can do it on the consulting services basis. Please feel free to reach out to sales@backendless.com to discuss the options.
Regards,
Mark
I want to add that I couldn’t check prod pushes with your certificate because I have no access with distribution profile.
But I’ve checked our production certificate once more and it works fine with iOS 12 and 13, with both Backendless and NWPusher.
For the moment we don’t have any issues on our side, all certificates work correctly and I can receive pushes with production certificate as well as with sandbox.
Please make sure you’re using the correct provisioning profile, and your Xcode project configured correctly in the release mode.