Search Issue Tracker
By Design
Votes
0
Found in
5.5.3f1
Issue ID
921325
Regression
No
[Android] For checking and loading .obb file on device is necessary to restart the app or make the pause and resume processes
Reproduction steps:
1. Open the attached project;
2. Check if "Split Application Binary" in Player Settings is checked;
3. Build the project on the device;
4. In the app click a button "WRONG NAME" and then a button "Open Next Scene" (the app crashes);
5. Open the app, in there click a button "PROPER NAME" and then a button "Open Next Scene";
Actual result: the second scene is not loaded.
Expected result: the second scene should be loaded.
Note: the second scene is loaded when before pressing a button "Open Next Scene", the app is minimized and then maximized (it goes like pause and resume processes). After the pause and resume processes, Unity automatically checks if .obb file is available and loads it. However, there is no method in Unity which checks and loads .obb file when it is available, without making the specific pause and resume processes.
Reproduced with: 5.5.0b1, 5.5.4p1, 5.6.2p2
Cannot be tested with 2017.1 and 2017.2 versions because the app crashes. The crash is caused by enabling "Split Application Binary" setting and choosing Gradle (New) in Build System. Also, cannot be tested with 5.4 because there is no Build System setting.
Devices under test:
Verizon SM G930V, OS:6.0.1, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:Verizon/heroqltevzw/heroqltevzw:6.0.1/MMB29M/G930VVRU2APG3:user/release-keys
Lge LG H340n, OS:5.0.1, CPU:armeabi-v7a, GPU:Adreno (TM) 306, Build:lge/c50n_global_com/c50n:5.0.1/LRX21Y/151672304cd28:user/release-keys
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
megatonmedia
Nov 19, 2017 00:10
By design? So what's the proper way of dealing with the OBB files on first execution of app? Do we call Application.Quuit() the first time we run an app on android?