- Edited
Screenshot Link: https://pasteboard.co/o1SGAnaLvN43.png
Google Play Link: https://play.google.com/store/apps/details?id=com.teamblind.blind&hl=en_IN&gl=US
As soon as I open the app I see the screenshot. Any idea what could be the issue?
Screenshot Link: https://pasteboard.co/o1SGAnaLvN43.png
Google Play Link: https://play.google.com/store/apps/details?id=com.teamblind.blind&hl=en_IN&gl=US
As soon as I open the app I see the screenshot. Any idea what could be the issue?
codingcoffee Try the following:
I believe what's happening here is that the app is noticing something different happening as a result of secure app spawning and refusing to run based on that.
Relevant issue on the tracker here: https://github.com/GrapheneOS/os-issue-tracker/issues/1908
Whether you'd like to disable secure app spawning system-wide to make this app work is up to you. Disabling it doesn't make things less secure than Stock OS, but secure app spawning brings a major security benefit and minor privacy benefit, so choose accordingly.
[deleted] i think I'll agree with your assessment of the apps. But I was still curious as to what was causing the issue to begin with. And they are not 2 separate apps. I think Blind app includes the LIAPP sdk which is causing the ruckus.
@matchboxbananasynergy I have already tried what you recommended, and it was still throwing the error. So I don't think the secure app spawning is being flagged, but something else is triggering the issue. So I was curious as to what could've been the problem.
Regardless, I think it's best to ignore the app, and just go about using the web versions of the app for now.
Thanks everyone!
codingcoffee But I was still curious as to what was causing the issue to begin with
You are right. If I could I would delete my comment. I think that the point could be valid but the phrasing and stress on permissions and trackers barely answer your question, and I realized too late that simply asking a question doesn't need to correspond with any opinion on the subject.
[deleted] As per your request, I've deleted your post above.
codingcoffee I know you've said that you won't be using the app, but I'm still trying to figure this out just to know what's happening here.
Can you confirm whether this was on the owner or a secondary user profile?
After further testing with other members in the Matrix community, it seems that disabling secure app spawning makes the app work fine in the Owner profile.
In secondary profiles, the app works if you disable secure app spawning, reboot the phone and then force stop the app and clear its cache and storage, but I don't know if that would actually stick.
It seems that the most optimal way to use it is to disable secure app spawning and use it in the Owner profile. Whether you wan to do that or not is another matter.
matchboxbananasynergy it was on the owner's profile for me.
I think I had missed clearing of the cache and storage, which is why disabling secure app spawning still didn't make the app run for me. Just confirmed the same, and it's working now!