You can try to send it, in the database is only one iOS device - and this is the test device, no problem sending push notification to this device.
And i have only one PUSH Setting in the Appery.io environment
You can try to send it, in the database is only one iOS device - and this is the test device, no problem sending push notification to this device.
And i have only one PUSH Setting in the Appery.io environment
What has the Release Checkbox on the "Application Settings\iOS Binary" to do?
this is checked at the moment
but the certificate (.p12) file for the PUSH Notification is for Development ....
Can this be the problem?
Please try to delete edited (blue colored file) and Undo all source changes, then test again.
hmmmmm
i just deleted the blue colored file ... but now i can't compile the ipa file again? i get an build error (without any description)
How do i get this file back again?
oh i just found the "undo all source change" - now i got the original ".plist" file
The .ipa was successfully build
But the same problem - i can't send push to the iOS Device - same error "that no password is set"
For testing i just deleted the certificate - and i still get the same error (that the password is not set) - but now i havn't a certificate at all???
You will need a valid provisioning profile file for Push and and appropriate certificate file.
I know it, but regardless what i do, i get everytime the error that no password is set.
I have downloaded the .cer file from apple, and transformed it into a .p12 file (the same way i did it for the Distribution certificate in iOS Binary)
entered the password and saved it
build a new .IPA file - and tried to send a push notification from https://appery.io/push/a1xxxxxxxxxxxx...
but i still get the error ![]()
Is it possible to get an additional error code or so?
Because the error that the "certificate password is not set" is definitive wrong ...
I don't know what to do ... or rom where the app is getting the certificate password?
maybe an other place - i don't know it ....
Hello! I'll pass this problem to developers team so they can check. Sorry for inconvenience.