Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing sandbox APNS on AdHoc Distribution Builds for iOS
    text
    copied!<p>I've been reading a bunch of Apple's docs, as well as many other SO questions, but haven't found the answer to this particular question.</p> <p>I have an existing workflow in place for generating AdHoc Distribution builds for QA members and beta testers. Now that I've added support for push notifications, I'd like those notification paths to be able to be tested as well. </p> <p>I'm under the impression that Developer builds, signed with a Development provisioning profile, generate tokens that for the sandbox/development APNS environment, and Distribution builds, signed with a Distribution provisioning profile (whether that be destined for AdHoc Distribution OR AppStore Distribution), generate tokens for the production APNS environment. I believe this can be confirmed by opening the different .mobileprovision files, and examining the <strong>aps-environment</strong> key.</p> <p>I'd like to know if there's a way to have my AdHoc Distribution builds use the sandbox APNS environment, rather than the production APNS environment. </p> <p>If I really wanted QA and beta testers to use sandbox APNS, would I have to somehow find a way to allow them to run development builds, rather than distribution builds?</p> <p>Or are my assumptions about the way things work way off base? (referenced <a href="https://stackoverflow.com/questions/1943722/iphone-apns-device-tokens-in-sandbox-vs-production/2261758#2261758">this post</a> and <a href="https://stackoverflow.com/questions/2625773/why-not-use-development-provisioning-instead-of-ad-hoc">this post</a>)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload