-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
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
Connection issues #20
Comments
This is fixed: we support
I've added tests for the string-only cases for realtime and rest |
No tests to prevent a regression? |
Also, is this deployed so I can retry the JSBin? |
I added tests, as stated above |
Not yet |
Can't see any tests in the commit you sent? Given 3 out of 4 were failing, should we not add coverage to all? Can you deploy please so that we can test this + the other auth issue in production and then in CI for the web server? |
2 were failing (tests above), 1 was being used incorrectly ( |
Ah, great, shout when this and other fixes are deployed so that we can test. |
Unfortunately there is another bug, if you pass in an API key without the form |
This should fix it: c458536 |
I see that's tagged 0.7.5, is that deployed? |
Yes
|
Resolved |
Thanks |
@paddybyers I am a bit confused why http://jsbin.com/vuvozisape/1/edit?js,console,output is not working.
Seemingly it will only connect when using the format
Ably.Realtime({ key: "key" })
, and all other key & token formats fail for different reasons.I also thought we had changed our libraries to support the use of a a key or token string in place of the constructor options which too doesn't seem to be working.
Can we ensure we add test coverage to this once resolved?
The text was updated successfully, but these errors were encountered: