Search Issue Tracker
Fixed
Fixed in 1.5.2
Votes
0
Found in [Package]
1.5.1
Issue ID
LOC-909
Regression
No
Data from Google Sheets are pulled incorrectly when starting values are reversed in the Editor
Reproduction steps:
1. Open the attached project “GoogleSheetsBug“
2. Select the Table “Assets/Table/Test Table 1”
3. In the Inspector window press the “Pull” button
4. In the Inspector window press the “Open in Table Editor” button
5. Observe pulled values
Expected result: The table contains correct values (Cow → Moo, Cat → Meow)
Actual result: The values are pulled incorrectly (Cat → Moo, Cow_2 → Meow)
Reproducible with: 1.3.1 (2021.3.19f1, 2022.2.8f1), 1.4.0-exp.1 (2021.3.19f1, 2022.2.8f1, 2023.1.0b6, 2023.2.0a5), 1.4.3 (2021.3.19f1, 2022.2.8f1, 2023.1.0b6, 2023.2.0a5)
Reproducible on: Windows 11
Note: Pulling the data for the second time works correctly
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment