-
Notifications
You must be signed in to change notification settings - Fork 56
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
No keyName specified #41
Comments
Sorry, we have made API changes but it seems perhaps the version you are using is outdated. If you are using the CDN it's possible we've not published the changes to the CDN mistakenly: can you confirm and I will fix shortly when I am back in the office? |
Yep, using the CDN version. Thanks for the quick reply. |
0.8.0 is now on the CDN; sorry for that. |
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After getting back to development after approx 2 weeks, my previously working application now receives the following error when trying to connect with the realtime library:
{"statusCode":401,"code":40101,"message":"No keyName specified"}
This presumably happens on the following line:
new Ably.Realtime({ key: Settings.ABLY_KEY, log: { level: 1 }, clientId: "clientid", transports: ['web_socket']});
Where
Settings.ABLY_KEY
is ofcourse my valid API key.Were there same API changes I am now aware of?
The text was updated successfully, but these errors were encountered: