This is possibly related to  Issue 170925  and  Issue 170880 

I am also having the exact same issue since the most recent Chrome for Andorid update. Please fix it ASAP!

same issue here, switch to 'Browser', the built-in app in android, will work, but not chrome with the latest updates. please fix, thanks.

I tried this on 25.0.1364.123, authorising with a Google account, and was unable to reproduce the problem (worked for me). It might be that the Flickr redirect back to the native application has changed since this bug was filed. 

Is this still a problem? What is the failure rate? Is it specific to any kind of account (e.g. Google / Yahoo / etc/) ?

Still seeing this in our app with 25.0.1364.169; not sure whether the example app has changed.

Mat, is your app public? Any chance I can try with it?

The app is here, but will need a username and password sent separately; I can email credentials over if you'd like

https://play.google.com/store/apps/details?id=uk.ac.warwick.startwarwick

@jknot It curious that it's working for you.  Here's another quite accessible app that it happens with: https://play.google.com/store/apps/details?id=com.jjinx.dropboxdownloader (If you have the dropbox app installed you will need to uninstall it first, so it will try to authenticate using the browser).

Deleted: Screenshot_2013-03-11-11-44-36.png 116 KB

	Screenshot_2013-03-11-11-44-36.png 116 KB View Download

Ok, I got this to repro on a Nexus 7. It repro'd for a Yahoo and a Google account. I used the same version as @jknotten.

Also repro'd on Nexus 7. It seems that the problem is that URL overriding code is not being activated because there is a redirect to a 'form submit' (page transition type 7):

The authorize button on the page does a form submit to http://www.flickr.com/services/oauth/authorize.gne which redirects to flickrj-android-sample-oauth://... 

Project: .../internal/apps
Branch : master
Author : John Knottenbelt <jknotten@chromium.org>
Commit : 7d9974f13444641fb0f89e34f9be7d2334764914

Code Review +2: John Knottenbelt, Marcin Kosiba
Verified    +1: John Knottenbelt
Change-Id     : I95a2cdaef2f302c753bacfab9f891254dbfe911e
Reviewed-at   : https://gerrit-int.chromium.org/33572

Great news, thanks for your work all.

The fix is low risk IMO, and both me and John agree that it'd be worth merging to M26.

argh.. forgot that this needs to go through a Canary first.

 Issue 170880  has been merged into this issue.

 Issue 170880  has been merged into this issue.

Project  : .../internal/apps
Branch   : 1410
Author   : John Knottenbelt <jknotten@chromium.org>
Committer: Marcin Kosiba <mkosiba@google.com>
Commit   : 4c1e5a08cde5dbd059291159c4d7339c9be9ec23

Code Review +2: Marcin Kosiba
Verified    +1: Marcin Kosiba
Change-Id     : I717c2a4edc2aae5ff20a8ca663d3adb669c21475
Reviewed-at   : https://gerrit-int.chromium.org/34326

Thanks for the fix. Our app is working again

Hi Paul, 

I am facing similar issue that you mentioned above on latest Chrome Version 27.0.1453.90 If I uninstall the latest update of Chrome, my app works well on Chrome version 18.0.1025469

So if possible can you please retest your issue with latest Chrome update or provide me the link of your APK "FlickrjAndroidSampleActivity-debug.apk".

@23 Just tested authorising my Flickr app Glimmr with Chrome 27.0.1453.90, doesn't appear to be any problem (Glimmr uses the same mechanisms as FlickrjAndroidSampleActivity).  You should be able to build the apk from the github repo provided in OP.

Same problem here, with version 27.0.1453.90 of chrome on nexus 10 and nexus 4, i get ERR_UNKNOWN_URL_SCHEME while it's working on other browsers.

Still not working. Updated to latest.

Expected result:
Chrome should launch the app specified by the callback url.

Actual result:
Chrome fails to launch receiving app and instead displays the page shown in the attached screenshot.

This bug is marked as fixed and the author of the original issue (and more importantly original repro steps) confirmed this as fixed.
Since you're reporting that this is still not fixed, please file a new bug or at least provide the exact repro steps. Saying 'still not working' is not actionable for us. What isn't working, which app? what device? which version, which channel of Chrome? what exactly did you do to trigger the error?

This issue started occurring after a recent chrome update. Custom App URLs are not being recognized and chrome throws the same error as shown in the screenshot above.

Chrome Ver: 28.0.1500.64
Phone: Nexus 4
Android OS: 4.2.2

I'm having the same issue here. We have an app that is for iOS and Android devices.

So now I have to differ not only in "isIos" and "isAndroid", but rather in "isIos" and "isAndroid", and if "isAndroid", then is it "Chrome over V. 25?", then use this... 

Another major usability problem in my view is that when using the Intent-Uri-Scheme, Chrome/Android fall back to the store. BUT if the device is not supported the user gets an message stating the "pname:xxx.xxx..." could not be find. With the custom-Scheme-Uri method I could intercept after some timeout and direct the user to the play store, where as opposed to the Intent method, the user sees the app-detail-page with a nice warning that says "Your device isn't compatible with this version".

Anyone else ran into this?

 Issue 170880  has been merged into this issue.