Unified intent URI?

Question

I am having problems with intent URIs on a specific device, so I tried the CommonsWare URLHandler sample, as suggested here: Running my application using intent URIs and the intent URI hyperlink on my sample page also cannot invoke the application. The sample announces its filter intent as follows:

<intent-filter> <action android:name="com.commonsware.android.MY_ACTION" /> <category android:name="android.intent.category.DEFAULT" /> <category android:name="android.intent.category.BROWSABLE" /> </intent-filter> 

And the hyperlink on the example web page:

 <a href="intent:#Intent;action=com.commonsware.android.MY_ACTION;end">Link back to URLHandler via intent: URL</a> 

This works on most devices, but not on HTC Amaze 4G running Android 4.0.3. When I touch the link, Logcat gives:

 I/PRIME(9029): <CallBackProxy> Send to WebViewClient. I/PRIME(9029): <Browser> Send to HtcLinkifyDispatcher I/ActivityManager(262): START intent from pid 9029 D/MP-Decision(891): Aggress decision engine: Off D/MP-Decision(891): Switch back to normal parameters: Nw=2.700000, Tw=180, Ns=2.100000, Ts=270, Decision_ms=100, Poll_ms=10 V/NfcService(600): setForegroundNdefPush msg = null callback = null D/HtcTelephony(561): requestSetFastDormancy: module=0 mode=0 D/WebViewTimersControl(9029): onBrowserActivityPause D/WebViewTimersControl(9029): Pausing webview timers, view=com.android.browser.BrowserWebView@40e562f8 I/ActivityManager(262): Start proc com.htc.HtcLinkifyDispatcher for activity com.htc.HtcLinkifyDispatcher/.HtcLinkifyDispatcherActivity: pid=11087 uid=1000 gids={1015, 3002, 3001, 3003, 5001, 5003, 3007, 3006, 2001, 1007} D/ConnectivityService(262): onUidRulesChanged(uid=1000, uidRules=0) V/browser(9029): BrowserActivity.onWindowFocusChanged D/HtcLinkifyDispatcherActivity(11087): @@@@@ receive action=com.commonsware.android.MY_ACTION I/HtcAppAssociationsUtils (Dispatcher)(11087): @@@@@ enable by 2 = true I/HtcAppAssociationsUtils (Dispatcher)(11087): @@@@@ method = 0 I/HtcAppAssociationsUtils (Dispatcher)(11087): @@@@@ check enable = true D/MP-Decision(891): Aggress decision engine: On D/ActivityManager(262): Config after re-evaluted by window manager: null D/MP-Decision(891): Switch to aggressive parameters: Nw=1.990000, Tw=140, Ns=1.400000, Ts=190, Decision_ms=50, Poll_ms=10 V/browser(9029): BrowserActivity.onWindowFocusChanged D/HtcTelephony(561): requestSetFastDormancy: module=0 mode=1 W/InputManagerService(262): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40e75100 D/WebViewTimersControl(9029): onBrowserActivityResume D/WebViewTimersControl(9029): Resuming webview timers, view=com.android.browser.BrowserWebView@40e562f8 W/BaseUi(9029): mMainView is already attached to wrapper in attachTabToContentView! W/BaseUi(9029): mContainer is already attached to content in attachTabToContentView! V/NfcService(600): setForegroundNdefPush msg = null callback = android.nfc.INdefPushCallback$Stub$Proxy@40e73470 D/memalloc(9029): /dev/pmem: Unmapping buffer base:0x569c5000 size:4386816 offset:4177920 D/browser(9029): [BrowserActivity::Connectivity_Type] ===== 1 I/ActivityManager(262): No longer want com.htc.providers.settings:remote (pid 10935): hidden #16, adj=15 D/Process(262): killProcessQuiet, pid=10935 D/Process(262): dalvik.system.VMStack.getThreadStackTrace(Native Method) D/ConnectivityService(262): onUidRulesChanged(uid=1000, uidRules=0) D/Process(262): java.lang.Thread.getStackTrace(Thread.java:599) D/Process(262): android.os.Process.killProcessQuiet(Process.java:823) D/Process(262): com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:15132) D/Process(262): com.android.server.am.ActivityManagerService.trimApplications(ActivityManagerService.java:15294) D/Process(262): com.android.server.am.ActivityStack.activityIdleInternal(ActivityStack.java:3450) D/Process(262): com.android.server.am.ActivityManagerService.activityIdle(ActivityManagerService.java:4303) D/Process(262): android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:362) D/Process(262): com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:1706) D/Process(262): android.os.Binder.execTransact(Binder.java:338) D/Process(262): dalvik.system.NativeStart.run(Native Method) 

Does anyone know what happens with URI intentions here? Why doesn't it work? And is there a workaround?

Thanks Simon

Answer 1

Since I can replicate this issue on HTC One S, and I cannot replicate this issue on other ICS / JB devices, I believe this is another result of the Linkify workaround that HTC came to the scene in response to a lawsuit led by Apple

And is there a workaround?

If you control both sides (for example, a WebView containing the link, as well as an application that responds to the intent URL), you can manually force the chooser through Intent.createChooser() , and this may work.

If, however, you rely on third-party code (such as a web browser) to be able to open your application on these HTC devices, I think you're just screwed.