IssueTracker

Issue might be related to this internal issue to which I unfortuantely don't have access to (mentioned in commit cad0c4a).

We have passed this to the development team and will update this issue with more information as it becomes available.

I just realized that this is especially problematic in combination with the "hide private space" feature. On Pixel Launcher, when searching for "private space" always brings up the result "Private space: tap to set up or open". Internally, this is handled by unlocking the private space if it exists, or opening private space settings (and thus requiring authentication) if it doesn't. That means that for the user, these cases indistinguishable, and thus a third party with access to the phone can't know whether the user has a private space.

Since third-party launchers cannot open settings, it is distinguishable and this somewhat breaks the security of "hide private space".

I really hope you can resolve this issue in time for the final Android 15 rollout, especially since it should be a literal one-line change..

Unfortunately, there's yet another issue with private space for third-party launchers. Settings.Secure.HIDE_PRIVATESPACE_ENTRY_POINT is also marked as @hide. To work around this, I simply copied the settings key hide_privatespace_entry_point. This worked when testing the debug build of our launcher on the emulator, however, when installing a release build, it suddenly crashes with:

java.lang.SecurityException: Settings key: <hide_privatespace_entry_point> is not readable. From S+, settings keys annotated with @hide are restricted to system_server and system apps only, unless they are annotated with @Readable.

Ignoring the fact that the error message (or worse, the behavior) is incorrect, since it did work with a debug version of a non-system app, this is definitely problematic. Because third-party launchers cannot query the value of this system setting, they don't know when to hide the private space while it's locked. This noticeably degrades the user experience when using private space with a third-party launcher, and is unnecessarily confusing for our users.

What

Feature request

Yes, I also don't have the option to open private space using Microsoft Launcher

Where

Build and device data

- Build Number: google/shiba_beta/shiba:15/AP31.240617.015/12207491:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1

Debugging information
Google Play services
com.google.android.gms
Version 243433044 (24.34.33 (260400-666809342))
System App (Updated)

Android System WebView
com.google.android.webview
Version 666803142 (129.0.6668.31)
System App (Updated)

Network operator: Vi India
SIM operator: Vi India

Network operator: JIO 4G
SIM operator: Jio

Filed by Android Beta Feedback. Version (Updated): 2.44-betterbug.external_20240710_RC02 (DOGFOOD)
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

Information redacted by Android Beta Feedback.

Thanks. What about the "hide private space" system setting? Is the same planned for that?

Thanks for the quick reply, appreciate it! Looking forward to further updates.