Search Issue Tracker
Fixed
Fixed in 6000.1.0b9, 6000.2.0a6
Votes
0
Found in
6000.1.0b7
6000.2.0a4
Issue ID
UUM-98072
Regression
No
Publish To Play process fails with Curl error 52: Empty reply from server
Steps to reproduce:
- Create a new project
- Switch to Web platform
- Press the Publish to Play button
- Select the attached "test" build
- Proceed to Publish the build
- Observe the Build publish progress window and the Console
Actual results: Build upload process fails towards the end and Curl error 52: Empty reply from server is thrown
Expected results: Build upload process to Play succeeds without issue
Reproducible with versions: 6000.1.0b7, 6000.2.0a4
Can’t test with versions: 2022.3.58f1, 6000.0.38f1 (Publish to Play button is not present)
Tested on (OS): Windows 11, macOS 15.3
Notes:
- Project build size - 663.71MB
- Uploading the build via the Unity Play website succeeds
Comments (1)
-
SharedRealities
Oct 05, 2025 20:06
Still getting this issue on 6000.2.6f2
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 6000.2.0a6):
The issue has been fixed in the cloud's backend
Fix verified on Mar 6th, 2025 using Unity Editor version 6000.2.0a6
Resolution Note (fix version 6000.1.0b9):
The issue has been fixed in the cloud's backend
Fix verified on Mar 6th, 2025 using Unity Editor version 6000.1.0b9