-
Notifications
You must be signed in to change notification settings - Fork 2
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
Services setup guide? #29
Comments
Update: tested and working! :)
Does this work? |
That didn't work for Instapush, but it worked for Pushbullet. |
Just had chance to refresh my memory. If you enter a valid user token, Snarl should create an application within Instapush which it will then use for notifications. Can you check your Instapush dashboard to see if it's managed to do that? I will rework the service to require |
I've uploaded a special Beta 3 release here: https://sourceforge.net/projects/snarlwin/files/Snarl/R5/ Can you test it out? I've changed the way the Instapush redirect works so now you need to create the app and events you want within Instapush itself. To configure Snarl, create a new Instapush scheme (this beta will ignore any existing schemes you have created, sorry), enter the Snarl currently exports the following trackers:
All should be pretty self-explanatory. If any are null, the redirect will send a single space to prevent Instapush from complaining about a missing tracker. Let me know if you'd like other trackers exporting and I'll see what I can do. Hope this all makes sense! 😀 |
Yeah, when using my user token, Snarl never managed to create an app inside Instapush. Is there something specific I need to do on the Snarl side to get it to register, or just send a test notification? |
How are you testing notifications using the special Beta 3? Could you share the app id and secret and I'll run a test myself? chris.gsi(at)fullphat.net |
Would it be possible to get setup guides for Services? I'm primarily interested in Instapush. I can't seem to connect Snarl R5 beta 2 to my Instapush account.
The text was updated successfully, but these errors were encountered: