Just to wrap up our private conversation here back in the main thread.
It looks like you had set up a temporary site config, perhaps it was unintentionally set up as a site config, i.e. you just left off the project by mistake. That config was pointing to a gitrepo which contained a config, which probably had its core_api.yml
set to use 168
.
Once you trashed that config, and restarted Desktop, it reverted to using the automatically updating config, which has a core of 172
and so the setup wizard started working again.
I didn’t change anything, I think it was the deletion of the site config that fixed it.
To break it down a bit here, you had
- A project that had not been setup before, and you were wanting to run the advanced setup wizard on it.
- You encountered the error saying the config required core,
v018.172
, but you were runningv0.18.168
. - What the error meant by "You are running version
v0.18.168
" was that Shotgun Desktop’s config was running on corev0.18.168
. - Shotgun Desktop as a whole uses a “site” config, which is a
PipelineConfiguration
entity with noProject
assigned. This config is where it gets the core version it is uses for general SG Desktop operations. - As soon as you enter a project in SG Desktop that has been set up with its own config, and launch apps, it will not use the site config/core, and will use the project’s config/core.
- You had a custom site config. Although I couldn’t see the files, I assume it used the older core
v0.18.168
. - So as soon as you trashed the site
PipelineConfiguration
entity and restarted desktop, it went back to using the default site config, which is whatever the latest version oftk-config-basic
is defined in our app store.
I hope that helps explain, but it sounds like it’s all sorted for you now, sorry for the confusion.
Cheers
Phil