Peter-Easton
commented
2 years ago This issue has been resolved in Build SQ1D.220205.004.2022022818.
Marking as resolved.
Closed Peter-Easton closed 2 years ago
Peter-Easton
commented
2 years ago This issue has been resolved in Build SQ1D.220205.004.2022022818.
Marking as resolved.
thestinger
commented
2 years ago I don't think anything was resolved but if it's not easily reproducible it's best to close it. It wouldn't be a GrapheneOS issue but rather an AOSP profile issue anyway. We cannot realistically track AOSP issues as a whole on our tracker and we're going to need to start closing those.
Test of Initialization of Play Services in Second Profile
Equipment
Procedure
Control
As a control to ensure the trustworthiness of the test, the test was first done using the owner profile.
The GrapheneOS app store
app.grapheneos.apps(Version 1) was first downloaded from Github and installed in the owner profile. Numerous other apps have already been installed in the profile and the profile has been used for calls, texting, internet browsing, pictures and other typical use cases for a smartphone.Once installed, Sandboxed Play Services was then installed in the Owner Profile through the GrapheneOS app store by selecting "Google Play Store" which lists "Google Services Framework" and "Google Play Services" as dependencies, and tapping "Install All." The installation was allowed to complete.
A previously registered, disposable Google Account enrolled in the Google Advanced Protection Plan using 2 Yubikeys was then signed into on the device by opening Play Store and following the on screen instructions. When prompted to, the Yubikey was placed on the back of the phone.
Once sign-in was verified to be working, the apps were then removed from the owner profile.
Test
A second profile was created using the Multiple Users settings menu, and switched to. A password was set, and two fingerprints registered with the phone using the launcher. Location Services was switched off.
The GrapheneOS app store
app.grapheneos.appswas then installed, and Play Services was installed the same way it had been installed in the Control setup.The installation was allowed to complete.Play Store was then opened and a sign-in was then attempted.
Expected Results
Play Store would allow for a sign-in, as per control.
Observed Results
After the account name and password was entered, the Yubikey was prompted for. While using the Yubikey via NFC, the phone accessed the Yubikey multiple times before it could be taken away. Vanadium was observed to be opened automatically and directed to go to the Yubikey demonstration website.
When Vanadium was closed, Play Store was opened again and displayed the Sign In page. Attempting to sign into the accounts ended at the 2FA page, where further attempting to use the Yubikey simply caused Vanadium to open the Yubikey demonstration website.
Play Services, Play Store, and Google Services Framework were then Force Stopped via the Apps menu, then allowed to reopen, which allowed Play Store to open to the splash screen showing the Play Services logo.
USB debugging was enabled in the owner profile along with Wireless Debugging and the phone connected to the computer to collect logcat. Logging was then started, Play Services was opened again to the splash screen, and the following logs collected.