Closed KieronQuinn closed 2 years ago
With further testing, it seems that while the server can now start, apps are unable to request permissions or connect to the service. There's probably been some more method signature changes.
About rikka.core.util.BuildUtils
, rikka.core.util.BuildUtils
use kotlin inline, but Android Studio lint cannot recogonize it, so actually I want to replace it with normal Build.VERSION.SDK_INT
(and androidx.core.os.BuildCompat
for preview systems).
Fixed in b09ac2580045ce182d49b4cf17cd5bf8fdf805f3, thank you!
Please report bugs of Shizuku itself.
Requirements:
Change "[ ]" to "[x]" if it meets the requirements.
Reports not meet the requirements will be immediately closed.
Information:
Logs:
Relevant lines:
02-11 00:14:31.010 31841 31841 I Service : starting server... 02-11 00:14:31.011 31841 31841 I shizuku_server: System.exit called, status: 50 02-11 00:14:31.011 31841 31841 I AndroidRuntime: VM exiting with result code 50.
Related full logcat.
Describe the bug:
In Android 13 the method signature for IPackageManager.getApplicationInfo has changed from
to
This causes the server to not find the manager, and thus exit with code 50. Changing the method signature (simply casting to long) fixes it, and I would make a PR, except it's not pretty:
Of course, there are SDK checks in BuildUtils.java in the common module, but this module is not a dependency for the server, and is tagged with a todo to be replaced with
rikka.core.util.BuildUtils
, so I suggest it might be a good time to do that migration and use it in the server at the same time instead.Additional context:
The suggested fix works on 13 DP1: