{"id":44767,"date":"2023-04-17T22:18:27","date_gmt":"2023-04-17T16:48:27","guid":{"rendered":"https:\/\/droidwin.com\/?p=44767"},"modified":"2023-04-17T22:18:27","modified_gmt":"2023-04-17T16:48:27","slug":"starling-banking-app-not-working-in-rooted-device-fix","status":"publish","type":"post","link":"https:\/\/droidwin.com\/starling-banking-app-not-working-in-rooted-device-fix\/","title":{"rendered":"Starling Banking App not working in rooted device [Fix]"},"content":{"rendered":"

In this guide, we will show you the steps to fix the issue wherein the Starling Bankip app is not working on rooted devices. Gaining administrative privileges by rooting the device via Magisk does open the gateway to a plethora of customizations. But on the flip side, it brings in a few uninvited guests as well, most noticeably the tripping of SafetyNet which will prevent any banking and payment apps from running on your device. Well, this isn’t something new and has been going on for ages.<\/p>\n

To bypass this limitation, all that you need to do is hide Magisk, flash the SafetyNet Fix module, and then hide the root from a few Google apps and services. However, for the past two days, this tweak isn’t working with the Starling Bankip app, as a result of which, users are unable to use it on their rooted devices. If you are also in the same boat, then this guide will make you aware of a nifty workaround to rectify this bug. Follow along.<\/p>\n

Starling Banking App not working on rooted devices<\/h2>\n

\"Starling<\/p>\n

The culprit behind this issue is the firebaseremoteconfig.googleapis.com<\/strong> API of Google. So to rectify it, you just need to block this site [apart from obviously passing the SafetyNet Test<\/a> beforehand].<\/p>\n

For that, you could use a third-party app like Block Site or block it on a DNS level via DNS Adguard, Adaway, etc. So carry out this tweak and it should fix the issue of the Starling Bankip app not working on rooted devices.<\/p>\n


\n