Push notifications documentation wrong

[provokateurin]

The documentation about subscribing at the push proxy is wrong. It shows that you have to send a json object as body (https://github.com/nextcloud/notifications/blob/master/docs/push-v2.md#L135), but actually you have to send urlencoded parameters.
This is totally irritating and I put a lot of time into investigating why my library wasn't working.

[nickvergessen]

Just for the record, unless you have a apple/android key from our developer group you can not use the push proxy

[provokateurin]

That means I cannot create an app that gets notifications?

[nickvergessen]

The thing is the push proxy needs to have the apple and android developer certificate so it is allowed to push to those devices. It would work, if you create a valid dev cert and pass it on to us, so we deploy it on the proxy. But as far as I know this would in theory allow us to push releases for your appp to the respective store. But I might be wrong?
Cc @tobiasKaminsky

[tobiasKaminsky]

But as far as I know this would in theory allow us to push releases for your appp to the respective store. But I might be wrong?

This is independent. One is app store and one is firebase (push).

[provokateurin]

Shouldn't this be moved to a separate issue?

[provokateurin]

@nickvergessen @tobiasKaminsky I don't understand why the push proxy code is not opensource, but my solution now is implementing my own push proxy and eventually publishing it. I already get the notifications from the server so I only need to implement the push part. I don't need you to add my certificate to the official push proxy anymore. Thanks anyway

Still this issue isn't resolved so I will create a PR to fix the documentation at some point in the near future.