Plain Text Nostr

<-- back to main feed

thread · root 9e3ccb51…9152 · depth 2 · · selected e278e205…1042

thread

root 9e3ccb51…9152 · depth 2 · · selected e278e205…1042

GrapheneOS -- 2d [root] 
|    nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqqlhllz44qcejrz5ugufleuzj84nppdv5lgpv3ss67cpftzsres4svky27
|    4 Based on your other replies in the thread, you've resolved the issue already. Google misrepresents the feature
|    you enabled as a security feature when what it actually does is disallowing any device or OS not licensing
|    Google Mobile Services including integrating Google's Chrome web browser, etc. from installing your app.
|    GrapheneOS users can work around it by using another Play Store frontend as opposed to the sandboxed Play Store
|    but it's much better if apps avoid using that setting.
|    reply [2 replies]
GrapheneOS -- 2d
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqqlhllz44qcejrz5ugufleuzj84nppdv5lgpv3ss67cpftzsres4svky27
4 If your app want to make your app easily available outside of the Play Store, you can apply to publish it via
Accrescent which is a Play Store alternative available in the GrapheneOS App Store. It's currently in Alpha and
you need to apply to publish apps through it. See https://accrescent.app/ for more information.

Your app is easily available to GrapheneOS users regardless especially now that you fixed the Play Integrity API
store listing issue but you can support an alternative.
reply

Write a post

Sign in with a signing-capable method to publish.