# Known issues for 2.02.05

**URL:** <https://qa.fmod.com/t/known-issues-for-2-02-05/18331>\
**Category:** Known Issues\
**Created:** [February 8, 2022, 12:49am UTC](https://qa.fmod.com/t/known-issues-for-2-02-05/18331 "2022-02-08T00:49:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/andrew/32/261_2.png) [@Andrew](https://qa.fmod.com/u/Andrew)\
**Post date:** [February 8, 2022, 12:49am UTC](https://qa.fmod.com/t/known-issues-for-2-02-05/18331/1 "2022-02-08T00:49:03Z")

</div>

**Issue**  
A crash bug was found after release that affects all FMOD 2.02.05 products.

**Solution**  
This issue has been fixed and patched versions of all FMOD 2.02.05 products are available on the Download page.

---

<div class="post-metadata">

**Author:** ![doomedbunnies](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/doomedbunnies/32/3115_2.png) [@doomedbunnies](https://qa.fmod.com/u/doomedbunnies)\
**Post date:** [March 8, 2022, 5:15am UTC](https://qa.fmod.com/t/known-issues-for-2-02-05/18331/2 "2022-03-08T05:15:23Z")

</div>

This is kind of late query, but…

Is there a way for us to tell the difference between a broken already-downloaded 2.02.05 build and the newer fixed 2.02.05 build?

We had already upgraded to 2.02.05 before the bug fix and so it was already on our build machines. After the bug was announced, we downgraded back to 2.02.04 because that was the only way we could think of to be sure we absolutely had the broken version of 2.02.05 entirely out of our whole build pipeline; the fixed 2.02.05 shows the same values in `FMOD_VERSION` and returns the same results from `FMOD_System_GetVersion()` as the broken release did, so there was no reliable way for us to verify that we’d actually updated every build machine and every platform that needed to be updated.

Do you have any guidance for how we can better handle this sort of situation in the future?

---

<div class="post-metadata">

**Author:** ![Andrew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/andrew/32/261_2.png) [@Andrew](https://qa.fmod.com/u/Andrew)\
**Post date:** [March 17, 2022, 11:49pm UTC](https://qa.fmod.com/t/known-issues-for-2-02-05/18331/3 "2022-03-17T23:49:51Z")

</div>

Look in doc/revision.txt :

20/12/21 2.02.05 - Studio API minor release (build 122665) ← Unpatched. Don’t use it.  
4/2/22 2.02.05 - Studio API minor release (build 123444) ← Patched. You can use it.

Or get 2.02.06 which has just been released.

---

<div class="post-metadata">

**Author:** ![doomedbunnies](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/doomedbunnies/32/3115_2.png) [@doomedbunnies](https://qa.fmod.com/u/doomedbunnies)\
**Post date:** [March 18, 2022, 4:28am UTC](https://qa.fmod.com/t/known-issues-for-2-02-05/18331/4 "2022-03-18T04:28:03Z")

</div>

Thanks! Is there an API to access that build number at runtime?

(we’ll be upgrading to 2.02.06 just as soon as we’re out of code lockoff for our current update)

---

<div class="post-metadata">

**Author:** ![Andrew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/andrew/32/261_2.png) [@Andrew](https://qa.fmod.com/u/Andrew)\
**Post date:** [March 22, 2022, 5:37am UTC](https://qa.fmod.com/t/known-issues-for-2-02-05/18331/5 "2022-03-22T05:37:28Z")

</div>

Currently there’s no way to access the build number at runtime. I think we’ll fix that for a future release. For now, you can see the build number at the top of the fmod log file in a logging build.