hi!
i was trying some of my old apps on grapheneos, including grindr.
i've had trouble passing the login/signup for that particular app.

initally the error just mentioned needing google play services,
but once i enabled that (in a new profile), alongside google play,
the app somehow still wouldn't have it, tho no more useful errors.

i'd wonder, might anyone else have encountered or even solved this?

    kiara Hello there!

    As far as I know, Grindr (like most apps) should work fine with Sandboxed Google Play.

    As a first step, I just want to make sure that you've set this up properly:

    1. Install all 3 Google apps from the "Apps" app on your phone.
    2. Open Play Store and click on "Sign in" to initialize Play Services (this is required even if you won't use Play Store to get your apps)
    3. After doing all of that, then install Grindr and see if it works.

    If you've already done all of that, or have now done it properly and the app still doesn't work, it may have a hard dependency on Play services geolocation APIs.

    Please follow the steps outlined here to do this:

    https://grapheneos.org/usage#sandboxed-google-play-configuration

    Specifically, this portion:

    By default, apps using Google Play geolocation are redirected to our own implementation on top of the standard OS geolocation service. If you want to use Google's geolocation service instead, you can disable the "Reroute location requests to OS APIs" toggle and manually grant "Allow all the time" Location access to Google Play services. For it to be fully functional, you also need to use "Google Location Accuracy" link to access the Google Play services menu for opting into their network location service. This will send the nearby Wi-Fi and cellular networks provided via the Location permission to their service to retrieve a location estimate. The Nearby Devices permission can also be granted to give it access to nearby Bluetooth device IDs. If you stick with the default enabled redirection mode, none of this needs to be granted for working geolocation in apps. In order to fully take advantage of Wi-Fi and Bluetooth scanning, you also need to enable the scanning toggles in Settings ➔ Location ➔ Location services which are disabled by default rather than enabled by default like the stock OS.

    If you do this and it still doesn't work, do one final sanity check of uninstalling and re-installing Grindr one more time and let us know if that doesn't fix it.

        MetropleX changed the title to App Compatibility: Grindr .
        17 days later

        spiral SETTINGS>APPS>SANBOXED GOOGLE PLAY>REROUTE LOCATION REQUESTS TO THE OS

          None of this worked for me. I also tried this in a completely freshly setup profile but I cannot get grindr to work.

            3 months later

            fgcle for those trying to use this on latest releases what issues persist or have appeared?

            Current compatibility mitigation options should ensure the app works fine so long as there arent any dependencies on ctsProfileMatch or Strict Integrity level for current APIs.

                MetropleX

                fgcle

                With Grindr I simply cannot log in to the app. Scruff, a similar app to Grindr, works perfectly without having to change any settings in GOS

                      spiral Thank you. But without Grindr mitigation to GrapheneOS doesn't work for me. That's unfortunate. :-(

                        MetropleX
                        To more accurately answer your question, I have not tried to use Grindr on a recent GOS build. I will give it another shot and report back exactly what happens.

                            spiral This would be really really AWESOME. Thanks so much.

                              You need to install apps depending on Google Play after you've installed Google Play. If you installed them before doing that, you need to remove and reinstall them. Make sure to install them from the Play Store if you want to minimize problems. If you install them from Aurora Store, make sure it's correctly configured to use the session installer since most modern apps on the Play Store use split packages and split packages are required for asset / feature delivery.

                                I actually tried to get Grindr to work a few days ago after reading this thread, but it didn't work for me. Didn't say anything because I had nothing valuable to add. Still don't, just lots of failure.

                                I tried on a fresh new profile. Installed all of GMS apps. Installed via Google Play. Logged in to Google Play. Also cannot log in or create an account on Grindr.

                                Granted literally every single permission to both Google Play Services and Grindr. Didn't work.

                                Enabled exploit protection compatibility mode. Didn't work.

                                Tried logging in using Google for single sign on. Grindr shows up in the connected apps, but still doesn't get past that point. Tried creating a user using email + password. Also didn't work.

                                Didn't try phone number or Facebook login because I'm not sure how I'd explain anything popping up to unwat's better half.

                                Checked logcat. Nothing helpful there.

                                  It would seem that if the need to give away all the "keys to the kingdom in" terms of permissions / security is required (and the app still doesn't work), ones threat model is of so little consequence that the use case for a hardened OS is unwarranted.

                                    Kamaehuakanaloa
                                    Not exactly. It's perfectly valid to want to use an app like Grindr, contained to its own profile which stays shut down when not in use. GOS is, in my opinion, perfect for this exact use case.

                                        spiral We will have to agree to disagree on this one. Using a native app like Grindr, for which there is no audited, FOSS alternative front end, is inherently insecure.