# Unable to build: Settings instance has not been initialized. Unable to continue build

**URL:** <https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668>\
**Category:** Unity\
**Created:** [December 20, 2022, 1:14pm UTC](https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668 "2022-12-20T13:14:01Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\
**Post date:** [March 16, 2023, 5:59am UTC](https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668/21 "2023-03-16T05:59:20Z")

</div>

Understandable, Unity only allow us to submit every 2nd update for verification. Our next release, 2.02.13, will hopefully be verified in the near future. Hope this helps!

---

<div class="post-metadata">

**Author:** ![sapfw](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@sapfw](https://qa.fmod.com/u/sapfw)\
**Post date:** [March 21, 2023, 8:59pm UTC](https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668/22 "2023-03-21T20:59:34Z")

</div>

Just updated FMOD Studio to 2.02.13. Using FMOD for Unity version 2.02.11. Still having the same bug.

When you refer to the version numbers do you mean FMOD Studio or FMOD for Unity plugin? I don’t see a more recent FMOD for Unity plugin on either the FMOD website or the Unity asset store.

Thanks for being so responsive!

---

<div class="post-metadata">

**Author:** ![sapfw](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@sapfw](https://qa.fmod.com/u/sapfw)\
**Post date:** [March 21, 2023, 9:14pm UTC](https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668/23 "2023-03-21T21:14:14Z")

</div>

p.s. also huge thanks to @erikdrsoftware above. the workaround seems to fix it!

---

<div class="post-metadata">

**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\
**Post date:** [March 21, 2023, 9:26pm UTC](https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668/24 "2023-03-21T21:26:00Z")

</div>

Hi,

The issue is with the Unity integration. We have submitted 2.02.13 to Unity for verification but that is an external process so it will take some time for it to be listed on the asset store. Hopefully, it will be processed soon and it will be listed on the asset store.

Hope this helps!

---

<div class="post-metadata">

**Author:** ![sapfw](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@sapfw](https://qa.fmod.com/u/sapfw)\
**Post date:** [March 24, 2023, 3:45am UTC](https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668/25 "2023-03-24T03:45:17Z")

</div>

Ok, thank you.

When you referred to the version number before I wasn’t sure if you were referring to FMOD Studio or the integration package. Now I got it 🙂

[Previous page](https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668.md?page=1)
