Error sending HipChat notification: Value cannot be null. Parameter name: HipChat authentication token is not specified.
I'm getting:
Error sending HipChat notification: Value cannot be null.
Parameter name: HipChat authentication token is not
specified.
However, the auth token is specified: http://cl.ly/image/1y3L3B1h3d2o
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Feodor Fitsner on 16 Jun, 2014 06:20 PM
Will take a look.
Support Staff 2 Posted by Feodor Fitsner on 16 Jun, 2014 06:49 PM
Do you use
appveyor.yml
for configuration?3 Posted by byron on 16 Jun, 2014 06:54 PM
No, I don't.
Support Staff 4 Posted by Feodor Fitsner on 16 Jun, 2014 07:04 PM
I mean, you don't have
appveyor.yml
in the repository, right?5 Posted by byron on 16 Jun, 2014 07:05 PM
Correct.
Support Staff 6 Posted by Feodor Fitsner on 16 Jun, 2014 07:07 PM
OK, I'm trying to reproduce the issue.
Support Staff 7 Posted by Feodor Fitsner on 16 Jun, 2014 07:15 PM
Trying to reproduce, but can't... Have you applied changes by clicking "Save" button? What's the name of that project - I'd like to take a look at its settings in database?
8 Posted by byron on 16 Jun, 2014 07:29 PM
I did save the settings. I can also re-open notification settings and see the correct values. That's where the screen shot came from.
The project is called "NovaEnergyFixedForwardPortal"
Support Staff 9 Posted by Feodor Fitsner on 16 Jun, 2014 07:34 PM
Was it a Pull Request build?
Support Staff 10 Posted by Feodor Fitsner on 16 Jun, 2014 07:43 PM
Right, found the issue. Notifications are not being sent when a Pull Request is made.
I'm fixing it right now - will deploy update later today.
11 Posted by byron on 16 Jun, 2014 07:44 PM
Excellent!
Support Staff 12 Posted by Feodor Fitsner on 18 Jun, 2014 04:03 AM
Update has been deployed. Should be working now.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:45 AM.