Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.5.0a5
Issue ID
UUM-132869
Regression
No
Asset's filename gets truncated at the last newline when exported and reimported as an Asset Package
How to reproduce:
1. Create and open a new 3D project
2. In the terminal, from the project’s root directory, run this command: “ touch $'Assets/filename\nwith\nnewline.txt' “
3. In the Project tab, right-click and select “Refresh“
4. Note down the file’s name
5. Right-click the created file and select “Export As Asset Package…”
6. In the pop-up window, click “Export…“, and note down where the package is exported
7. Delete the original file
8. Right-click in the Project tab and select “Import Package“ → “Custom Package…“
9. Select the package that was exported in step 6
10. In the pop-up window, click “Import”
11. Observe the imported file’s name in the Project tab
Actual result: The file gets reimported as “filename\nwith“
Expected result: The file gets reimported as “filename\nwith\nnewline.txt“
Reproducible with: 2023.1.0a4, 6000.0.66f1, 6000.3.6f1, 6000.4.0b5, 6000.5.0a5
Reproducible on: Ubuntu 22.04, macOS 15.5 (user)
Could not reproduce on: No other environment tested
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
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.