SafetyNet basicintegrity fails - Magisk

I have two Xiaomi phones, one Redmi Note 8 and one Redmi Note 10, both with unlocked bootloaders. I made a fresh factory reset on them and installed the latest version of Magisk.
My problem is that SN basicintegrity fails on both of them (and ctsProfile as well of course). But I want to take care of basicintegrity first.
What I have done already is to enable MagiskHide and also Hide Magisk app with a custom name.
For MagiskHide, I selected all modules under "Google Play services" and "Google Play Services for AR". Not sure if I should select anything else. I also tested hiding with a root checker app and it looks that hiding works.
I have no Magisk modules installed. Using stock ROM on both phones.
Is there anything else I should to to pass basicintegrity SN?

API error?
If so, just wait for some days new version will solve this problem.

Pixel 3 XL on android 11 with magisk 22. Safetynet passed up until a few days ago. Not now tho. I wonder what changed?

Guys just put some more effort into searching, there is one big Magisk support thread and lot of discussion about this issue

Update to latest Canary
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk

Lord Sithek said:
Guys just put some more effort into searching, there is one big Magisk support thread and lot of discussion about this issue
Click to expand...
Click to collapse
It's difficult to find info in one big thread, not sure why that's how most discussion happens. Separate threads make more sense.

hkjo said:
It's difficult to find info in one big thread, not sure why that's how most discussion happens. Separate threads make more sense.
Click to expand...
Click to collapse
Multiplying posts doesn't make sense in my opinion. Several different threads were created for the same issue. It's not really that difficult to check few last pages of the main support thread since the issue is relatively new

Yeah, multiple threads on the same topic aren't good.
But one big thread that mixes different discussions beats the whole idea. Threads were invented for a reason. To concentrate discussion on a specific topic or sub-topic, and to have a sensible title. To save you from scanning posts in a megathread to find out if they're about your topic or not. Also, not all discussion is necessarily recent.

I had the exact same issue yesterday.
A quick search of the support thread took me to
The solution

wfred said:
I had the exact same issue yesterday.
A quick search of the support thread took me to
The solution
Click to expand...
Click to collapse
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!

Cyb3rFr4nk said:
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!
Click to expand...
Click to collapse
The linked solution is:
Update Magisk (to build 22103 or later).
This thread is about the Magisk apps SafetyNet checker extension needing an update due to an API error. SafetyNet wasn't actually failing...
If you need a few tips on how to get SafetyNet passing, there are some collected here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

Cyb3rFr4nk said:
Hello,
Please, if you could—I hope you could—post the link to the solution you found. The masked link isn't working.
Thanks!
Click to expand...
Click to collapse
Here you go, don't know why it was messed up
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Basically it was moving to the canary

Didgeridoohan said:
The linked solution is:
Update Magisk (to build 22103 or later).
This thread is about the Magisk apps SafetyNet checker extension needing an update due to an API error. SafetyNet wasn't actually failing...
If you need a few tips on how to get SafetyNet passing, there are some collected here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
Click to expand...
Click to collapse
Thank you!
I had visited the link to your site, through Google search, while searching for a fix. I also went to magisk general discussion thread, and started reading from April 23rd backwards, in a bid to locate/trace "the solution." While doing that, I came across "the solution," but didn't really try that as I'm on a later stable build (23000) than that canary build.
Background: I started facing this issue, yesterday, after I installed 23.0, from 20.4—which I had been on for a long time and didn't really want to upgrade from to avoid something like this, but after updating my Redmi Note 7 to MIUI 12.5 (Q) (I'm on xiaomi.eu stable), I started having restarts. So, I made the jump.
The restarts stopped after uninstalling that build, so I decided to upgrade to the latest stable. Did that, only to find that SafetyNet no longer passes. Basic integrity fails, and that was before installing EdXposed, which usually causes this. When I first noticed it, I checked my Play Store for device certification status, and it came out positive. That changed after a couple of reboots—I don't know which one in particular, as there were quite some during that time.
I've tried everything—except uninstalling and re-installing magisk—without success: different versions of Universal SafetyNet Fix, MagiskHide Props, enabling and disabling MH.
I have decided to put up with it. Since only a couple of my apps are affected (no GPay in my country), I am trying to make do without them until I get my new phone. Don't wish to do something that would require a factory reset/data wipe, as this is currently my DD, and I'd hate to get stranded.
Thanks all the same.

wfred said:
Here you go, don't know why it was messed up
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Basically it was moving to the canary
Click to expand...
Click to collapse
Cyb3rFr4nk said:
Thank you!
I had visited the link to your site, through Google search, while searching for a fix. I also went to magisk general discussion thread, and started reading from April 23rd backwards, in a bid to locate/trace "the solution." While doing that, I came across "the solution," but didn't really try that as I'm on a later stable build (23000) than that canary build.
Background: I started facing this issue, yesterday, after I installed 23.0, from 20.4—which I had been on for a long time and didn't really want to upgrade from to avoid something like this, but after updating my Redmi Note 7 to MIUI 12.5 (Q) (I'm on xiaomi.eu stable), I started having restarts. So, I made the jump.
The restarts stopped after uninstalling that build, so I decided to upgrade to the latest stable. Did that, only to find that SafetyNet no longer passes. Basic integrity fails, and that was before installing EdXposed, which usually causes this. When I first noticed it, I checked my Play Store for device certification status, and it came out positive. That changed after a couple of reboots—I don't know which one in particular, as there were quite some during that time.
I've tried everything—except uninstalling and re-installing magisk—without success: different versions of Universal SafetyNet Fix, MagiskHide Props, enabling and disabling MH.
I have decided to put up with it. Since only a couple of my apps are affected (no GPay in my country), I am trying to make do without them until I get my new phone. Don't wish to do something that would require a factory reset/data wipe, as this is currently my DD, and I'd hate to get stranded.
Thanks all the same.
Click to expand...
Click to collapse

Related

Cannot get snapprefs working

I was hoping that I could get some insight here on the Nexus forum for an issue I'm having w/ xposed. I did post this over there but the thread for snapprefs has been closed. Any insight would be appreciated.
I cannot get snapprefs working in snapchat. I have been trying to get this to work for the last couple of days w/ no luck. I am running about 8 other modules in xposed w/ no issues. The first time I started from scratch yesterday, I removed all modules & only have snapprefs enabled currently. But what I have tried is completely removing xposed/installer (Framework: xposed-v80-sdk23-arm/installer: 3.0 alpha4) & both apps then starting from scratch. Even using past versions of SP & SC made no difference. I am attaching a logcat from xposed. The only other things worth mentioning is that my device is encrypted & I am not running a current version of Pure Nexus(I'm on ver-6.0.1-20160103 w/ stock kernal)but I wouldn't think these would make a difference since my other modules are working. So any help would be appreciated. Let me know if more information is needed.
Thanks!!
The thread was closed because any question you may have has already been answered. Snapprefs works fine on mine. Every rom I have have tried. Mind you I don't have mine encrypted as there really is no point.
Your issue from that log is the wrong version of Snapchat. The last version supported Is 9.21.1. So you will have to use that version and not update.
Also do not post the same thing across different threads.
Had you followed directions you would have been fine.
zelendel said:
The thread was closed because any question you may have has already been answered. Snapprefs works fine on mine. Every rom I have have tried. Mind you I don't have mine encrypted as there really is no point.
Your issue from that log is the wrong version of Snapchat. The last version supported Is 9.21.1. So you will have to use that version and not update.
Also do not post the same thing across different threads.
Had you followed directions you would have been fine.
Click to expand...
Click to collapse
Thank you, zelendel & sincere apologies man. I can't believe I overlooked that. Such an easy fix. Doh!
I don't use Snapchat but when I set it up for a friend I had an issue. If you have xposed framework installed, Snapchat will not login. You have to flash the xposed uninstaller in recovery. Then reboot and login to Snapchat. Once you successfully login then reboot and reinstall xposed and you will be good to re set up your other modules and snapprefs. Just a heads up and good luck.
bghouse10 said:
Thank you, zelendel & sincere apologies man. I can't believe I overlooked that. Such an easy fix. Doh!
Click to expand...
Click to collapse
No prob, but to be honest it's questions like that the dev had me close the thread.
Glad you got it working.
I completely understand & feel like a tool cuz I get annoyed when I come across it on the forum. I have been a member for a few years & not that anyone wants to look at my history but if you did, the few posts that I have made, were made after much reading, searching & as relevant as possible. Won't happen again. Thanks!

Viper4android Android 11??

There is viper4android for android11 or I need to wait?
Based on the research I've done we'll have to wait. There was an update to the magisk module September 12th but based on the change log it doesn't pertain to Android 11.
I wasn't able to enable tethering or install viper therefore I rolled back to 10 and will continue to monitor.
Thanks ?
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
SirAugustine said:
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
Click to expand...
Click to collapse
This worked for me the first time. Pretty much flash/reboot and you're done... no separate APK, no extra reboot to install the driver. I'm somewhat amazed.
jljtgr said:
This worked for me the first time. Pretty much flash/reboot and you're done... no separate APK, no extra reboot to install the driver. I'm somewhat amazed.
Click to expand...
Click to collapse
I can only imagine that whoever made this ZIP removed the need for the driver? I'm not quite sure either. But I scanned it for any malware or viruses and it is cleaned. Worked on the first flash and no bootloop so it seems to be legit.
I found mention of alpha versions of Viper being released elsewhere... I assume this is a product of that. I took a look at the scripts and it does mention moving native libraries around to various places and the embedded APKs and misc files looked similar to what I'd expect from the Android 10 version. It was just nice that the Magisk script did everything in one go instead of having to follow order-sensitive instructions with other Magisk modules then retrying the driver install until it stuck.
That said, the alpha thread said it cannot be used with the audio modification library module... bootloops to having your sim cards not be detected were reported until only Viper was installed.
Here is the alpha release post: https://forum.xda-developers.com/showpost.php?p=83525879&postcount=4371
The YouTube link has a matching CRC to this one.
I flashed this one, but it's distorting my external speakers and is buggy, but it does process...so BE CAREFUL. This will get you there until a more stable version is out.
https://www.youtube.com/watch?v=ltbJryJT1gg&feature=youtu.be
SirAugustine said:
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
Click to expand...
Click to collapse
Working on LineagOS 18.1 on pixel 4a 5g. Thanks for the link.

Comdirect photoTAN app detecting root

Since version 8.3.0 additional measures to detect root have been added, do not update as MagiskHide won't be able to prevent detection. Until a solution is found I would recommend staying on the previous version for as long as possible.
Finding out what exactly is causing the root detection is beyond my technical abilities but I would provide as much information needed to those willing to help.
---
Update: December 14th 2021 - Method no longer sufficient
---
The solution found by @pxrave appears to be working:
pxrave said:
Hey fellas I got it working and others apps detect magisk before.
Update to latest v23
Install modules riru and riru unshare
Remove data from tan app
Go to magisk hide and tick all process to hide included the isolated
Start the tan app and do the activation again.
Problem you need wait 2 days to activate because comdirect use new activation process for photo tan app.
Working fine all version 8.3
Click to expand...
Click to collapse
Link to the Riru Unshare module:
GitHub - vvb2060/riru-unshare
Contribute to vvb2060/riru-unshare development by creating an account on GitHub.
github.com
also stcpay yesterday is updated to 1.6 and started to detect my magisk canary (22105)
I can confirm what swour says.
on Android 9 and 11, my magisk root is recognized, magiskhide is active and the phototan app is added.
Yes this is a serious problem. I used xposed magisk and x privacy... Latest comdirect tan app detect all...
+1
+1 big issue for me
Only solution I found (for now): Go back to version 8.2.1 using a backup or any mirror, e.g. https://downloadapk.net/comdirect-photoTAN-App.html
Unfortunately you need to register again then
I have already applied the update. The easiest method is to wait few days for a magisk fix, right? I would can wait few days, no problem. I have an absolutly clean Android 8.1 build on the phone for banking. It's crazy that the bank is make it so difficult for us to use a save own build.
allrightlite said:
The easiest method is to wait few days for a magisk fix, right? I would can wait few days, no problem.
Click to expand...
Click to collapse
Perhaps that is too optimistic. I doubt that one app is of great interest
Asellus said:
one app is of great interest
Click to expand...
Click to collapse
Until the new root detection is also available for other apps, it will be fixed quickly.
Conan179 said:
Until the new root detection is also available for other apps, it will be fixed quickly.
Click to expand...
Click to collapse
Thanks, then I will easly wait. No need to reactivate hopefully.
Conan179 said:
Until the new root detection is also available for other apps, it will be fixed quickly.
Click to expand...
Click to collapse
Yes, of course, if other app developers find a similar way. So, congrats to the developers of the phototan app to find it.
Asellus said:
Yes, of course, if other app developers find a similar way. So, congrats to the developers of the phototan app to find it.
Click to expand...
Click to collapse
I don't think so, there is at least one other app that shows the same behavior.
new root dedction
i updated stc pay yesterday to 1.6 and it found my magisk canary (22105) the think i notes is the (isolated) is added to the app !!!
forum.xda-developers.com
I also noticed the (isolated) thing with me.
I tried with v23 this morning, w/o success :-(
Same here, got v23 and working safetynet-fix, no success. Downgraded photoTAN to v8.2.1 .
+1
I'm not surprised, there is nothing in the changelog that this has been fixed.
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
muschi.muscholini said:
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
Click to expand...
Click to collapse
I have a ZTE Blade L130 with the old photo tan app, that is my rescue. But you can't activate the old one. But it's keep working.
muschi.muscholini said:
Downgrading to 8.2.0 or 8.2.1 doesn't work for me. Did you do something else than uninstalling 8.3.0 and installing 8.2.1?
Click to expand...
Click to collapse
I had to unhide the app in magisk hide and hide it again, after that it worked.

[24.1] Magisk from User perspective - Safety check not working ??

Hi folks,
I got the new update 24.1 of my good old Magisk on top of my Lineage OS on payton device.
But I guess the safetynet check is gone and/or no more working since last update as of the banking app and also the game i.n.g.r.e.s.s is no more working..
What do I have to do in order to get back a positive safetynet check?
I have no much experiencies behind the scenes but all you are made a great job in your laisure time but please give me a chance to understand how and what must I configure to get working Magisk (MagiskHide and SafetyNet Check passed). Maybe there is a additional module that makes the SafetyNet check being passed.
Thank you
Tom
Tom_Scott said:
Hi folks,
I got the new update 24.1 of my good old Magisk on top of my Lineage OS on payton device.
But I guess the safetynet check is gone and/or no more working since last update as of the banking app and also the game i.n.g.r.e.s.s is no more working..
What do I have to do in order to get back a positive safetynet check?
I have no much experiencies behind the scenes but all you are made a great job in your laisure time but please give me a chance to understand how and what must I configure to get working Magisk (MagiskHide and SafetyNet Check passed). Maybe there is a additional module that makes the SafetyNet check being passed.
Thank you
Tom
Click to expand...
Click to collapse
Please consult this thread, especially first few posts:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Lord Sithek said:
Please consult this thread, especially first few posts:
Click to expand...
Click to collapse
Thank you for the answer, but I dont understand the thing being written in the discussion thread. Can you give a hint what do I have to do in order to solve the problem?
Thanks
Tom
Tom_Scott said:
Thank you for the answer, but I dont understand the thing being written in the discussion thread. Can you give a hint what do I have to do in order to solve the problem?
Thanks
Tom
Click to expand...
Click to collapse
Well... In short:
MagiskHide is gone now, replaced by Zygisk & DenyList. DenyList doesn't do any hide itself, but it can be used by additional modules to do it. SafetyNet check is also removed, but you can replace it by installing a checker from Play Store. Recommended one is YASNAC, search and install.
If you don't pass SafetyNet, first enable Zygisk & Enfoce DenyList, then go to Configure DenyList, tap on three dots in right upper corner and enable system apps. Then search for Google Play Services, expand the list of processes and mark com.google.android.gms and com.google.android.gms.unstable. [Additionally mark every app that search for root access]. Clear the data of Google Play Services and Google Play Store and check in YASNAC if you pass SafetyNet now. If not, download this module and flash in Magisk:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Then reboot and check SafetyNet again.
Usually this should be enough to pass SafetyNet, but if not, let me know, we can try another things. If you use official LineageOS, probably you will have to spoof the device's fingerprint, but... one thing at a time
As for bank apps (and some games too), it depends how much enforcements they use. If they rely only on SafetyNet, passing it will be sufficient to run them. But many bank apps use addtional measures to prevent running on rooted devices nowadays. But there are other workarounds which we can try if just passing SafetyNet isn't enough.
Thank you very much. Your guide enables passing the Safety Net check so I can use my special apps again.
In order to understand the new working principle: Please, can you explain what the DenyList denies? And do you know why the CTS check is gone?
Thank you very much
Tom
Tom_Scott said:
Thank you very much. Your guide enables passing the Safety Net check so I can use my special apps again.
In order to understand the new working principle: Please, can you explain what the DenyList denies? And do you know why the CTS check is gone?
Thank you very much
Tom
Click to expand...
Click to collapse
I think you should get familiar with the Topjohnwu statement on Magisk: https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458
Those changes were obviously well-thought and although they may look like a step back, they will allow to achieve much progress in time

"Hide the Magisk app" feature does not work.

Lately I upgraded to Magisk 24.1 from 23 and lost the usual stealth features then reverted back to 23 again. Everything works fine except for hiding the app. Now some apps detect root and don't work. When I use the feature an extra icon for Magisk named "Settings" is created that does not open the app. The original icon is not removed and opens the app like usual. If I leave it like that, I eventually lose root, then I have to uninstall the Settings app for Magisk to work again. I tried to uninstall and reinstall Magisk many times but still experience the same behavior. Something is clearly broken but I don't know how to fix it. Anyone faced the same problem or has any idea what to try?
if the feature doesn't work please try to contact me later thank you!
koryonp10 said:
if the feature doesn't work please try to contact me later thank you!
Click to expand...
Click to collapse
It does not work. I've been fighting with it for a couple days now.
ok so you need to try to restart your phone and if that doesn't work please try to email me at [email protected] i know a lot more than people think
also send me a video
The solution to your issue has been posted here: https://forum.xda-developers.com/t/rename-hide-magisk-not-working-for-v23.4396841/
Why do you want to downgrade though? v24.1 has denylist which works similar to magisk hide. All you need to do is install Universal Safetynet Fix (Magisk modules) and everything should work.
simplydat said:
The solution to your issue has been posted here: https://forum.xda-developers.com/t/rename-hide-magisk-not-working-for-v23.4396841/
Why do you want to downgrade though? v24.1 has denylist which works similar to magisk hide. All you need to do is install Universal Safetynet Fix (Magisk modules) and everything should work.
Click to expand...
Click to collapse
Worked a treat, thank you very much! Basically I downgraded because everything worked fine with the old version of Magisk and I didn't bother to search for a different solution. Is that the best module to pass Safetynet? I think I saw there's a few solutions available.
ser848 said:
Worked a treat, thank you very much! Basically I downgraded because everything worked fine with the old version of Magisk and I didn't bother to search for a different solution. Is that the best module to pass Safetynet? I think I saw there's a few solutions available.
Click to expand...
Click to collapse
Magisk 23 + Magisk Hide was detected by many bank apps I have and I was tired of dealing with it, so I decided to upgrade.
Magisk 24 + Universal Safetynet Fix + Shamiko worked like a charm and everything has been hidden and I have a feeling I won't have to deal with root hiding for a long time.
simplydat said:
Magisk 23 + Magisk Hide was detected by many bank apps I have and I was tired of dealing with it, so I decided to upgrade.
Magisk 24 + Universal Safetynet Fix + Shamiko worked like a charm and everything has been hidden and I have a feeling I won't have to deal with root hiding for a long time.
Click to expand...
Click to collapse
Thanks a lot again, I will give it a try.
koryonp10 said:
if the feature doesn't work please try to contact me later thank you!
Click to expand...
Click to collapse
koryonp10 said:
ok so you need to try to restart your phone and if that doesn't work please try to email me at [email protected] i know a lot more than people think
also send me a video
Click to expand...
Click to collapse
Hello and a very warm welcome to XDA, @koryonp10. I hope you'll always get the assistance you require, and much more we appreciate your intentions to provide your knowledge and expertise to other members. Thanks very much for that!
Please allow me to share with you the principle of this website:
XDA Developers was founded on the simple principle that SHARING IS GOOD and when many people SHARE what they know, EVERYONE benefits. We exist upon this ethos. We RESPECT each other, we SHARE with each other, we do not judge one another, and we HELP all who ask.
Click to expand...
Click to collapse
In order to live this spirit, I suggest to consider to publicly share your knowledge in the threads and not to drag the XDA members to your email, private messages or outside of XDA. Only from what you publicly posts, all can learn and are able to ask corresponding questions. Thanks very much for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
I have Magisk 24 + Universal Safetynet Fix + Shamiko installed on Android 11. It warns me that Shamiko not active as "denylist is enforced'. Regardless, I still get a warning message when I start my HSBC banking app.
simplydat said:
Magisk 24 + Universal Safetynet Fix + Shamiko worked like a charm and everything has been hidden and I have a feeling I won't have to deal with root hiding for a long time.
Click to expand...
Click to collapse
Hi, have read the changelog from magisk 24 that hide not included.
Saftynet Fix i think i have read this in past, i hope i find it. I have find this thread, but how get Shamiko?? And is Zygisk also needed?
At Moment i have HTC U11 with magisk 23 + riru lsexposed, because i need xprivacy.
richardmace said:
I have Magisk 24 + Universal Safetynet Fix + Shamiko installed on Android 11. It warns me that Shamiko not active as "denylist is enforced'. Regardless, I still get a warning message when I start my HSBC banking app.
Click to expand...
Click to collapse
Same issue here not on android 11 though.
richardmace said:
I have Magisk 24 + Universal Safetynet Fix + Shamiko installed on Android 11. It warns me that Shamiko not active as "denylist is enforced'. Regardless, I still get a warning message when I start my HSBC banking app.
Click to expand...
Click to collapse
Hi @richardmace have you fixed for HSBC Banking App? I had same issue
No, not fixed but not a major issue as app still works. I am now not enforcing the deny list and Shamiko is now active.
I am new to the subject but have similar issue. There is an medical application for diabetes in Google Play. It is called Freestyle Libre 3. "3" is important as there are "1" and "2" versions of this app. This app is used to monitor glucose with the help of external device that is placed on the body via bluetooth. The application has two "features" so far:
1) it is available only on a few smartphones (a few Apple's and a few Samsung's)
2) it is available only in few countries (GB, DE, NL, SE and just a few more)
All my bank apps work with zygisk but this medical app doesn't. I added this app and all google play services on deny list. YASNAC shows passed for basic integrity and cts profile. I tried Shamiko and Universal Safety Fix too. Hiding Magisk doesn't help. still no success. But once Magisk is uninstalled the app starts and works.
Could it be somehow an unusual case when application devs made up some one trick more than Magisk is assuming for apps that check for root? Is there any hope to have this app working on LineageOS with Magisk installed?
The working solution is to allow "USB Debugging" in "Developer options", and additionally by Xiaomi, turn off "MIUI Optimization".

Categories

Resources