Search Issue Tracker
Won't Fix
Votes
0
Found in
Core-1.0.1
Issue ID
UUM-137185
Regression
No
[Ubuntu] CSV importer for Platform Toolkit's Achievement Editor does not detect CSV files
Steps to reproduce:
- Open the attached project
- In the Achievement Editor window, press the Export button
- Name the file and export the Saves
- Press the Import button
Actual results: No CSV files are shown in the File browser
Expected results: CSV files are shown in the File browser, including the file exported in step 2
Reproducible with versions: 1.0.0, 1.0.1 (6000.3.11f1, 6000.4.0b12, 6000.5.0a9, 6000.6.0a1)
Can’t test with versions: 6000.0.70f1 (Package is not supported)
Reproducible on (OS): Ubuntu 22
Not reproducible on (OS): macOS 26.3.1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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:
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.