This message was deleted.
# cloud
s
This message was deleted.
a
cc @polite-kilobyte-67570
p
hi @faint-army-19363 what kind of dependency and compile errors do you see when trying to upgrade your
livekit-client
version? (there was a dependency issue with
@livekit/react-components
v1.0.2, but that was fixed in 1.0.3)
f
turbo build error with react-example folder path ones, let me share full log with you
p
hm, there should be no need for you to compile with turborepo at all as you are just consuming the packages, right? One other thing to be aware of: are you calling the
server-sdk-js
from client-side code in your app?
f
hm, there should be no need for you to compile with turborepo at all as you are just consuming the packages, right? yes. "npm run build" gave the same error when we run it from example folder. One other thing to be aware of: are you calling the
server-sdk-js
from client-side code in your app? - no
p
ah, sorry. only understood your situation now. you’re just running both meet and the react-example locally, and react-example is failing for you. Are the same errors happening for you on https://example.livekit.io ? (this is the deployed version of the react-example code)
f
ok let me check on this and get back to you quickly
@polite-kilobyte-67570 with https://example.livekit.io , it seems to work login, screenshare, mute/unmute and end. According the /rtc?access_token=XXXX request we observed that livekit-client passing 1.3.2. let me check our dependency and package.json and see what may be affecting api calls issues from our custom react-app end
Thank you for you insight @polite-kilobyte-67570
@polite-kilobyte-67570 update: so according to our dev team , we are using server-sdk-js and cloud api calls 500 issues were automatically sorted after upgrading "livekit-server-sdk-js" to latest version ( https://github.com/livekit/server-sdk-js/releases/tag/v1.1.0 )
🙌 1