Target SDK version upgraded to 36 - Fixed an issue on Android 16 where some apps (e.g., MX Player) could not start normally after being intercepted and tapping "Allow" - Fixed an issue where app launches that carry return values (e.g., QQ login, TapTap login) could not start normally after being intercepted and tapping "Allow" - Optimized the UI of the launch authorization dialog - Added a "Log Recorder" to easily monitor app launch behavior and interception records - The launch authorization dialog now supports long-pressing an Activity name to copy the relevant rule - Adopted a new rule storage scheme, improving rule read/write compatibility and stability - Fixed various minor issues and small bugs ⚠️ Important Note: This update involves significant low-level changes. A system reboot is required after installation for normal operation. Thank you for every Issue submitted. The author continuously monitors, evaluates, and improves the module based on your feedback.

This is an Xposed module that intercepts launches from one third-party app to another. When activated, if a third-party app tries to launch another third-party app, the system will pop up an app launch dialog. You can also set custom allow/deny rules. Give it a try! Module Conflict Notice - The "Activity Launch Protection" feature in the "Hide My Applist" module may cause abnormal interception for some apps. You need to enable the "Disable Activity Launch Protection" option in the settings. Custom Rules Explanation Syntax: identifier caller target - Custom rules allow flexible configuration for various apps (system apps are currently not supported). There are three identifiers: allow, ask, deny. The default rule is ask. - For apps that use special wake-up methods that cause background launches, you need to configure background launch interception rules. Example Templates: - Template 1: allow caller_package_A target_package_B – Allows app A to launch app B; no dialog will pop up. - Template 2: deny caller_package_C A:target_activity_D – Denies app C from launching activity D of the target app; no dialog will pop up (note the A: prefix before the activity name). - In the request dialog, long-press the activity name to copy related example rules. To capture more launch behavior info, use the Log Recorder. - For more advanced rule templates, open the app to view the comments. New Background Auto-Start Interception Setting Starting from version 1.06(7), to address special app launch methods, the old complex multi-chain A:{**} interception feature has been deprecated and replaced with the Background Intercept Launch feature. This new feature can more effectively intercept background activity auto-starts, with simpler syntax. - New background auto-start interception template syntax: ask -b related_package(TOP) A:target_activity_name PS: How to allow apps without rules by default, while still adding ask rules as needed? allow * * # Global allow for apps without rules ask … … ask … … deny … … Log Recorder The Log Recorder is used to view historical activity launch records. This tool greatly helps users capture and copy activity launch behavior to write custom rules. Any app launch behavior cannot escape the recorder's tracking. It can also record module bug logs. If you encounter any exceptions, please provide at least a screenshot of the Log Recorder before submitting an Issue.