Updated an expired certificate but device tokens are set to inactive?

Dear Sir/Madam,

After updating our p12-certificate today, after it has been expired for a few months. I notice that the device tokens of my two devices are set to inactive.

The updated p12-certificate has no different bundle-identifier, so that should not have been an issue. When sending a test message to the selected devices with a tag, the Error console stays empty.

I am at a loss on what to do here...and I could use some pointers.

Kind Regards,

Daniel Dekker

RescueMate

Didn't find what you were looking for?

New post

Comments

8 comments

  • Hi Daniel,

    Can you send over the device IDs for the devices you are using? Can you also confirm that notifications for your devices are turned on at both the app and OS level?

    1
  • Hello Jennifer,

    Thank you for your reply the device tokens are:

    2F45140B79BDC3C6286BE2C89530F646A6E84E31C974F5D5A1A670B4DDBD68EB

    Created 1 year, 3 months ago

    Last Registration 19 hours, 53 minutes ago

    Status Inactive

     

    8DEE8B908613262573A0166355105565DD41472D8D1D2BA92231F489AEE5CAC8

    Created 8 months, 4 weeks ago

    Last Registration 19 hours, 53 minutes ago

    Status Inactive

     

     

    0
  • Hi Daniel,

    It looks like the device tokens are still registering with our system, as their last registration date was yesterday. Were you able to confirm that the devices were opted-in on the app and OS level? How are you handing device registration in your iOS app?

    0
  • Hello Jennifer,

    I register the devices on startup of the app. Just to be sure.

    Both devices have their notifications allowed, this has not been changed in months. Neither has the code of the app.

    The only thing that changed is the new p12 certificate.

    I need to send out some push messages and usually send test messages to myself first to see if everything is still working, because we only send a message once every 3 months.

    0
  • Hi Daniel,

    Thanks for confirming that. Could you let me know which version of our SDK you're running and send the code for how you've set up push registration?

    0
  • Hello Jennifer,

     

    I do not really see how that will solve my issue, since the code has not changed in months and it has been working before the expired certificate...

    0
  • Hi Daniel,

    It's important to know which SDK version you're using and how you've implemented device registration because our best practices change over time and Apple may make updates to their system that are then propagated on our side.

    Once we can confirm that the SDK is up to date and is being implemented properly, we can take a deeper look into whether the certificate might be causing the problem. Normally we see errors in the Error Console when the certificate is the problem though, which is not happening in your case. 

    0
  • Hello Jennifer,

    I now understand the question for the SDK version, i had a really old version still, the Xamarin library was on version 2.2.0, now updated it to the latest version, made the required changes. 

    I now have push messages working again.

    Never imagined that an old version would just be disabled like that. Silly Apple.

    Thank you for your replies and help!

     

    Kind regards,

    Daniel Dekker

    RescueMate BV

    0

Please sign in to leave a comment.