# \[FMOD\] transform : assertion: 'previousPoint != NULL' failed on macOS (Unity + FMOD 2.03.07) **URL:** \ **Category:** Unity\ **Created:** [August 26, 2025, 9:08am UTC](https://qa.fmod.com/t/fmod-transform-assertion-previouspoint-null-failed-on-macos-unity-fmod-2-03-07/23272 "2025-08-26T09:08:58Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Viacheslav\_Chernyshe](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Viacheslav\_Chernyshe](https://qa.fmod.com/u/Viacheslav_Chernyshe)\ **Post date:** [August 26, 2025, 9:08am UTC](https://qa.fmod.com/t/fmod-transform-assertion-previouspoint-null-failed-on-macos-unity-fmod-2-03-07/23272/1 "2025-08-26T09:08:58Z")
Hello, After upgrading our project from **FMOD 2.02.22** to **FMOD 2.03.07** we started seeing a recurring error on **macOS** builds (it never occurs on Windows): ```auto [FMOD] transform : assertion: 'previousPoint != NULL' failed UnityEngine.Debug:LogError (object) FMODUnity.RuntimeUtils:DebugLogError (string) (at Assets/Plugins/FMOD/src/RuntimeUtils.cs:594) FMODUnity.RuntimeManager:DEBUG_CALLBACK (FMOD.DEBUG_FLAGS,intptr,int,intptr,intptr) (at Assets/Plugins/FMOD/src/RuntimeManager.cs:104) ``` Some details: - Unity version: 2022.3.44f1 - Target platforms: iOS + Android (but issue reproduces on macOS Editor/Build only). - We tested with a clean project: removing all effects/sounds and leaving only a blank master bus makes the error disappear. Adding events back sometimes triggers the assertion. - The error often appears in batches (hundreds of lines) immediately after starting an event. - We also see related warnings like events waiting for sample data (`EventInstance::updateForStart waited XXX ms`). Questions: 1. What does this specific assertion (`previousPoint != NULL`) mean inside FMOD? 2. Is it related to migrated curves/automation (e.g. distance attenuation, automation points not starting at 0)? 3. Why does it reproduce only on macOS and not Windows? 4. Are there recommended steps to debug which event/parameter curve is causing the assertion? We already tried: - Rebuilding all banks. - Removing/adding events one by one. - Checking automation curves for duplicated or missing first point. Any advice or confirmation if this is a known regression in 2.03.x would be really helpful. Thanks! ---
**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:** [August 29, 2025, 5:51am UTC](https://qa.fmod.com/t/fmod-transform-assertion-previouspoint-null-failed-on-macos-unity-fmod-2-03-07/23272/2 "2025-08-29T05:51:39Z")
Hi, Thanks for the information. > [@Viacheslav\_Chernyshe](#): > > What does this specific assertion (`previousPoint != NULL`) mean inside FMOD? It maybe linked to a race condition with regarding snapshots. For question 2 - 4 I don’t have answers at this point, hopefully we will resolve them with some more investigation. Would it be possible to uploads the built banks to your [profile](https://fmod.com/profile#uploads) so I can test them on my side? Thank you for bringing this to our attention. ---
**Author:** ![Viacheslav\_Chernyshe](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Viacheslav\_Chernyshe](https://qa.fmod.com/u/Viacheslav_Chernyshe)\ **Post date:** [September 4, 2025, 1:55pm UTC](https://qa.fmod.com/t/fmod-transform-assertion-previouspoint-null-failed-on-macos-unity-fmod-2-03-07/23272/3 "2025-09-04T13:55:26Z")
Done it ---
**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:** [September 9, 2025, 5:02am UTC](https://qa.fmod.com/t/fmod-transform-assertion-previouspoint-null-failed-on-macos-unity-fmod-2-03-07/23272/4 "2025-09-09T05:02:46Z")
Thanks you for the banks. I have been able to reproduce the issue. This assert is warning of a thread issue. Nothing wrong that you have done something that we will fix. I have passed on the issue to our development team to investigate further. I do not have a workaround at the moment. Thank you for bringing this to our attention. ---
**Author:** ![Viacheslav\_Chernyshe](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Viacheslav\_Chernyshe](https://qa.fmod.com/u/Viacheslav_Chernyshe)\ **Post date:** [November 10, 2025, 7:40am UTC](https://qa.fmod.com/t/fmod-transform-assertion-previouspoint-null-failed-on-macos-unity-fmod-2-03-07/23272/5 "2025-11-10T07:40:03Z")
Hello, are there any updates? ---
**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:** [November 10, 2025, 9:47pm UTC](https://qa.fmod.com/t/fmod-transform-assertion-previouspoint-null-failed-on-macos-unity-fmod-2-03-07/23272/6 "2025-11-10T21:47:10Z")
This has been fixed for our next release (2.03.11) which should be out in a couple of weeks. ---
**Author:** ![Viacheslav\_Chernyshe](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Viacheslav\_Chernyshe](https://qa.fmod.com/u/Viacheslav_Chernyshe)\ **Post date:** [November 11, 2025, 7:39am UTC](https://qa.fmod.com/t/fmod-transform-assertion-previouspoint-null-failed-on-macos-unity-fmod-2-03-07/23272/7 "2025-11-11T07:39:27Z")
Great news, thank you!