这可能对遇到此问题的每个人都没有帮助，但这里是满足我们需求的方法...

This may not be helpful to everyone with this problem, but here's what worked for our needs...

我们在开发者控制台中为每个应用创建了新项目，以便每个应用都有自己唯一的推送通知发送者密钥.我们发现所有应用程序都可以具有相同的发送者密钥，只要推送通知服务器(在我们的例子中是 AWS SNS)可以通过另一种方式区分交付目标，我们在设备注册推送时通过捆绑 ID 来实现这一点.最终，我们不需要为每个应用都有独特的项目.

We were creating new projects in the Developers Console for each app so that each would have its own unique sender key for push notifications. What we discovered is that all apps can have the same sender key, as long as the push notification server (AWS SNS in our case) can differentiate the delivery targets by another means, which we're doing by bundle ID when devices register for push. In the end, we didn't need to have unique projects for each app.

它没有回答极限是什么或一旦达到极限如何克服这些问题，但它提供了达到我们所寻求的目的的方法.

It doesn't answer the questions of what the limits are or how to get past them once they've been reached, but it provided the means to the end we were seeking.