Hi,
Google in Android 13 has made API(s) like Accessibility service(s) unavailable to apps not installed via a Session-based package installer, unless the User enables 'restricted settings' for an app in App Info Page settings.
SAI currently does not use the setPackageSource() API to tell the system that an APK is user-acquired, which could be dangerous because an App installed via SAI could trick users into enabling Accessibility service for it.
Therefore, SAI should use Android’s new setPackageSource() API to tell the system that the app came from a user-acquired APK via the parameters PACKAGE_SOURCE_LOCAL_FILE or PACKAGE_SOURCE_DOWNLOADED_FILE. This can be used by apps implementing the session-based package installation API to trigger the same behavior when sideloading arbitrary APK files.
Hi, Google in Android 13 has made API(s) like Accessibility service(s) unavailable to apps not installed via a Session-based package installer, unless the User enables 'restricted settings' for an app in App Info Page settings.
SAI currently does not use the setPackageSource() API to tell the system that an APK is user-acquired, which could be dangerous because an App installed via SAI could trick users into enabling Accessibility service for it.
Therefore, SAI should use Android’s new setPackageSource() API to tell the system that the app came from a user-acquired APK via the parameters PACKAGE_SOURCE_LOCAL_FILE or PACKAGE_SOURCE_DOWNLOADED_FILE. This can be used by apps implementing the session-based package installation API to trigger the same behavior when sideloading arbitrary APK files.