Bluemix Push Notification服务不再工作了? [英] Bluemix Push Notification service not working anymore?

查看:120
本文介绍了Bluemix Push Notification服务不再工作了?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个原生的iOS Swift应用程序与一个 Node.js Bluemix 后端与MobileFirst服务(AMA,Cloudant,推送iOS 8)交谈,该服务适用于月。几天前,我注意到我无法再从iOS应用程序注册新设备(IMFPushClient.sharedInstance()。registerDeviceToken()以404响应。



我知道最近对MobileFirst服务进行了更改(例如各种推送服务合并为一个),所以我想我应该重新绑定这些服务。这解决了注册问题,但从那时起我就无法收到推送通知。



这就是我尝试的方法:




  • 已创建使用MobileFirst服务初学者样板
  • $ b $的全新后端b
  • 克隆最新版本的 Bluelist 示例应用已配置此新后端

  • 已发布我的捆绑包ID的新 APN 证书并将其上传到推送服务

  • 已成功注册,可在我的设备上发送推送通知。我通过调用/ devices



    在这里您可以看到您上传的.p12文件的证书类型。确保您使用的是Sandbox环境,它将被列为Sandbox。生产环境也是如此。


    I have a native iOS Swift app talking to a Node.js Bluemix backend with MobileFirst services (AMA, Cloudant, Push iOS 8), which worked well for over a month. A few days ago I noticed that I could no longer register new devices from the iOS app (IMFPushClient.sharedInstance().registerDeviceToken() responded with a 404).

    I knew that changes had been made recently to the MobileFirst services (e.g. the various push services were merged into one), so I figured I should rebind those services. This resolved the registration issue, but I haven't been able to receive push notifications ever since.

    This is what I tried:

    • created a completely new backend with the "MobileFirst Services Starter" boilerplate
    • cloned the most recent version of the "Bluelist" sample app and configured it for this new backend
    • issued a new APNs certificate for my bundle ID and uploaded it to the push service
    • successfully registered for push notifications on my device. I have verified this by calling the /devices REST API (essentially, I followed these steps).

    Now every time I use the REST API to send messages (after figuring out that the bearer token approach was replaced with a new "appSecret" header), I get an HTTP 202, but the notification never arrives. Likewise, when I try to send the message through the service's dashboard, I get a success message, but the notification never arrives.

    One thing I noted is that the symptoms stay the same even if I don't provide the .p12 certificate to the service, so I wonder if this might be some certificate issue, but I have no idea how to trace this. Also, IIRC the "old" MobileFirst services required me to provide the bundle ID and version of the mobile app, but this seems to be gone now. Any help is greatly appreciated.

    解决方案

    We were able to solve the issue above by making sure the sandbox environment was using a sandbox .p12 file. To verify this setting go to the IBM Push Notification Dashboard and click the Configuration tab:

    Here you can see the Certificate Type of the .p12 file you have uploaded. Make sure if you are using the Sandbox environment it is listed as Sandbox. Same is true for the Production environment.

    这篇关于Bluemix Push Notification服务不再工作了?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆