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

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

问题描述

我希望将使用推送通知的应用的所有权从一个帐户A转移到帐户B,当我转移捆绑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.

推送通知仍然正常。

我的问题(感谢您阅读到目前为止,当我必须更新城市飞艇中的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?

没有前缀的包ID将是相同的,种子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?

我希望这是有道理的。

非常感谢提前

推荐答案

好吧,对于任何其他人反对这个,只要你不改变捆绑ID你会没事的,推送通知是n受种子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天全站免登陆