new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Tauri · Plugins and security · all subjects

deep-link/testing

8 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Deep link testing on desktop - installation requirement

Deep links are only triggered for installed applications on desktop. On Linux and Windows you can circumvent this using the register_all() Rust function to register schemes to trigger the current executable.

Deep link testing with register_all example

Example code for testing deep links on desktop using register_all(): use tauri_plugin_deep_link::DeepLinkExt; #[cfg_attr(mobile, tauri::mobile_entry_point)] pub fn run() { tauri::Builder::default() .plugin(tauri_plugin_deep_link::init()) .setup(|app| { #[cfg(any(windows, target_os = "linux"))] { use tauri_plugin_deep_link::DeepLinkExt; app.deep_link().register_all()?; } Ok(()) }) .run(tauri::generate_context!()) .expect("error while running tauri application"); }

AppImage deep link support with register_all

Installing an AppImage that supports deep links on Linux requires an AppImage launcher to integrate the AppImage with the operating system. Using the register_all() function allows deep links to work out of the box without requiring external tools. When the AppImage is moved to a different file system location, the deep link is invalidated since it uses an absolute path, making runtime registration important.

Deep link testing on macOS limitation

Registering deep links at runtime is not possible on macOS. Deep links can only be tested on the bundled application which must be installed in the /Applications directory.

Test deep links on Windows

To trigger a deep link on Windows, open <scheme>://url in the browser or run 'start <scheme>://url' in the terminal.

Test deep links on Linux

To trigger a deep link on Linux, open <scheme>://url in the browser or run 'xdg-open <scheme>://url' in the terminal.

Test deep links on iOS

To trigger an app link on iOS, open the https://<host>/path URL in the browser. For simulators, use 'xcrun simctl openurl booted https://<host>/path' to directly open a link from the terminal.

Test deep links on Android

To trigger an app link on Android, open the https://<host>/path URL in the browser. For emulators, use 'adb shell am start -a android.intent.action.VIEW -d https://<host>/path <bundle-identifier>' to directly open a link from the terminal.

Give your agent this brain