Search Issue Tracker
Duplicate
Votes
1
Found in
2019.2.17f1
2019.3.0b5
Issue ID
1211762
Regression
Yes
[iOS][2019.2][2019.3] Consecutive UnityWebRequests do not update after one UnityWebRequest has been completed
How to reproduce:
1. Launch the user-supplied project on Unity
2. Build the project for iOS
3. Launch the build on an iOS device through Xcode
4. Watch the device's screen
Expected result: all images on the screen turn green and say "Hello World!"
Actual result: only one image turns green and the rest are prevented from completion
Reproducible with: 2019.2.17f1, 2019.2.19f1, 2019.3.0b5, 2019.3.0f5
Not reproducible with: 2019.2.4f1, 2019.3.0b4, 2020.1.0a1
Could not test with: 2017.4.36f1, 2018.4.15f1, 2019.2.5f1, 2019.2.16f1
Notes:
1. I was not able to test on versions 2019.2.5f1 through 2019.2.16f1 due to another iOS bug featuring a pink device screen
2. Only reproduced in 2019.2-2019.2.19f1 and 2019.3.0b5-2019.3.0f5. Not reproducible in the entire 2020.1 stream
3. Could not test on 2018.4 and 2017.4 due to errors
Reproduced on:
iPhone 8 iOS 11.0
iPad (7th generation) iOS 13.2.2
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
This is a duplicate of issue #1195969