Official Unity Remote Config packages "2.1.2" and "3.0.0-pre.4" are now available

Remote Config v0.3.1 is now available in the Package Manager. (original post date: 7/25/19)

Release Notes:

• Added long type support for settings
  
• Fixed bug that caused the Remote Config Management Window to not display correctly after a domain reload.
  
• Added slider control for rollout percentage on rules
  
• The UI will now properly recover from any server-side errors.
• The UI will now reject duplicate rule names rather than depending on the Service API
• Moved Remote Config configuration requests to new URIs in the API Gateway
• Removed reliance on API Gateway URL that needs `-prd` at the end.
• The "All Users" pseudo-rule, is now named what it actually is, "Default Config."

 

Remote Config v0.3.2 is now available in the Package Manager. (original post date 8/7/19)

Release Notes:

• The input field on each setting is now the type of that setting, so developers don't have to worry about having incorrect values.
  
• Added warning when a setting key name reached 255 characters.

 

[1.0.7 Preview] - 2019-10-14
We're currently promoting the 1.0.7-preview release of the package . You can install via the Asset store or the Services Window. Here's what's going out with it:

• Boolean checkbox is now a dropdown with True and False
• The "Rollout Percentage" slider label is now an editable text field as well
• Added support for more unity attributes: unity.cpu, unity.graphicsDeviceVendor and unity.ram
• Fixed floating point rounding issue
• The editor window now saves the last fetched environment, configs and rules on editor close, and on playmode enter

 

[1.0.8 Preview] - 2019-10-29

We just shipped a 1.0.8-preview release, here are the release notes:

• Fixed bug where RemoteConfigDataManager would try set the RemoteConfigDataStoreAsset dirty when it doesn't exist
• Added documentation for unity.model predefined attribute
• The Remote Config window now supports having duplicate setting key names, but the backend will still reject duplicate setting keys.
• On a failed push to servers, the Remote Config window will re-fetch everything, so that users see the state of their environment on the server.
• Added a button to the Remote Config window that will take you to the Remote Config dashboard
• Now the release environment will have "Default" next to it in the environment dropdown.
• The cursor now turns into an editing cursor when hovering over editable fields in the Remote Config window.
• Fixed bug on Windows which would cause the name of a rule to wrap onto the lower line when the Remote Config window is small.

 

As mentioned in the previous post regarding locale settings, can you share your specific values?

 

Are you calling ConfigManager.FetchConfigs? This is also probably causing the other symptoms.

The user and app attributes are custom structs that you can use to provide attributes for rule conditions. I can provide an example implementation if that's helpful.

This is a bug with the 1.0.6 package. It's since been addressed in subsequent preview package updates. Can you try one of the newer versions and see if this solves the issue? 1.0.8-preview.1 is going through the verification process now.

 

No differences, other than how they're accessed in a rule's condition (user.[attribute], app.[attribute]). We de-coupled them due to some feedback from developers who wanted app attributes that stay the same across a session, but user attributes that may change.

If you have thoughts on that though, it'd be valuable feedback for us!

 

Got it, we'll look into this right away.

 

For proper tracking, it would probably be best to open separate threads for each issue/request. Thanks!

 

This is the v1.2.0-preview release of Unity Remote Config

• The configs and rules for a config are now displayed separately, and appropriately labeled.
• Added support for Variant rules in the Remote Config GUI.
  • Added a rule type dropdown next to the rule name, use this to change between segmentation and variant rules.
  • NOTE: When switching from a variant rule to a segmentation rule, it will result in a loss of local changes to variants.
  • Updates to the settings table for variant rules:
    • Added an

      Add Variant

      button that will add a variant.
    • Each variant has a name, and a variant weight.
    • The weights are

      null

      by default, which will result in a even balancing on the backend at time of assignment.
• Added a public get to

  config

  as a

  JObject

  to

  RuntimeConfig

  , so entire config can be retreived as a

  JObject

  .
• Added a "Select All" button to the variant rules settings view that will add all settings to the rule.
• A slew of UI stability fixes and refactors.

 

This is v1.2.0-preview.1 release of Unity Remote Config

• Fixed a bug where configId and environmentId were not pushed on creating / updating the rule.

 

This is v1.2.0-preview.2 release of Unity Remote Config

• Refactored the settings tree view into its own public class, so it can be used to create custom GUI.
• All tree view columns should now autoresize by default.
• Added confirmation dialog when switching from rule type 'variant' to 'segmentation'
• Made Unity.RemoteConfig.Editor.RemoteConfigWebApiClient a public class.
• Config object in RuntimeConfig class gets initialized on creation- Package now exposes all server errors as warnings in the console
• Moved the checkbox to add a setting to a segmentation rule to the left side of the treeview for consistency.
• Now the Remote Config window will block you from changing key names, types, and deleting settings that are being used in a rule to mimic the backend APIs.

 

Hello! We’ll begin posting regular updates with release notes again starting today. With the launch of Unity Gaming Services, we now have 2 main Remote Config Package streams that we will provide updates and release notes for:

1. Our “standalone” Remote Config 2.x version stream [@2.1.2] which will be available as default in 2022.2
   How to install Remote Config specific versions depending on your editor version: Install 2.1.2 Verified Remote Config
2. The 3.x version which is part of Unity Gaming Services (UGS) [@3.0.0-pre.4].

The 2.x release stream will be our main supported version, whereas the 3.x stream will include more experimental updates in combination with the new UGS beta services. Please note that there are new dependencies in 3.x for the Core and Authentication packages, which are now inherited in Remote Config for that release stream (initialization instructions linked below).


v2.1.2 release of Unity Remote Config

• Updates to Package Docs
• Bug fix to address editor memory leak

2.1.2 Package Docs


v3.0.0-pre.4 release of Unity Remote Config (as part of UGS)

• Updated com.unity.remote-config-runtime dependency to 3.0.0-pre.10
• Fixed links in Documentation, and updated integration guides
• Updated ExampleSample
• Removed unneeded APIs Docs with Docs Flag

3.0.0-pre.4 Package Docs and Upgrade Notes
New UGS Core and Auth Initialization

 

Verified in Package Manager does not imply production ready, it represents our internal validation process which takes time. Our updated versions typically address fix bugs in previous versions, so you would be advised to use the latest version and test in your app.