# 1.10.01 - SetParameterValuesByIndices missing in iOS libraries

**URL:** https://qa.fmod.com/t/1-10-01-setparametervaluesbyindices-missing-in-ios-libraries/13516
**Category:** Unity
**Created:** [November 3, 2017, 10:21am UTC](https://qa.fmod.com/t/1-10-01-setparametervaluesbyindices-missing-in-ios-libraries/13516 "2017-11-03T10:21:32Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![r618](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/r618/32/36_2.png) [@r618](https://qa.fmod.com/u/r618)
#### Post date: [November 3, 2017, 10:21am UTC](https://qa.fmod.com/t/1-10-01-setparametervaluesbyindices-missing-in-ios-libraries/13516/1 "2017-11-03T10:21:32Z")

</div>

Seems like the above is missing from distributed iOS libraries, build fails with linker error  
I’ve commented out  
//[DllImport(STUDIO\_VERSION.dll)]  
//private static extern RESULT FMOD\_Studio\_EventInstance\_SetParameterValuesByIndices (IntPtr \_event, int[] indices, float[] values, int count);  
( just returning RESULT.OK from setParameterValuesByIndices(int[] indices, float[] values, int count) )  
in fmod\_studio.cs to make it build.  
~

---

<div class="post-metadata">

### Author: ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)
#### Post date: [November 6, 2017, 2:57am UTC](https://qa.fmod.com/t/1-10-01-setparametervaluesbyindices-missing-in-ios-libraries/13516/2 "2017-11-06T02:57:02Z")

</div>

Thanks for bringing this to our attention.  
This does appear to be a bug in 1.10.01, we will make sure this is fixed for the next release.

---

<div class="post-metadata">

### Author: ![kedarshashi](https://avatars.discourse-cdn.com/v4/letter/k/fbc32d/32.png) [@kedarshashi](https://qa.fmod.com/u/kedarshashi)
#### Post date: [November 28, 2017, 12:25am UTC](https://qa.fmod.com/t/1-10-01-setparametervaluesbyindices-missing-in-ios-libraries/13516/3 "2017-11-28T00:25:54Z")

</div>

> [@](#):
>
> Thanks for bringing this to our attention.  
> This does appear to be a bug in 1.10.01, we will make sure this is fixed for the next release.

Having the same issue, used the same comment fix temporarily. Looking forward to the fix 🙂