在 iTunesConnect 中所有权转移后推送通知仍然有效 [英] will push notification still work after ownership transfer in iTunesConnect

查看:24
本文介绍了在 iTunesConnect 中所有权转移后推送通知仍然有效的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我希望将使用推送通知的应用的所有权从一个帐户 A 转移到帐户 B,当我转移时,bundle id 保持不变,但种子 id 发生变化.

I am looking to transfer ownership of an app that uses push notifications from one account A to account B, when I transfer the bundle id is maintained but the seed id changes.

我使用城市飞艇处理所有推送通知(效果很好)

I use urban airship to deal with all the push notifications (works really well)

传输时保留捆绑 ID (com.mydomain.myapp).种子是(捆绑 ID 随帐户更改之前的XXYYZZ".

the bundle id is maintained when transferred (com.mydomain.myapp). The seed is (the 'XXYYZZ' before the bundle id changes from account to account.

这似乎不在城市飞艇帐户详细信息的捆绑 ID 中 - 只是 com.mydomain.myapp 位.

This does not seem to be in the bundle id on urban airships account details - just the com.mydomain.myapp bit.

推送通知仍然可以正常工作.

Push notifications still function fine.

我的问题(感谢您阅读到这里)是什么时候我必须更新城市飞艇中的 apns 证书 - 这将必须通过新帐户 B 的个人资料进行更新 - 具有不同的种子 ID,这是否会中断连接在应用当前用户设备和新帐户之间推送 apns?

My question (thanks for reading this far) is when I have to update the apns certificate in urban airship - this will have to be updated through the new account B's profile - which has a different seed id, will this break the connection between the apps current users devices and the new accounts push apns?

没有前缀的bundle id是一样的,seed id前缀对apns ssl证书有影响吗?

The bundle id without the prefix will be the same, does the seed id prefix have any bearing on the apns ssl certificate?

我希望这是有道理的.

非常感谢

推荐答案

好的,对于其他遇到此问题的人,只要您不更改 bundle id 就可以了,推送通知不受种子 id 的影响.

Ok, for anyone else coming up against this as long as you dont change the bundle id you will be fine, push notifications are not affected by the seed id.

这篇关于在 iTunesConnect 中所有权转移后推送通知仍然有效的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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