We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Put cert.pem and key.pem under some directory, say /top/secret/cert.pem and /top/secret/key.pem, respectively.
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
Download the production certificate and key. Put them under the exact same path as sandbox certificate/key. i.e. overwrite the sandbox certificate/key
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
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
The text was updated successfully, but these errors were encountered:
fixing #33
c556ed9
fixed
Sorry, something went wrong.
monnand
No branches or pull requests
Put cert.pem and key.pem under some directory, say /top/secret/cert.pem and /top/secret/key.pem, respectively.
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
Download the production certificate and key. Put them under the exact same path as sandbox certificate/key. i.e. overwrite the sandbox certificate/key
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
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
The text was updated successfully, but these errors were encountered: