Issue with "Allowlist config Urls"

[BarryCarlyon]

@drago

I hope this is my last question, the configuration saved using the back-end is not the same as the front-end’s.

Just to clarify

if you use the API or the JS helper to set the extension config service they should be the same.

You can choose not to use the config service and store information in your database instead.

@drago

• My app’s version is 0.0.1

The version of your extension is irrelevant.

@drago

On the front-end, I’m using: twitch.configuration.set(“broadcaster”, “1”, JSON.stringify(config))

You wrote to the config segment and said that it is version “1”

@drago

On the back-end, for fetching configurations, there is no version parameter.

The version is returned with the contents of the config.
It’s not a paramter it is “part” of the config

Reference

example response:

{
  "data": [
    {
      "segment": "global",
      "content": "hello config!",
      "version": "0.0.1"
    }
  ]
}

The extension config service only stores one item of configuration per segement.
That item of configuration may or may not have a version attached to it. Versions are used to block/allow activation of the extension into a slot.

You cannot “load” version “0.0.1” if you set a config of version “1” theres no history/way to load older configurations.

If you don’t want to block activation of an extension to force configuration first don’t use versioning.

I fear you are getting confused over the purpose of the version attached to the configuration.

If the version set with config matched the version set in the dashboard, allow activation.

That version can be a string of any format/content, even as simple as “ok” doesn’t need to be numeric.