Custom url callback scheme

[dcburke1]

Hello,

Would it be possible to allow the use of a custom scheme?

(i.e.) instead of http://, https://, file:// etc.  I'd like to use overwolf-extension://  Currenlty, overwolf-extension:// does not validate when I attempt to use it as a redirect URL in my application's settings.

For reference: http://developers.overwolf.com/url-based-api/ 

For context:  I have a treadmill desk at home that I love to use and I regularly use my fitbit while walking.  What I want is for an application that will show current steps (updated every 30-60 seconds), maybe a progress bar to daily goal, etc. while playing a pc game, watching netflix, etc via the Overwolf overlay.

Thanks!

[JeremiahFitbit]

This is supported with OAuth 2.0.

[dcburke1]

Is there another way to register it besides using this form? Below is the error that I get when I try to register the URL that I want to use:

[JeremiahFitbit · Accepted solution]

This appears to be a bug. Thanks for finding it!

The form validation is not following RFC 2396's rules for scheme, specifically regarding the hyphen. We will get this fixed in the next few weeks.

[dcburke1]

Hey, no problem!  I'm glad to know that it was just a bug and that I'll be able to make this soon, thanks!

[Michael]

---

@dcburke1 wrote:
For context:  I have a treadmill desk at home that I love to use and I regularly use my fitbit while walking.  What I want is for an application that will show current steps (updated every 30-60 seconds), maybe a progress bar to daily goal, etc. while playing a pc game, watching netflix, etc via the Overwolf overlay.

---

@dcburke1 I just thought I would add that you aren't likely to get updates every 30-60 seconds, as Fitbit normally syncs once every ~15 minutes. (Unless you go trigger a forced sync through the "Sync Now" process.)

[dcburke1]

---

@Michael wrote:

---

@dcburke1 I just thought I would add that you aren't likely to get updates every 30-60 seconds, as Fitbit normally syncs once every ~15 minutes. (Unless you go trigger a forced sync through the "Sync Now" process.)

---

@Michael That would be an issue, but I was thinking that the All-Day Sync feature on my iPhone would get me more rapid updates (with the app closed or in background on my phone, but my phone near me).  Maybe I misunderstand how the All-Day Sync works...

Even if it is only every 15 minutes, that's rapid enough for my purposes. It does sort of lose a bit of the "ooo" factor that way though.

Thanks for the heads-up! 🙂

[lukas444]

Any progress with it?

[Doug]

---

@dcburke1 wrote:

@Michael That would be an issue, but I was thinking that the All-Day Sync feature on my iPhone would get me more rapid updates (with the app closed or in background on my phone, but my phone near me).  Maybe I misunderstand how the All-Day Sync works...

Even if it is only every 15 minutes, that's rapid enough for my purposes. It does sort of lose a bit of the "ooo" factor that way though.

Thanks for the heads-up! 🙂

---

All-Day sync means the mobile device will sync about every 15 minutes, even if not the foreground app, provided of course there is an internet connection (carrier or wi-fi).  Without it on, the mobile device will try to sync when you bring the app to the foreground (if it has been over 15 minutes?) or whenever you tap the "Sync Now" option on the device page.

But you should just be able to leave the app open on the dashboard and see real-time numbers change as you walk.  If may need to make the OS screen time-out longer if you don't want to have to keep touching the display to keep it on.

[Michael]

@Doug That is true, but the live data displayed in the app doesn't get synced to the Fitbit servers, so it isn't available via the API, which is what he was asking for.

[JeremiahFitbit]

@lukas444: Sorry for the delay. We hope to get to this in the next two weeks.

[ShaneFitbit · Accepted solution]

Hi dcburke1,

The bug should be fixed now. Thanks for bringing this to our attention and apologies for the delay!

-Shane 

[MikeGr]

Can I enter a custom scheme without anything after the ://. For example, If i wanted to use simply overwolf-extension://    , how come I am getting the same error message that it is not a valid url?

Thank you!

[JeremiahFitbit]

We're going to update the validation so that nothing is required but "://" when not using http or https.

[MikeGr]

Jeremiah,

Thank you. How can I find out when this has been implemented?

Thanks!

[JeremiahFitbit]

We'll post an update in this forum topic.

[MikeGr]

Thank you. Any eta?

Thanks

[JeremiahFitbit]

We hope to have this out in a release sometime next week.

[ShaneFitbit · Accepted solution]

The issue is fixed now. Any urls with non-http and https schemes no longer need a path. 

[Navindas]

But for iOS its not working as expected. When I try to achieve it with custom url scheme e.g. myiOSapp:// it redirect me to other page which have message like "Sorry, that page is following a different trail.". It is working fine with https url scheme but not with custom url scheme.