Search Issue Tracker
In Progress
Under Consideration for 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X
In Progress in 6000.4.X
Votes
0
Found in
2022.3.67f1
6000.0.58f1
6000.2.6f1
6000.3.0b3
6000.4.0a2
6000.5.0a1
Issue ID
UUM-120143
Regression
No
[Android] Addressables Web Requests Fail with a "2363380-Download Handler Error"
Reproduction steps:
1. Open the attached “IN-115345” project
2. Open the Android Logcat (Window > Analysis > Android Logcat)
3. In Build Settings (File > Build Settings), enable Development Build
4. Build and Run the Android Player
5. In the Player, write “256” on the input text field
6. Hit the “Start Downloading” button
7. Wait until the download finished log appears
8. Observe the Android Logcat
Expected result: No "2363380-Download Handler Error" error messages appear
Actual result: A "2363380-Download Handler Error" error message appears
Reproducible with: 1.27.0 (2022.3.66f1)
Couldn’t test with: 2.0.3, 2.7.2 (6000.0.58f1, 6000.2.4f1, 6000.3.0b2) (The project is using a custom 1.27.0 Addressables package)
Reproducible environments: macOS 15.6.1
Not reproducible environments: No other environments tested
Reproducible with these devices:
VLNQA00521 - Galaxy S22 Ultra USA (SM-S908U), CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno 730, OS: 14
VLNQA00403 - Galaxy Z Flip3 5G (SM-F711B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00460 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 14
Not reproducible with these devices:
VLNQA00641 - Google Pixel 9 (Pixel 9), CPU: -, GPU: Mali-G715, OS: 15
VLNQA00372 - Galaxy S21 5G (SM-G991U), CPU: Snapdragon 888, GPU: Adreno 660, OS: 12
VLNQA00519 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
Couldn’t test with these devices:
VLNQA00336 - HUAWEI Y6p (MED-LX9N), CPU: MediaTek MT6762R, GPU: PowerVR Rogue GE8320, OS: 10 (Device-specific logging issues)
VLNQA00325 - Galaxy Note 10 Global (SM-N970F), CPU: Exynos 9 Series 9825, GPU: Mali-G76, OS: 12 (Network issues on the device)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Open” button in Inspector does not function for certain Assets
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
Add comment