There is no official APNs documentation specifically for handling separate targets within same project, because APNs has nothing to do with your project / target set up.
As you can read in Setting Up a Remote Notification Server,
The delivery of remote notifications involves several key components:
- Your company's server (known as the provider server)
- Apple Push Notification service (APNs)
- The user's device
- Your app (running on the user's device).
Each item in above list is identified by
- Apple Push Notification service (production, or sandbox/development): the url you use to trigger APNs from you server
- User's device: device token your app gets when it registers for remote notification
- Your app (running on the user's device): bundle id, and provisioning profile (dev/appstore/adhoc/inhouse) you use to run the app
- Your company's server: APNs certificate you create, in dev portal for you bundle id (mentioned above), and use to trigger remote notifications to a particular device
As you can see there is not restriction on which server can trigger which remote notification, or how the app code, project, or targets are set up.
A single server (or even a developer machine, from command line using curl
), can trigger push notifications, for all the right combinations of above conditions. It is up to you to make sure you use the correct certificate for the correct version of the app. e.g. if you use the InHouse app's APNs certificate with an AppStore app's device token it will fail, etc.
Many developers (including myself) have triggered push notification from command line, to multiple versions of the same app, with separate targets and it works.