Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
4.2.2
Issue ID
ET-16
Regression
No
[2D Platformer] No texture data error is thrown when building and publishing
How to reproduce:
1. Create a new "2D Platformer Microgame" project
2. Publish > WebGL Project > Create and Publish New Build
Expected result: Build is finished with no errors and a new published build tab opens
Actual result: Build finishes but throws an error
Reproducible with: 2020.3.41f1, 2021.3.16f1
Could not test with: 2022.2.2f1, 2023.1.0a25
Reproduced on: M1 Max MacBook Pro (2021)
Full error:
{{No texture data is available to upload.}}
{{{}UnityEditor.BuildPipeline:BuildPlayer (UnityEditor.BuildPlayerOptions){}}}{{{}Unity.Play.Publisher.Editor.PublisherBuildProcessor:OpenBuildGameDialog (UnityEditor.BuildTarget) (at Library/PackageCache/com.unity.connect.share@4.2.3/Editor/PublisherBuildProcessor.cs:178){}}}{{{}Unity.Play.Publisher.Editor.PublisherWindow:OnWebGLBuildTargetSet () (at Library/PackageCache/com.unity.connect.share@4.2.3/Editor/PublisherWindow.cs:748){}}}{{{}Unity.Play.Publisher.Editor.PublisherWindow:OnCreateABuildClicked () (at Library/PackageCache/com.unity.connect.share@4.2.3/Editor/PublisherWindow.cs:509){}}}{{{}Unity.Play.Publisher.Editor.PublisherWindow/<>c__DisplayClass75_0:<SetupButton>b__0 () (at Library/PackageCache/com.unity.connect.share@4.2.3/Editor/PublisherWindow.cs:627){}}}{{{}UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&){}}}
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
- "Shader warning in 'Hidden/HDRP/DownsampleDepth'" warnings are thrown after building a project
- Scene is not rendered and appears black when the Custom Renderer Feature is utilized
- [ShortcutManager] The Context Menu is not updated in the Shortcuts menu when resolving a Binding Conflict
- [Quest] Foveation Level is 0 when SRP Foveation is enabled
- Freeze when displaying text with "-T" in Play mode
Resolution Note:
We could not reproduce this issue. After this issue was created we made some backend changes for Unity Play and currently don't see any related errors or additional issue reports. If it should occur again please let us know.