Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

APNS: does not change the server's address when switch from sandbox to production #33

Closed
monnand opened this issue Sep 13, 2013 · 1 comment
Assignees
Labels
Milestone

Comments

@monnand
Copy link
Member

monnand commented Sep 13, 2013

  1. Put cert.pem and key.pem under some directory, say /top/secret/cert.pem and /top/secret/key.pem, respectively.

  2. Use the following command to add a sandbox provider:

    curl http://127.0.0.1:9898/addpsp -d service=myservice -d pushservicetype=apns -d cert=/top/secret/cert.pem -d key=/top/secret/key.pem -d sandbox=true

  3. Download the production certificate and key. Put them under the exact same path as sandbox certificate/key. i.e. overwrite the sandbox certificate/key

  4. Use the following command to add the production provider:

    curl http://127.0.0.1:9898/addpsp -d service=myservice -d pushservicetype=apns -d cert=/top/secret/cert.pem -d key=/top/secret/key.pem

  5. Now, push message through that provider, the sandbox certificate/key will be used even if it has updated the database.

This bug is discovered through this thread

@ghost ghost assigned monnand Sep 13, 2013
monnand added a commit that referenced this issue Sep 13, 2013
@monnand
Copy link
Member Author

monnand commented Oct 5, 2013

fixed

@monnand monnand closed this as completed Oct 5, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant