Search Issue Tracker
Fixed
Fixed in 4.2.4
Votes
0
Found in [Package]
4.2.2
Issue ID
ULOB-20
Regression
No
Remote Config asset throws Deployment package version warning when "View in Deployment Window" is clicked
How to reproduce:
1. Open the “IN-120004” project
2. Right-click in the Project window and select Create > Services > Remote Config
3. Select the Remote Config asset and in the Inspector window click “View in Deployment Window”
4. Observe the Console
Expected result: Nothing appears in the Console
Actual result: A Console log appears: “[RemoteConfig]: Please update your Deployment package to use this feature. A minimum version of 1.4.0 is required.”
Reproducible with: 4.1.1 (6000.3.0b10), 4.2.2 (6000.2.12f1, 6000.3.0b10, 6000.4.0a4, 6000.5.0a1)
Could not test with: 6000.0.62f1 (Compilations errors)
Reproducible on: macOS Tahoe 26.0.1, Windows 11 (by user)
Not reproducible on: no other environments 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
- 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 (fix version 4.2.4):
The assembly definition was missing a conditional define to say that it is using deployment window 1.1