Hi,

I am seeing this as the result field on the PushMessage callback.

Does this indicate it worked or not?

{"pushedTo":{"kid":"kid_VTagZneFqE"},"rawResults":{}}

 Nothing is sent to my phone.

Gary

Hi Gary,

Can you please try following couple of things:

1. Unregister and register again for push notifications from your phone
2. Send a test push notification from Kinvey Console
   

Meanwhile, I will find you necessary documentation on PushMessage callback.

Regards,

Wani

{
  "pushTokens": [
    {
      "token": "808b2cc50dafda2d008107bd3d2114386b5b65cb4a40d362ba592b4791808fe7",
      "platform": "ios",
      "arn": "arn:aws:sns:us-east-1:853461911189:endpoint/APNS_SANDBOX/kid_Wkdx_osbwe_development/371eb3ac-30d0-378e-afe1-1536999c6f66"
    }
  ]
}

 When I send a push from the Engagement page I get 202 Accepted

What does that mean, why not 200?

Nothing shows up on the iPad.  Not in the app nor in the Notificatuions area.

Now what?

Gary

Hi Gary,

The push field looks normal to me.

Can you share following couple of items to give me a better idea:

1. A timeline of events related to push functionality (when it started working, stopped working, issues faced, different things tried etc.)
2. Your code relevant to push functionality (registration, receiving notifications etc.)
3. Kinvey app id
4. SDK version

Hi.

1. For the test app I created last night it has never worked.  For our three production apps it stopped about 2-3 months ago.  For the production apps we tried re-uploading the certificates, that didn't help. We tired altering the business logic code as instructed, that helped temporally but crippled out app and then finally quite working.  For the app I created last night everything is new and newly uploaded.

2. We are using a built in control in Embarcadero's Rad Studio. I can try to capture the REST commands sent if that would help.  However, you indicated the registration is working correctly.  The reception when the app is closed is handled by iOS and should appear in the Notifications area.  It does for other apps, such as Mercat.  This is using iOS 9.0.0

3. The app name is pushtest2.  The App Key is kid_Wkdx_osbwe.  I am not sure what you mean by app id?

4. API version is 3

By the way, this is affecting all of our apps and on multiple different phones, and both Android and iOS.

Gary

Hello Gary,

At this time can you re-upload your APNS certificate to your application?  Please let us know when you complete this step.

If you could add support@kinvey.com to your environment I would be happy to ensure that the migration goes smoothly from here on out.

Thanks,

 Hi,

I found the problem with the Android side.  It was an error in the Manifest File.

I re-uploaded the Apple certificate.  It didn't give me an error, but it didn't give me a confirmation either.

The iOS still doesn't work.

You have the login information

It is a production certificate because that is the way RadStudio does things with Ad-Hoc builds.

Gary

Gary,

Can you email me about this?  Damien@kinvey.com -- and add me a collaborator.

Thanks,

Hello Damien,

I re-uploaded my APNS Certificate but our users don't get any push at all.

When I used the Console to test the service I got a 202 success but devices got no push notifications.

Would you mind ensuring migration was successful?

Cheers,

Aris

 Hi Aris,

Nice to know someone else is having the same problems I am.

That tends to assure me that it's not my app.

One thing, right now I am not able to successfully upload certificates.  Kinvey keeps saying it can't validate them.  I have tried with both Firefox and Safari.

Gary

 Hi Gray,

Can you please try re-uploading your APNS certificate (which is a .p12 file) to the Kinvey console using Safari / Chrome browser. This could solve your problem.

Thanks,

Jagan

Gary