Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.4
2018.4.30f1
2019.4
Issue ID
1299203
Regression
No
[Android] Project crashes before loading the Scene when "Application.RequestAdvertisingIdentifierAsync" callback is used
How to reproduce:
1. Open the user's attached project "GetAdvertisingIdentifierRepro.zip"
2. Load the Scene "advertisingIdentifier"
3. In the Build Settings select "Add Open Scenes"
4. Build and Run the Project to an Android device
Actual result: The application crashes before loading the Scene
Expected result: The Scene loads without any issues
Reproducible with: 2018.4.31f1, 2019.4.18f1, 2020.1.0b11
Not reproducible with: 2020.1.0b12
Reproducible on:
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
VLNQA00004, Meizu MX5 (MX5), Android 5.0.1, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00333, Hmd Global Nokia 7 plus (Nokia 7 plus), Android 10, CPU: Snapdragon 660, GPU: Adreno (TM) 512
VLNQA00099, Google Pixel XL (Pixel XL), Android 9, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00052, Xiaomi MI MAX (MI MAX), Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
Notes:
- "Application.RequestAdvertisingIdentifierAsync" can be found in "AskForAdvertisingIdentifierAsync.cs"
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
Resolution Note (fix version 2020.2):
No longer reproduces in 2020.1.0b12, 2020.2.1f1, 2021.1.0b1 and 2020.2.0a2