Push notifications are broken - IOS

Hello, Backendless support team
APP ID : 6BB8FB6D-7BEA-2244-FF30-A3C649DEB100
currently from few days we are facing problem with push notification. Before it was working we have uploaded the new certificates with password.
from application after sending push we are getting messageId and status as scheduled. and in backendless we can see notifications Pub/Sub traffic monitor under message tab.
we have checked the device token in device list. Device token are same.
Looking forward for positive response, because the application is on App store and notifications are not working…

Hi.
We have checked this functionality right now and all work fine.
Please, try to remove all certificates from backendless and upload it again.

Did you have any error during certificate uploading or sending messages?
Did you make all steps without mistakes when create certificate (see instruction below)?
https://backendless.com/docs/ios/doc.html#messaging_push_notification_setup_ios

Hello, Support Team

i have gone through the link and here is the steps we followed and output we are getting plz find the attachments i have attached screen shot…

— I have reset the certificates.

— while creating user we are taking the device token and registering the device for message service.

DeviceToken : Printing description of deviceToken:

<3ed08657 0828ee10 902a19b7 60c449fd ac1ce079 9ecc10a2 65194819 98205808>

[backendless.messagingService registerDeviceToken:deviceToken response:^(NSString *result)

{

//In result we are getting the result

Printing description of result:

4FB82639-B21B-12A2-FF9D-1A064CC93D00

} error:^(Fault *fault) {

//we are not getting error while registering the device.

}}];

after registering [backendless.messagingService currentDevice] we are getting the deviceId

in backendless developer console we got this device and token in channel plz look at the attached Image

— while sending the push

[backendless.messagingService

publish:@“default” message:[pushData valueForKey:@“alert”] publishOptions:publishOptions deliveryOptions:deliveryOptions

response:^(MessageStatus *messageStatus)

{

NSLog(@“MessageStatus = %@ <%@>”, messageStatus.messageId, messageStatus.status);

}

error:^(Fault *fault)

{

NSLog(@“FAULT = %@”, fault);

}];

as a result we are getting:

MessageStatus = C065CFD0-E3B0-6FC6-FF98-41B945FC0600 <SCHEDULED>

MessageStatus = D6551805-3B01-CF53-FFF7-EA01F40B2F00 <SCHEDULED>

MessageStatus = 58F9E02B-193B-4F28-FFAB-7796EBE38C00 <SCHEDULED>

MessageStatus = FECFDDAB-2271-98BE-FFCA-5ED7154A6400 <SCHEDULED>

MessageStatus = 147F1B59-5E97-5F48-FF21-BDF61A9F0700 <SCHEDULED>

MessageStatus = 778E4590-E919-8470-FF0B-7C9ADF570000 <SCHEDULED>

MessageStatus = AE97CFAF-7C03-2757-FF8F-3BB944C4D600 <SCHEDULED>

MessageStatus = DAA43A75-E6D0-2283-FFE8-37795EA33500 <SCHEDULED>

MessageStatus = 47B29F19-2737-96D6-FFAD-FB040684BE00 <SCHEDULED>

MessageStatus = 990039A6-0BC9-32C6-FF31-FD52926CB400 <SCHEDULED>

MessageStatus = 256C52A6-AE9C-F357-FF72-F79603FBAB00 <SCHEDULED>

MessageStatus = B3D70514-B7D7-30B7-FFB0-A0698EE2A700 <SCHEDULED>

— Pub/Sub Traffic monitor i can see the message and it disappear after few seconds i have attached the screenshot…

Thanks for additional infromation.
We’ve created inner task (BKNDLSS-14499) to deeper investigate this problem.

Hello, After publishing push in terminal im getting response

curl -H application-id:6BB8FB6D-7BEA-2244-FF30-A3C649DEB100 -H secret-key:3FAF5834-EC24-1BC5-FF48-AFA49385F500 -H application-type:REST -H Content-Type:application/json -x GET -v https://api.backendless.com/v1/messaging/A91ECF2A-7F07-19B7-FF70-1324B2CEA700

  • Could not resolve proxy: GET

  • Closing connection 0

curl: (5) Could not resolve proxy: GET

you are using wrong arguments in curl should be “-X GET” instead of “-x GET”

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff}
span.s1 {font-variant-ligatures: no-common-ligatures}

TechnoMac-5:~ technomac-5$ curl -H application-id:6BB8FB6D-7BEA-2244-FF30-A3C649DEB100 -H secret-key:3FAF5834-EC24-1BC5-FF48-AFA49385F500 -H application-type:REST -H Content-Type:application/json -X GET -v https://api.backendless.com/v1/messaging/B19BB0C4-A817-117D-FF37-8F05F6B62800

Note: Unnecessary use of -X or --request, GET is already inferred.

  • Trying 149.56.79.124…

  • Connected to api.backendless.com (149.56.79.124) port 443 (#0)

  • TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

  • Server certificate: *.backendless.com

  • Server certificate: COMODO RSA Domain Validation Secure Server CA

  • Server certificate: COMODO RSA Certification Authority

  • Server certificate: AddTrust External CA Root

GET /v1/messaging/B19BB0C4-A817-117D-FF37-8F05F6B62800 HTTP/1.1

Host: api.backendless.com

User-Agent: curl/7.49.1

Accept: /

application-id:6BB8FB6D-7BEA-2244-FF30-A3C649DEB100

secret-key:3FAF5834-EC24-1BC5-FF48-AFA49385F500

application-type:REST

Content-Type:application/json

< HTTP/1.1 200 OK

< Server: nginx/1.8.1

< Date: Mon, 24 Apr 2017 11:56:59 GMT

< Content-Type: application/json; charset=utf-8

< Content-Length: 179

< Connection: keep-alive

< Access-Control-Allow-Headers: Origin, application-id, application-type, Content-Type, secret-key, request, user-token

< Access-Control-Allow-Methods: POST, GET, OPTIONS, PUT, DELETE, PATCH

< Access-Control-Allow-Origin: *

< Expires: Thu, 01 Jan 1970 00:00:01 GMT

< Cache-Control: no-cache

< Cache-Control:: no-store, no-cache, must-revalidate, private

< Pragma:: no-cache

<

{“errorMessage”:“javax.net.ssl.SSLException: Received fatal alert: internal_error. Check your certificate.\n”,“messageId”:“B19BB0C4-A817-117D-FF37-8F05F6B62800”,“status”:“failed”}

NOTE: we have created new certificates and uploaded on backendless.

have you provided correct password?

yes certificates are few days old and password is correct…

Hello, I have checked it with code generated project, and it works. I have used developer certificate.

We have checked the password and created a new certificates, install it and still getting the same error. Can you please look into it ? We have tried all the possible ways we can do it.

Hello!

What version of Backendless are you using? What certificates are you using (production or developer)?

Regards,
Olga

We are using backendless v3 with a production certificate.

  1. Have you changed your Xcode project build configuration from development to production?
  2. Have you exported your app for Ad Hoc Deployment to check it with the production certificate?

Yes we have checked both.

How do you create the provisioning profile? Could you describe every step in detail? I suspect you’re using a provisioning profile pointing to the sandbox environment. As a result, there is a mismatch between the profile and the certificate.

We already have a this app live on the app store so we don’t think it’s a profile issue.

Well, if you try to verify it locally in your Xcode and the app is in the app store, you will not be able to for the following reason: the certificate on the backend is for Production. When you run it in Xcode, you’d be using development provisioning profile, which works only with Sandbox certificate.

So my question is - how do you verify that it is not working?

Hi!

Could you please say, what message status returns after executing this code from the terminal?

curl -H application-id:YOUR-APP-ID -H secret-key:REST-SECRET-KEY -H application-type: REST -H Content-Type:application/json -X GET -v [url=https://api.backendless.com/v1/messaging/YOUR-MESSAGE-ID]https://api.backendless.com/v1/messaging/YOUR-MESSAGE-ID[/url]

Hello,
I’ve checked this issue once again, and everything works fine with development and production certificates for v3 and v4. If your message status is “published” please check if your app bundle id matches your certificate bundle id and push notifications for this app are allowed on the device.

Regards, Olga