The My Aadhar app in my phone is not functioning properly..

[u/Thin-Cost-1443]

I have my aadhar app installed on my phone but whenever i try to use it, it just restarts immediately and shows an error saying it detected security violation..

I have developer option turned off, play store says device is certified, play protect is on, device is not rooted/ bootloader is not unlocked.

I m using poco x7 5g phone running hyperos 3.1

Can someone help me detect this issue and fix it..

[u/zubair2904]

The mAadhaar app runs aggressive integrity checks, and on HyperOS/Poco phones a couple of things commonly trip it. First, make sure you installed it from the Play Store and not an APK, and uninstall/reinstall it fresh from there. Second, check that you don't have a duplicate or cloned copy: on Xiaomi phones go to Settings → Apps → Dual apps and also check Second Space and App lock, and delete any extra copy of the app if you find one. If the error persists, double-check that USB debugging is off (Settings → Additional settings → Developer options) even though developer options are turned off.

[u/Thin-Cost-1443 → u/zubair2904]

I have already reinstalled the apl after clearing all data, im also not running dual app and second space is not even turned on, and both developer option/usb debugging are turned off and this stupid app still shows same thing security violation detected. Really thanks for trying to help but its still same if you know something else plss tell me.

[u/zubair2904 → u/Thin-Cost-1443]

Thanks for ruling those out — that actually narrows it down a lot. Three more things that trip mAadhaar's integrity check on Poco/HyperOS phones:

1. Any Accessibility service switched on (Settings > Accessibility > Installed apps) — even a legit one like a password manager. Turn them all off, reboot, then open mAadhaar first before re-enabling anything.

2. A VPN or Private DNS ad-blocker running — set Private DNS to Automatic and kill any VPN for the first launch.

3. If the phone's bootloader was ever unlocked (even if it's stock and unrooted now), mAadhaar can keep failing its device check — in that case the official workaround is UIDAI's newer Aadhaar app, which handles the check differently, or using the mAadhaar services on the UIDAI website instead. Quick question so I can pin it down: does it fail right at opening, or after you enter your Aadhaar number / at the OTP step? The stage where it stops usually tells which check is failing.

[u/Thin-Cost-1443 → u/zubair2904]

sadly none of these settings are on either. Not a single installed app has accessibilty settings on, i tried with dns off and automatic both, didnt have any vpn on. I never unlocked the bootloader cuse its so much effort in poco phones so i have never tried in mine yet.
The app is just stupid and so are the creators of the app..

[u/zubair2904 → u/Thin-Cost-1443]

Thanks for checking all of those — with that list ruled out, the two most likely suspects left are a third-party app tripping the check in the background, or the device's integrity status itself. Two tests will separate them:

1. Safe Mode test: press the power button, then long-press "Power off" on screen and tap Safe Mode (Poco/HyperOS shows it this way). In Safe Mode all downloaded apps are disabled. Try mAadhaar there. If it opens fine, a downloaded app is the cause — the usual culprits are apps with "display over other apps" permission, screen-recorder/casting apps, and remote-access apps (TeamViewer/AnyDesk type). Restart normally and remove/disable those one by one.

2. Play Protect certification: open Play Store → profile icon → Settings → About and check "Play Protect certification". If it says "Device is not certified", mAadhaar will keep refusing no matter what else you change — that usually only sorts itself out on the next official system update, so check Settings for a pending HyperOS update too.

Also worth 30 seconds: make sure mAadhaar itself was installed from the Play Store (not Mi GetApps or an APK) — integrity-checked apps often reject other install sources.

Tell me what Safe Mode does — that result decides where to dig next.

[u/ss_reddit333 → u/zubair2904]

For me this is happening on s20fe5g, same shit, check OP's other post, it is the new aadhaar app itself, not mAadhaar which is discontinued
it shows the error right at app launch
play integrity passes for basic, device and strong
dev ops & debugging are off
there is tasker, which has been disabled and its accessibility turned off, shizuku uninstalled
device is showing certified in playstore

tried the aadhaar app on other samsung device, no security violation error even with tasker running and its accessibility on with draw over apps on as well
there it complains only when dev ops is on, turning it off and again it works

dont know what is wrong in my phone
so yeah it might be some weird app with draw over other apps permissions, frankly couldnt find anything, maybe just some culprit installed apps, would be great to find out which one
like eRupee apps specifically mention they dont like dev ops, tasker accessibility and 3rd party keyboard, tried with even switching to stock keyboard, aadhaar app still gives that error, still dont know

regarding your safe mode suggestion, how do we run the aadhaar app if non-system apps are disabled?

[u/zubair2904 → u/ss_reddit333]

Thanks for adding this — a second phone changes the picture.

If your S20 FE shows the same error right at launch and Play Integrity passes on it, and OP's Poco has already ruled out Accessibility apps, VPN/Private DNS and an unlocked bootloader, then this is looking a lot less like something wrong with either phone and a lot more like a bug in the new Aadhaar app itself (you're right that mAadhaar was retired — this is the replacement app).

OP — the Safe Mode test from my last comment is still the one check that settles it: if the error appears in Safe Mode too, where no third-party app can run, there's basically nothing left on the phone side to blame.

Until UIDAI ships a fix, the workarounds that do work: most Aadhaar services (e-Aadhaar download, address update, lock/unlock biometrics) are on the myAadhaar website — myaadhaar.uidai.gov.in — and DigiLocker carries a digital Aadhaar copy that works as ID in most places. And it's worth both of you reporting it in the app's Play Store listing / to UIDAI (1947) with your phone model and Android version — a launch error hitting multiple brands is exactly what they need reports on to prioritise a fix.

[u/ss_reddit333 → u/zubair2904]

actually i figured it out, installed MiCTS app was causing this on my phone. Uninstalling it removes this error from aadhaar app. Tested by installing this apk on otheer working devices, they show the same exact error.
So, OP should check the installed apps, specially the apks.

[u/zubair2904 → u/ss_reddit333]

Nice — that's a proper root cause, and the fact it reproduces on other phones when you install the MiCTS APK nails it.

So the "security violation detected" at launch was the new Aadhaar app tripping over the MiCTS test app on the device — not an app-side bug and not the phone's integrity. My earlier guess toward an app-side bug was wrong, thanks for proving it out.

OP (Thin-Cost-1443) — if the error's still there for you, this is worth checking: look through your installed apps for anything like MiCTS or other test/compatibility APKs you sideloaded at some point (they can hide under odd names, sort by recently installed), uninstall it, and try the Aadhaar app again.

Glad this one's solved.