Kris

@jspizziri Thanks for all the awesome work! Is there a workaround for this currently (like downgrading) or is that PR probably coming out soon?

@stereodenis So 2.1.3 was the original version I was using before upgrading React Native but after upgrading, that version gives me a different problem ([Could not find com.google.android.exoplayer:exoplayer-core:2.11.4.](https://github.com/doublesymmetry/react-native-track-player/issues/1235#)) which was...

@russriser the changes that fix this are merged in https://github.com/doublesymmetry/KotlinAudio/pull/38. Just need to wait for it to be included in a new version

- #1249

Has this error always been there since you installed the package? I haven't seen that error before

Hmmm that's really weird I don't think I've run into it or seen any other issues on here like this from what I remember. I mainly develop my app on...

> > @WilliamPeralta Did you solve this? I am also facing this issue when integrating watermelon into an existing DB. But it works fine on a fresh install. My hunch...

It's because `callWriter` is only if you are nesting writers like shown here: https://nozbe.github.io/WatermelonDB/Writers.html?highlight=callWriter#advanced-nesting-writers-or-readers If you are not nesting the writer you should follow this part instead: https://nozbe.github.io/WatermelonDB/Writers.html?highlight=callWriter#writer-methods where as...

``` If everything is working fine, you can safely ignore this message (queueing is working as expected) ``` I just ignore it.

@radex Waiting on this to be merged as migrating to expo Modules (specifically Expo 44) from unimodules breaks WatermelonDB