Search Issue Tracker
Fixed
Fixed in 2021.3.25f1, 2022.2.19f1, 2023.1.0b16, 2023.2.0a13
Votes
0
Found in
2021.3.22f1
2022.2.15f1
2023.1.0b12
2023.2.0a10
Issue ID
UUM-32984
Regression
Yes
”ArgumentNullException: Array cannot be null” error is printed when passing an empty string to fileName of WWWForm.AddBinaryData and then access the data property
How to reproduce:
1. Open the user’s attached “WWWFormError.zip” project
2. Enter Play Mode
3. Observe the Console window
Expected result: “System.Byte[]” is printed
Actual result: “ArgumentNullException: Array cannot be null” error is printed
Reproducible with: 2021.1.0a1, 2021.1.28f1, 2021.3.22f1, 2022.2.15f1, 2023.1.0b12, 2023.2.0a10
Not reproducible with: 2020.3.47f1, 2020.2.0b3
Reproduced on: macOS 13.2.1 (Intel)
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
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
Resolution Note (fix version 2023.2.0a13):
Fixed in: 2023.2.0a13
Resolution Note (fix version 2023.1.0b16):
Fixed in: 2023.1.0b16
Resolution Note (fix version 2022.2.19f1):
Fixed in: 2022.2.19f1
Resolution Note (fix version 2021.3.25f1):
Fixed in: 2021.3.25f1