Search Issue Tracker
Third Party Issue
Votes
0
Found in
2021.3.39f1
2022.3.33f1
6000.0.6f1
Issue ID
UUM-73641
Regression
No
[Android] Resources aren't loaded when using multiple users feature
Steps to reproduce:
1. In the device go to Settings → System → “Multiple users” and enable “Allow multiple users”
2. Add and set up a second user if there’s not one
3. Switch to the second user
4. Open the “MultipleUsersBug” project
5. Select the device from the Run Device dropdown list and Build And Run
Expected result: shows “Resources Loaded” cube along with other GameObjects
Actual result: shows only the “Cube 1” GameObject
Reproducible with: 2021.3.39f1, 2022.3.33f1, 6000.0.6f1
Testing environment: macOS Sonoma 14.4.1 (Intel)
Not reproducible on: No other environment tested
Reproducible with devices:
VLNQA00460 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 14
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11 (has Multiple users feature)
Notes:
- If the project wasn’t built with “Build And Run” (like _adb install build.apk)_, it doesn’t upload the .obb files to the device, and the issue is reproducible with all devices
- Also reproducible with Guest user
- Couldn’t test with iOS as it doesn’t have Multiple users functionality
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
This is not the Unity problem. Separate users have isolated file spaces on the device and the second user can't read files from the main user storage. When installing an application for the second user using adb or from Unity (which also uses adb), OBB file gets copied to the file space for the main user and this looks like a Google bug. To check this just connect to the device and look at the "storage/Android/obb/com.DefaultCompany.sanitytest" folder in Internal shared storage for both users. Probably the same happens when the application is installed from Google Play. If copy OBB file manually to the device to "storage/Android/obb/com.DefaultCompany.sanitytest" for the second user as "main.1.com.DefaultCompany.sanitytest.obb", then the application starts working correctly.
We recommend to use AAB format instead of APK+OBB, because it works for the second user without problems.