-
Notifications
You must be signed in to change notification settings - Fork 27
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
Fresh install throws pusher errors #77
Comments
Hi there! That's bizarre, the package should be using the default Pusher keys. On the settings page for the package, do you have any keys registered? |
Yeah i think this is also a problem with moving the settings. You can add the default keys in. You can get to the settings by clicking on the box from the plugin screen the settings are listed below |
I am experiencing this error as well. This error still appears even after I manually add my own Pusher key and secret to the plugin's config file. |
Copied from #78 : Hi there - 2.0.9 should resolve this. I realize that I was only merging the main module with the config options only when the package was activated, meaning you couldn't see them in your settings page pre-activation. It should be fine now, hopefully :/ apologies! |
Thank you for fixing it @jpatel531 |
nice! |
This is fixed for me on Windows.
I don't have access to my Mac until Wed.
Thanks!
|
When you start a new pairing session after a fresh install, you get pusher errors.
First, I installed...
apm install atom-pair
Then opened
atom
Then used the "AtomPair: Start a new pairing session" command
And I got this error
The text was updated successfully, but these errors were encountered: