Sickchill: ISSUE: Join notifications now require the apikey parameter to send push notifications

[heymoe]

I started to receiver the following messages from Join when SR sends out a notification:

"All Join API pushes now REQUIRE the API Key parameter. Please go to https://joaoapps.com/join/web and regenerate your API URL with the apikey parameter"

Join's API docs: https://joaoapps.com/join/api/

[SickRage2]

Thanks for the issue report! Before a real human comes by, please make sure your report has all the below criteria checked

• [ ] Include basic information: Branch/Commit, OS, What you did, What happened, What you expected
• [ ] Enable debug logging (be sure to disable after the bug is fixed)
• [ ] Post debug logs, either inline (for smaller logs) or using gist

Please make sure you also read how to create an issue and followed all of the steps.

The title should describe your issue. Having "SR not working" or "I get this bug" for 100 issues, isn't really helpful. We will close issues if there isn't enough information.

Sometimes the devs may seem like grunts and respond with short answers. This isn't (always) because the dev hates you, but because he's on mobile or busy fixing bugs. If something isn't clear, please let us know, and this bot may get updated to automatically answer you.

Thanks!

[heymoe]

In case you really need it for this report:

SickRage Info:
Branch: master
Commit: 949e0acc613e8cc14c7555a3f154f031a94a9768
Database Version: 44.0
Python Version: 2.7.13 (default, Dec 21 2016, 07:16:46) [GCC 6.2.1 20160830]
SSL Version: OpenSSL 1.0.2k 26 Jan 2017
OS: Linux-4.10.2-1-ARCH-x86_64-with-glibc2.2.5
Locale: en_US.UTF-8

[sharkykh]

Just to be sure, you still need to have the device ID, just add the api key, correct?
And also - I will add the link to create an API.

[heymoe]

It's my understanding you need to add the apikey to the URL you're already using keeping the list of devices id to send the push to in it.

[sharkykh]

Fixed in develop branch.

[heymoe]

Just updated and tested.. Looks like it's working again. Thanks!