Search Issue Tracker
Fixed
Fixed in 6000.0.39f1, 6000.1.0b7, 6000.2.0a4, 7000.0.0a19
Votes
11
Found in
6000.0.30f1
6000.1.0a7
6000.2.0a1
7000.0.0a12
Issue ID
UUM-90066
Regression
Yes
Sprite Atlas Override for iOS setting remains disabled when saving its change to enabled
Reproduction steps:
1. Open the attached “IN-89845_iOSOverrideIssue.zip“ project
2. In the Project window, select the “New Sprite Atlas“ Asset
3. In the Inspector window, select the iOS environment settings
4. Enable the Override for iOS setting
5. Press the “Pack Preview” button
Expected result: The Override for iOS setting is still enabled and the change is saved
Actual result: The Override for iOS setting is disabled
Reproducible with: 6000.0.24f1, 6000.0.30f1, 6000.1.0a7
Not reproducible with: 2021.3.46f1, 2022.3.53f1, 6000.0.23f1
Reproducible on: macOS Sequoia 15.1.1
Not reproducible on: No other environments tested
Comments (2)
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
- 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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
TeorikDeli
Dec 12, 2024 13:14
Using v1 and overriding iOS settings just before the build is the only "solution" I found so far. But when you reopen Unity, your settings will be reset. v2 is just doesn't work. This should be have a high priority. Building for iOS is really painful atm. I found that, this bug was a known bug since may '24 (6000.0.0f1). It's interesting that this bug found its way to an LTS version -_-
tcvpromo
Nov 28, 2024 12:13
please, fix it ASAP!