How do I stop google play store from trying to manage apps installed in non-GPS Owner profile but made available in second user profile with GPS?

    axino
    If I'm understanding correctly, you want GPlay to stop updating apps across profiles? You can't. That's how app updating works on Android due to downgrade protection.

        Dumdum
        I'm not sure that's the issue I'm seeing initially. I have two different profiles, with separate instances of GPS.
        The apps installed as owner via apk, aegis and proton, I made "avaialble from owner profile" in both prior to GPS.
        One profile, GPS didn't install them, they say installed via file, but it is trying to manage and update them.
        The other profile, they aren't being picked up by GPS at all, even tho they were also made available from owner profile.
        I just created a 3rd profile to check.

        From what you're saying, if I let GPS update them in Profile1, the owner profile will even see the update? I thought all profiles were siloed. Owner profile does not have GPS installed.

        • de0u replied to this.

            axino I thought all profiles were siloed.

            No, in many ways. Two profiles on the same device are in the same time zone, share the notion of time, have the same battery percentage level, etc.

            In this case, while two profiles have different app data for each app, the code of the app itself is shared. If any profile updates an app, the app is updated in all profiles.

                de0u
                Understood, thank you. But why does only Profile1 with GPS try to manage apps that exist in play store, and not Profile 2?
                This is the biggest confusion for me. Two profiles, different google accounts, similar setups on the surface.

                    axino Why does only Profile1 with GPS try to manage apps that exist in play store, and not Profile 2?

                    There I am unable to help (I don't use Google Play).

                      axino Apps can be installed or not installed in a given profile, but the packages for apps installed in any profile are share among any profiles with the same app installed. This is based on package name. The OS package manager enforces that an update must have the same signing key and an equal or greater version. Key rotations can be authorized but only newer Android versions support those so generally you'd still keep signing the package with the old key used by older Android versions until you no longer supported them by raising the minimum supported version to the point key rotation is fully supported by every OS version.

                      Package name is meant to uniquely identify a published build variant, with no reuse for different build variants such as a Play Store vs. non-Play-Store build variant, but many app developers violate this guideline and cause confusion for their users by not using separate package names.

                      Does this help you?