Search Issue Tracker
Fixed in 1.0.9
Votes
0
Found in [Package]
1.0.0
Issue ID
1180267
Regression
No
[Remote Config] User can enter invalid characters into value fields
[Remote Config] User can enter invalid characters into value fields
When configuring rules, if the user chooses a type limited by input such as an Int or Float, the value field will prevent the user from entering alphabetic characters, but not prevent symbols from being entered. This is then properly sanitised when pushing/pulling, however what the user will see is no longer synchronised the pushed data and they may not be aware of a erroneous value being submitted.
Steps to reproduce:
- Create and open a new project in Unity 2019.3 (+) or download the attached project
- If in a new project, install the Remote Config package via Package Manager (it may be a preview package)
- Window > Remote Config Management
- Under any environment, add a new rule ("Add Rule") and configure it as an Int type value
- In the value field, enter numeric characters, observing they are accepted
- In the value field, enter alphabetic characters, observing they are blocked
- In the value field, enter other symbolic characters ($%^&*@!), observing they are accepted though they do not represent a valid Int value
- "Push" the values, observing it appears to have pushed with no issues
- Observe the value field set previously still reflects the same value
- "Pull" values back from the server, observing the actual sanitised value now appears in the field
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment