"termux-notification -u" generates this intents with a NULL mimetype (termux/termux-api#35)
Intent Intercept catches the intent when it has scheme "http:" but not when it has scheme "file:"
This one works:
termux-notification -c xxxx -u http://www.google.com
this not:
termux-notification -c xxxx -u file:///sdcard/xxx.html
Example caught:
intent://www.google.com#Intent;scheme=http;launchFlags=0x13000000;end
ACTION: android.intent.action.VIEW
DATA: http://www.google.com
URI: intent://www.google.com#Intent;scheme=http;launchFlags=0x13000000;end
FLAGS:
FLAG_ACTIVITY_FORWARD_RESULT
FLAG_ACTIVITY_PREVIOUS_IS_TOP
FLAG_RECEIVER_FOREGROUND
Providing the example for the not caught one is not so easy, GhostCommander catches the view intent and opens a directory.
"termux-notification -u" generates this intents with a NULL mimetype (termux/termux-api#35)
Intent Intercept catches the intent when it has scheme "http:" but not when it has scheme "file:"
This one works:
termux-notification -c xxxx -u http://www.google.com
this not:
termux-notification -c xxxx -u file:///sdcard/xxx.html
Example caught:
intent://www.google.com#Intent;scheme=http;launchFlags=0x13000000;end
ACTION: android.intent.action.VIEW
DATA: http://www.google.com
URI: intent://www.google.com#Intent;scheme=http;launchFlags=0x13000000;end
FLAGS:
FLAG_ACTIVITY_FORWARD_RESULT
FLAG_ACTIVITY_PREVIOUS_IS_TOP
FLAG_RECEIVER_FOREGROUND
Providing the example for the not caught one is not so easy, GhostCommander catches the view intent and opens a directory.