Yes, it looks like we regressed when we redesigned the OAuth UI as part of OAuth 2 and privilege scopes.

I'll see if I can create a quick fix.

@evzijst have there been any changes about this? I also wanted to create an OAuth consumer for an iOS app, so I need a callback URL that starts with a custom URL scheme. According to this thread this was possible in the past, but currently I get an "Enter a valid URL" error on the form when entering a non-http:// URL

Thanks @evzijst .

@rss_samuel Basically URLs that don't start with http://, but with something completely custom. People writing native, non-browser apps can bind those schemes to their application so that the browser will open it when it gets redirected to it.

If you've ever used bittorrent you may have seen "magnet links" which is an application of custom URL schemes.

@evzijst what your mean of custom url schemes?

I have deployed a fix for this. Custom URL schemes can now be used in OAuth callback URLs.

I had a closer look and realized this is a regression on our end.

Closing this preemptively.

This is more a support request than a feature request. I suggest we move it to support so we can discuss the details of your app, your actual requests and your consumer information.

Can you email all relevant details to support@bitbucket.org?