You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
LiveKitRoom/VideoConference simply stuck at Disconnected without throwing errors in either server orclient side in NextJs 14
Server
Version: [^2.1.2]
Environment: localhost
NextJs 14 App Router
Client
SDK: livekit-client
Version: [^2.0.10]
To Reproduce
Steps to reproduce the behavior:
Create LIVEKIT_API_KEY, LIVEKIT_API_SECRET,NEXT_PUBLIC_LIVEKIT_URL as instructed by https://docs.livekit.io
Create TokenEndPoint Api Routes ,
Create a page which used fetch from api to get token and useeffect to save tokens
The API call works and send a readable token
The client side doesn't throw any error
The default video conference component simply show disconnected .
The example video conference component demo doesn't even show it's disconnected ?
Expected behavior
The room call should be running with proper token .
If token is incorrect / server refused the authorization then there would be a respond of unauthorized .
Screenshots
The token from server API
The client side render
The front end console log to see if token is indeed received
Additional context
The guide is made for nextjs 13 , so I guess issue can come from here . But in such cases , an error would have been detected by the client sdk or server sdk and showed up .
The text was updated successfully, but these errors were encountered:
@Mohammedyaseen29 I checked if my keys were correct using the example app so I knew it's running . But it just suddenly run again so I don't know what happened . Probably an API choke happened for several days due to outdated packages .
Describe the bug
LiveKitRoom/VideoConference simply stuck at Disconnected without throwing errors in either server orclient side in NextJs 14
Server
Client
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The room call should be running with proper token .
If token is incorrect / server refused the authorization then there would be a respond of unauthorized .
Screenshots
![image](https://private-user-images.githubusercontent.com/118890894/318295005-40264d41-12b2-4ad8-9b4d-dcf69cdc6cb1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkxNTQ0OTYsIm5iZiI6MTcxOTE1NDE5NiwicGF0aCI6Ii8xMTg4OTA4OTQvMzE4Mjk1MDA1LTQwMjY0ZDQxLTEyYjItNGFkOC05YjRkLWRjZjY5Y2RjNmNiMS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjIzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyM1QxNDQ5NTZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04MWI0NDM3MGM4MmYwYmVkNDQxZjVkOTdlZDZmN2FkYzVhOWE4NjE3ZmE5N2I4NGIxMmU5ZmE1M2U3ZTgwOTdjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.DfhEkJoPaemHL3qC_78LOuO3oe2_r4VD0TIsV8hAmbs)
![image](https://private-user-images.githubusercontent.com/118890894/318295444-8111610e-0d3d-4a56-a555-56b7aced36ce.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkxNTQ0OTYsIm5iZiI6MTcxOTE1NDE5NiwicGF0aCI6Ii8xMTg4OTA4OTQvMzE4Mjk1NDQ0LTgxMTE2MTBlLTBkM2QtNGE1Ni1hNTU1LTU2YjdhY2VkMzZjZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjIzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyM1QxNDQ5NTZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT02YzE1MDQ3Y2YzYTY2Yjk3MThkYmFmZWIxNmE1ZTg4ZTg4MjYyODFjYzdiYTg1Njg4MDE5MGMyOGU4MzNkMzQyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.44UFFORWAop5_QWtZg9eTTpn3pZ93635kXObpAVnotM)
![image](https://private-user-images.githubusercontent.com/118890894/318295802-77a2032d-f441-4ed0-b922-48b0798718bb.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkxNTQ0OTYsIm5iZiI6MTcxOTE1NDE5NiwicGF0aCI6Ii8xMTg4OTA4OTQvMzE4Mjk1ODAyLTc3YTIwMzJkLWY0NDEtNGVkMC1iOTIyLTQ4YjA3OTg3MThiYi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjIzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyM1QxNDQ5NTZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05YjFhMjc0NjRjNDFjMmRmZjJjMWY0N2FkMDExM2U1YjYwMDMxNDI4MmVhZGQzYTI2MzhiYmNiYmE2MzgxZmRjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.tFE3Fg3Yu9oIZ3mcpLYFgsXq1ZsnLTC-KEK1BH-iUts)
The token from server API
The client side render
The front end console log to see if token is indeed received
Additional context
The guide is made for nextjs 13 , so I guess issue can come from here . But in such cases , an error would have been detected by the client sdk or server sdk and showed up .
The text was updated successfully, but these errors were encountered: