Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.5.2f1
Issue ID
890784
Regression
No
[iOS] UnityWebRequest starts timing out with FuseSDK when app is returning from background
When FuseSDK is used in the project, after going to background a few times, UnityWebRequest begins timing out.
Steps to reproduce:
1) Open the attached project (OC).
2) Build for iOS.
3) Run on a device.
- FuseSDK begins logging status messages in the console.
4) Minimize the app.
5) Return to app.
- Return steps 4 - 5 until status messages are no longer logged in the console after returning to app (usually 6 - 10 times).
FuseSDK is continuously making WWW calls and logging connection status to Xcode's console. After going to background and back a few times, UnityWebRequest starts timing out - this is first indicated by the abundance of "Connection OK" GUI messages and followed by "Timed Out" messages after a few seconds.
Reproduced on:
2017.1.0a3, 5.6.0f1, 5.5.2p2, 5.4.5f1, 5.4.3f1, 5.4.1f1 (couldn't test 5.3 - no UnityWebRequest).
Tested on:
iPhone 7 iOS 10.3
iPod Touch iOS 10.2.1
iPad Air 2 iOS 8.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment