yashsingh1/xdaforums huggingface dataset:
[Magisk] iBART:
Magisk updated on stable channel to 15.0

Anyway,moto g5 plus, Los 14.1, ele kernel.

12-27 13:34:50.046: F/DEBUG (3387): pid: 2580, tid: 2853, name: MediaScannerSer >>> android.process.media <<<

12-27 13:34:51.446: F/DEBUG (3640): pid: 3494, tid: 3568, name: MediaScannerSer >>> android.process.media <<<

12-27 13:34:53.860: F/DEBUG (4057): pid: 4006, tid: 4029, name: MediaScannerSer >>> android.process.media <<<

12-27 13:36:16.784: F/DEBUG (7175): pid: 6878, tid: 7172, name: MediaScannerSer >>> android.process.media <<<

12-27 13:36:18.425: F/DEBUG (7211): pid: 7191, tid: 7208, name: MediaScannerSer >>> android.process.media <<<

12-27 14:07:06.783: I/ActivityManager(1194): Start proc 12155:android.process.media/u0a9 for content provider com.android.providers.media/.MediaProvider

12-27 14:36:01.649: I/ActivityManager(1194): Killing 12155:android.process.media/u0a9 (adj 906): empty #17

12-27 14:54:50.872: I/ActivityManager(1194): Start proc 17802:android.process.media/u0a9 for content provider com.android.providers.media/.MediaProvider

12-27 14:55:26.547: F/DEBUG (18077): pid: 17802, tid: 18075, name: MediaScannerSer >>> android.process.media <<<

12-27 14:55:26.908: I/ActivityManager(1194): Process android.process.media (pid 17802) has died

12-27 14:55:26.921: I/ActivityManager(1194): Start proc 18088:android.process.media/u0a9 for content provider com.android.providers.media/.MediaProvider

12-27 14:55:27.233: F/DEBUG (18114): pid: 18088, tid: 18107, name: MediaScannerSer >>> android.process.media <<<

12-27 14:55:27.443: I/ActivityManager(1194): Process android.process.media (pid 18088) has died

12-27 14:55:31.978: W/ActivityManager(1194): Ignoring remove of inactive process: ProcessRecord{c709eb 0:android.process.media/u0a9}

12-27 14:55:32.542: W/ActivityManager(1194): Ignoring remove of inactive process: ProcessRecord{788f360 0:android.process.media/u0a9}

Crashes on startup or opening Google Photo. Uninstaller Google photo, disabled all magisk modules, keep crashing on startup.

Thanks.
[Magisk] jayte2168:
A new error occured.Failed to mount '/system' (Invalid argument)

************************

Magisk Uninstaller

************************

- Mounting /system, /vendor

mount: mounting /dev/block/platform/hi_mci.0/by-name/system on /system failed: Invalid argument

! Cannot mount /system

- Unmounting partitions

Updater process ended with ERROR: 1

I:Legacy property environment disabled.

I:Install took 2 second(s).

Error installing zip file '/external_sd/Magisk-uninstaller-20171226.zip'

Updating partition details...

I:Data backup size is 1115MB, free: 50641MB.

I:Can't probe device /dev/block/mmcblk0p43

Failed to mount '/system' (Invalid argument)

I:Actual block device: '/dev/block/mmcblk0p43', current file system: 'ext4'

I:Unable to mount '/usbotg'

I:Actual block device: '', current file system: 'auto'

...done

I:Set page: 'flash_done'

I:operation_end - status=1

I:Set page: 'clear_vars'

I:Set page: 'install'

I:Set page: 'main'

I:Set page: 'clear_vars'

I:Set page: 'main2'

I:Set page: 'advanced'

I:Set page: 'copylog'

I:Set page: 'action_page'

I:operation_start: 'Copy Log'

I:Copying file /tmp/recovery.log to /external_sd/recovery.log
[Magisk] Didgeridoohan:
Dude... Have you seen the number of posts the last couple of days? I'm actually trying to read them all but I definitely do not have time to reply to everyone or keep 100% track of every post by every user... I'm providing what little help I can because I enjoy it, but the last couple of days have been taxing.

At least post a link to a post of yours with the details.

OT, but... It's quite common that /vendor simply is a symlink to /system/vendor. If that's the case on your device, use /system/vendor/etc as a path.
[Magisk] Rom:
@topjohnwu

Hello,

I have just flash the last Magisk zip (v15), and by looking the recovery log, i can see that the img boot of my phone is found, but i get an JAVA error:

- Found boot image: /dev/block/mmcblk0p18
java.lang.ClassCastException: org.bouncycastle.asn1.DERApplicationSpecific cannot be cast to org.bouncycastle.asn1.ASN1Sequence
at com.topjohnwu.crypto.SignBoot$BootSignature.<init>(Unknown Source)
at com.topjohnwu.crypto.SignBoot.verifySignature(Unknown Source)
at com.topjohnwu.magisk.utils.BootSigner.main(Unknown Source)
Invalid image: not signed
- Unpacking boot image
MagiskBoot v15.0(1500) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/dev/block/mmcblk0p18]

Regarding the dmesg log file, idk how to investigate it for this type of problem.

I send here my two log files, if you want that i send the boot image my phone, you can tell me by PM instead of this thread where i can find it, as u want.

Oddly enough (and may be due to the many changes you made from 14 to 15), I tried once again to enable root masking for one of my user apps and restart my phone, the setting in question did not jump after that, so much better.

Thanks in advance:good:
[Magisk] Veid71:
You're good man I understand there's a lot lol no need to rush i just wasn't sure if you were tracking my issue or not I'm using SU for the time being until everything's fixed but my post is over on page 474 not sure why it wouldn't let me link it on my phone but I screenshotted it for you in case that makes it easier I appreciate all the help people have been trying to help me but none of the methods they suggested have fixed the problem yet :/
[Magisk] sjevtic:
Magisk, Termux, and OpenSSH

I'm running into some issues with Termux, and its OpenSSH package when using MagiskSU 14.6 on Android N (SuperMan ROM 2.8.0 by [MENTION=5899304]Tkkg1994[/MENTION]). Though MagiskSU has made some significant progress lately, it seems like it has a problem launching the daemonizing sshd process.

This does not work; when the command completes, there is no sshd running, and nothing in the log file:

LD_LIBRARY_PATH=/system/lib64:$LD_LIBRARY_PATH /sbin/su -p -c /data/data/com.termux/files/usr/bin/sshd -f /data/data/com.termux/files/usr/etc/ssh/sshd_config_root -E /data/data/com.termux/files/home/start-sshd/sshd_log.txt

But this does:

LD_LIBRARY_PATH=/system/lib64:$LD_LIBRARY_PATH /sbin/su -p -c /data/data/com.termux/files/usr/bin/sshd -f /data/data/com.termux/files/usr/etc/ssh/sshd_config_root -E /data/data/com.termux/files/home/start-sshd/sshd_log.txt -d

The only difference here is the -d flag, which is described in the sshd man page:

-d Debug mode. The server sends verbose debug output to standard
error, and does not put itself in the background. The server
also will not fork and will only process one connection. This
option is only intended for debugging for the server. Multiple
-d options increase the debugging level. Maximum is 3.

Note that:

There is no issue starting a daemonizing non-privileged sshd.

SuperSU has no problem starting the daemonizing privileged sshd.

A daemonizing privileged sshd can be started from an already-running privileged shell that MagiskSU previously started.

So, I suspect there is something odd here about the way MagiskSU is starting sshd. Any thoughts?

The LD_LIBRARY_PATH path manipulation seems to be an unfortunate consequence of the Termux shared libraries not containing the requisite dependencies for MagiskSU and numerous system binaries that shipped with the Android N ROM. Because it affects so many system binaries though, it seems like more of an issue with Termux than MagiskSU in my opinion.
[Magisk] VincentJoshuaET:
An app keeps prompting me superuser access, and I keep granting it forever yet it still prompts (Tiles app, happened to other apps as well). Also, I cannot change the Magisk Manager superuser access settings, it's stuck on Apps and ADB. Clearing logs causes a force close. Removing superuser permissions to apps also causes a force close.

I already cleared Magisk Manager's app data, reinstalled it as well. Though the same settings are restored even though I didn't restore them.

Also, the logs on superuser don't seem to be updating.
[Magisk] guest4711:
Think he means https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post74962808

And there is a log attached ...
[Magisk] topjohnwu:
Currently I'm targeting 2 issues:

Bootloops on Samsung devices. It seems that they are caused by dm-verity patch failure

Unencrypted devices unexpectedly encrypted

Both of the issues above are not in Magisk itself, but rather an installation/detection failure.

I will be active here for a few more hours, please upload your recovery.log and boot.img so I can know what's going on.

Sorry I can't go through all previous reports (don't have the time), If you already reported with recovery logs (or you found a decent report), point me there and I'll check it out
[Magisk] Pkt_Lnt:
Off to a couple morning appointments, I have your log and will look when I get home this afternoon.

---------- Post added at 08:52 AM ---------- Previous post was at 08:50 AM ----------

One here with a pixel issue, not mine but recovery log is attached. Thanks

https://xdaforums.com/showpost.php?p=74962808&postcount=4738
[Magisk] Kinder91:
hi all

This morning magisk offers me an update V15.

I launch it, he offers me to restart the phone, what I do.

And this is the drama, I had a nice message "Encryption unsuccessful".

I tried 2 3 reset but I gave up because I was already late for work ..

I guess it's the famous soft brick.

If a charitable soul could give me some advice, I am interested.

FYI, I still access the recovery twrp and I can access the entire contents of the phone via the "explore" function of the twrp.

Am I good for a complete reinstall with loss of all the data stored in the apps?

or a "wild" reinstall of the ROM can unblock me the situation?

thank you in advance for helping me
[Magisk] topjohnwu:
Your Magisk Manager does not have root permission. You should have enabled the hide manager feature, and something messed up. Try to uninstall your current manager, and re-install the latest APK from the OP.
[Magisk] Veid71:
Yeah it doesn't look like the hide magisk one exists and I've tried uninstalling and reinstalling it with the uninstaller like 4 times it always produces the same result for some reason
[Magisk] topjohnwu:
Can you grab a logcat when launching Magisk Manager?
[Magisk] leo.riv:
I am having issues with v15.0 on my Lenovo VIBE X3 (X3a40) 64bit android 6.0.1

I was able to flash Magisk 14.3 via TWRP with no issues.

after flash 14.5 or 14.6 or 15.0 have stuck on bootloop

I have a strange experience

When i am flashing 14.5 or 14.6 or 15.0 via TWRP couldn't get boot log,

but when i am flash Magisk 14.3 via TWRP get boot log,

I am uploading the recovery logs & 14.3 boot log

View attachment logcat.zip
[Magisk] Didgeridoohan:
https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/
[Magisk] Didgeridoohan:
Yes, please do what [MENTION=4470081]topjohnwu[/MENTION] asked about earlier and provide the recovery log from when flashing v15.0 and a copy of your boot image.
[Magisk] Jamoeda:
After severals installs of magisk 15.0 on Op5t, keep show me that error when I tried to install modules from magisk manager. Someone can help me fix this?

Log attached
[Magisk] Jamoeda:
More logs
[Magisk] _alexndr:
Bootloop here, Magisk v15 @ Samsung Galaxy S7 running pure stock (DQL1) ROM :(

According to your request in another thread - see attached (zipped) recovery.log, backed up stock boot.img and patched (zipped) boot_magisk.img

/data/adb/magisk_debug.log has not been created at all (clean install case over stock), so can't upload it...
[Magisk] Veid71:
heres the Matlog i opened it and this was the first thing i saw i notated some of the errors i saw but i attached it so you guys can look at it you guys are a lot better at this technical stuff than me lol i appreciate all the help ^_^ let me know if theres anything else i can do for ya that will help with the process, also on a side note it seemed like when i gave matlog root permission when magisk would ask for it it didnt stick so i opened up my file explorer and went to the root part and when it asked for permission i gave it to it but it didnt actually have permission for some reason

12-27 17:47:59.135 E/Magisk (20227): fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory

12-27 17:47:59.142 E/Magisk (20227): fopen: /data/adb/magisk_debug.log failed with 1: Operation not permitted

12-27 17:47:59.142 F/libc (20227): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x58 in tid 20230 (magisk)

then there was this saying something about a broken pipe?

12-27 17:47:59.256 E/ (20234): AM data write failed: Broken pipe

this pops up a lot within the log

12-27 17:48:00.597 E/Magisk (20269): fopen: /sbin/.core/img/.core/hidelist failed with 2: No such file or directory
[Magisk] Didgeridoohan:
https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post74978390#post74978390

Probably not. It's likely dm-verity issues, forced encryption or similar.

Install log, recovery log, Magisk log. All of those would be useful...

Are you using something other than an integer for versionCode in the module.prop? What you're seeing usually happens then... For versionCode the value HAS to be an integer.

Otherwise, how about providing one of those modules for analysis?
[Magisk] aryanking01:
I did not know how to post a picture so I have pasted this link of the logs and screenshots. Thank you :)

https://www.dropbox.com/sh/ag7vq19u3ydoixa/AACQ8G_U58sWiDA5JONIKIcJa?dl=0
[Magisk] shadowstep:
Thank you! That fixed it. I was not using an integer, actually. My version code was "3.0" and hence the issue. As soon as I removed the dot in the middle, it was fine. Thanks a lot once again! :)
[Magisk] Andrean123:
I use Redmi 4 Prime running MIUI 9 7.12.21. Installed v15 & TWRP says install complete , rebooted and no magisk manager installed & no root. Tried direct install from v14.5 but it force closes.

Recovery log attached
[Magisk] kush1131:
my phone is stuck on bootloop on v15 and 14.6

was working fine on v14.5

galaxy s6 edge plus (sm-g928g)

Nlite v6 nougat rom.

Here are the attached logs.
[Magisk] Jamoeda:
I get some error when I tried to install módulos from magisk manager. I attached log.

Can you log tell whats wrong?
[Magisk] Rom:
Same issue like with Magisk v15

@topjohnwu Hello,

Apparently i get the same boot img error during the Magisk v15.1 ZIP flash..

************************
* Magisk v15.1 Installer
************************
- Mounting /system, /vendor
- Device platform: arm
- Constructing environment
- Adding addon.d survival script
- Found boot image: /dev/block/mmcblk0p18
java.lang.ClassCastException: org.bouncycastle.asn1.DERApplicationSpecific cannot be cast to org.bouncycastle.asn1.ASN1Sequence
at com.topjohnwu.crypto.SignBoot$BootSignature.<init>(Unknown Source)
at com.topjohnwu.crypto.SignBoot.verifySignature(Unknown Source)
at com.topjohnwu.magisk.utils.BootSigner.main(Unknown Source)
Invalid image: not signed
- Unpacking boot image
MagiskBoot v15.1(1510) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/dev/block/mmcblk0p18]

I need to find and send here my boot image ?

Thanks in advance.
[Magisk] Didgeridoohan:
I believe that simply means that your boot image isn't signed...
[Magisk] Rom:
Yeah, but i don't understand why itsn't supported by Magisk, it is not encrypted, and there is no need to add any signature..
[Magisk] firozpatel:
HELP!!

Updated to 15.1 and still not passing safety net

Help onebodyy
[Magisk] Jamoeda:
I installed latested 15.1 anda I can t install modules.

Give me magisk_merge imgur.com mount fail.

Debug log attached.

Anyone with that issue?
[Magisk] Jamoeda:
Can't install modules. Latest magisk 15.1.

Anyone with that issue?

Log attached.
[Magisk] luan165:
Bug App's SD card.

All versions above 14.5 do not work on my phone (asus live G500TG), applications saved on SD card are not loaded.

Edit: I installed rom and tested 15.1, it does not allow me to move apps to the sd card. I believe that some modification was made from the versions above 14.5. :(
[Magisk] BustyLoli-Chan:
I'm also having an issue similar to this on the One Plus 3t. Seems like nothing has permission to use "external storage".

I'm going to try uninstalling and then installing 14 to see if this fixes the issue.

For whatever it's worth I've uploaded the debug log https://gist.githubusercontent.com/...43bee6b0364f368d1234a67fd84f/magisk_debug.log

Alright, so I don't know if this was an issue with magisk in the end... wiping user data fixed it while several attempts to install different versions of magisk did not
[Magisk] korom42:
[MENTION=4667597]Didgeridoohan[/MENTION] [MENTION=4470081]topjohnwu[/MENTION] Unfortunately got in bootloop with V15.1 too

Device : Xperia XZ F8332

ROM : Official Stock Oreo 8.0 (fw 41.3.A.2.24)

v14.3 and v14.5 only versions that work 100%

bootloop log attached below

Previous log for v15 #4793
[Magisk] Mondor1979:
Magisk 15.0 or 15.1 always shows Error 1 when trying to flash it to my Honor 9 8.0.0.321(C10). Shows "Modified" boot error on clean just installed system with complete wipes performed before this installation. SuperSU 2.82 shows the same message but it installs and works good after that. Logs I have are attached. Any help would be appreciated.

DMESG is 1024 KB, posting it as a link.

https://yadi.sk/i/-isMXPnR3R5utZ
[Magisk] copota:
15.1(1510) success on my...

Samsung Note 5 SM-N920P (sprint)

Nougat 7.0 Stock Touchwiz rooted with TWRP 3.2.1-0

Phone booted right away, and SafetyNet passes. I flashed 15.1 via recovery, after uninstalling 14.5.

I attached my magisk_debug.log just in case you want to review.

Thanks for all the hard work and dedication provided by the developers!
[Magisk] laupuy:
Yep, same here.

Device: OnePlus3

Rom stock, OpenBeta 29 (oreo)

Install log attached
[Magisk] korom42:
Since v15+ caused bootloop and last working version for me is 14.5 this is debug log for 14.5 + stock boot img maybe this can help
[Magisk] Razor10707:
https://drive.google.com/file/d/1mhvQfnsNPnM5fYM_NLn_-PpPV5cJLxWP/view?usp=drivesdk

V14.5 (1456) here
[Magisk] coronero:
Experiencing high cpu usage by magisk_daemon on 15 as well as on 15.1. Rolling back to 14.x gets things back to normal.

Revolves around messages like the following:

proc_monitor: com.google.android.gms.unstable (PID=12622 ns=mnt:[4026534584])

12-29 22:16:56.756 677 975 E Magisk : mount (null)->/ failed with 16: Device or resource busy

12-29 22:16:56.761 12637 12637 I Magisk : hide_daemon: Permissive detected, hide the state

12-29 22:17:07.211 677 975 E Magisk : mount (null)->/ failed with 16: Device or resource busy

P. S: Running on HTC 10 with Nougat Viper ROM
[Magisk] allanjohnkemp:
Can confirm that 15.1 installs fine on mate 9 now. Passes first boot whether installing from magisk manager or twrp. 15.1 passes softener. Only issues so far is that it re encrypts the device making all files unusable in twrp but I removed from device first so I'm safe. Flashing 15.1 also deletes Google account and trips the phone sort of into a first boot. Magisk log attached.
[MENTION=4667597]Didgeridoohan[/MENTION] logs as requested
[Magisk] Shiroki_Mashumaro:
The first log is generated when I try to undo the root authorization for the application.

The second log occurs when I open Magisk Manager. And I can't open magisk Manager anymore.
[Magisk] danmaman:
[MENTION=4470081]topjohnwu[/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION]

here is what a Dev wrote about magisk 15.1 bootloop and the OpenBeta for oneplus 3/T whatever

https://xdaforums.com/showpost.php?p=75006343&postcount=236
[Magisk] spysky:
Beelink GT1 Ultimate - Android 7.1..2 - error with builds newer than 14

Hi all,

I've done a quick search in the tread, but i don't think my issue is similar to anyone else's.

I'm installing magisk on a Beelink GT1 Ultimate, and when i flash the Magisk-v14.0.zip, it works perfect.

However all newer versions give me the same error, "Updater process ended with ERROR: 1". So far I've tried: Magisk-v14.6(1468), Magisk-v15.1, Magisk-v15.1(1510).

I'm flashing through TWRP, the magisk manager app, notifies and downloads the zip, but does not install or display any error.

From the logs, this looks like where the error starts:

mv: can't rename '/data/magisk.img': No such file or directory

...

! Unable to detect boot image

- Unmounting partitions

Updater process ended with ERROR: 1

Can anyone give some help with this?, in attach is the full TWRP logs

Thanks
[Magisk] SeishiNui18:
A lot of logs

First, thanks to [MENTION=8296134]Razor10707[/MENTION] for providing v14.5(1456) zip.

[MENTION=4470081]topjohnwu[/MENTION],

Here's what I got. First off, I did a clean start using the latest uninstaller zip then flashed v14 in TWRP. Updated Manager to the latest (5.5.2) then tried to install v15.1 which didn't change after reboot. Then went on to v14.5 to get some debug log, I have two: one before and one after reboot.

So, a lot of logs indeed which I hope will help you out.

Main concern: Not applying the update if done via Manager.
[Magisk] gilcu3:
I'm on Lineage OS 14.1 Google Nexus 5, rooted with magisk 15.1 (latest stable version). Since upgrading to 15.0 I have seen several "random" reboots, and every time it does it, I see this line in magisk log:

12-28 14:43:10.825 16328 16328 W Magisk : su: request rejected (10104->0)

full log:

12-27 14:44:25.074 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=3231 ns=mnt:[4026534305])
12-27 21:27:56.742 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=1215 ns=mnt:[4026534263])
12-27 21:37:53.649 4397 4397 W Magisk : su: request rejected (10104->0)
12-27 21:38:02.368 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=5793 ns=mnt:[4026534279])
12-27 21:38:22.124 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=7368 ns=mnt:[4026534324])
12-27 21:44:17.504 10844 10844 W Magisk : su: request rejected (10104->0)
12-27 21:44:31.759 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=12188 ns=mnt:[4026534277])
12-27 21:45:04.936 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=13560 ns=mnt:[4026534310])
12-27 22:51:33.590 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=21787 ns=mnt:[4026534372])
12-27 23:17:01.306 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=24101 ns=mnt:[4026534372])
12-28 00:42:25.067 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=28366 ns=mnt:[4026534377])
12-28 07:30:29.435 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=7072 ns=mnt:[4026534378])
12-28 09:20:20.298 16129 16129 W Magisk : su: request rejected (10104->0)
12-28 09:20:34.586 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=17507 ns=mnt:[4026534260])
12-28 09:20:58.735 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=18715 ns=mnt:[4026534306])
12-28 10:16:32.084 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=25014 ns=mnt:[4026534267])
12-28 14:09:42.775 31406 31406 W Magisk : su: request rejected (10104->0)
12-28 14:09:51.975 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=32716 ns=mnt:[4026534289])
12-28 14:10:17.368 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=1705 ns=mnt:[4026534305])
12-28 14:17:06.238 5252 5252 W Magisk : su: request rejected (10104->0)
12-28 14:17:23.734 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=7166 ns=mnt:[4026534291])
12-28 14:17:33.555 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=7838 ns=mnt:[4026534396])
12-28 14:43:10.825 16328 16328 W Magisk : su: request rejected (10104->0)
12-28 14:43:28.999 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=17844 ns=mnt:[4026534402])
12-28 14:43:44.037 160 191 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=19213 ns=mnt:[4026534379])

The UID 10104 corresponds to this app USSD Dual Widget for which I have denied root permission on MagiskManager. This behaviour wasn't happening on previous stable Magisk 14.0.

Thanks for such a great project :D Happy new year!!!