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
Both sides of call have error showing OT_AUTHENTICATION_ERROR: token has expired (1004)
Expected Behavior
Call connects fine.
Current Behavior
When upgrading to 4.14.5 it breaks something for us, however if we downgrade to v4.14.4 on the backend our code works fine without new packages (sodium, jwt, etc)
Not sure where this error is being caused.
Person A calls B.
A's publisher is seen by B after subscription.
B's publisher is never seen by A, both sides have error.
Environment
This behavior is seen in two systems:
Centos 7, php83, NGINX
WSL: Ubuntu Linux 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
"Error: token has expired (1004)
at onSessionInfoError (https://site.local/node_modules/.vite/deps/@opentok_client_dist_js_opentok__js.js?v=220147db:51486:55)
at invokeCallback (https://site.local/node_modules/.vite/deps/@opentok_client_dist_js_opentok__js.js?v=220147db:424:31)
at publish (https://site.local/node_modules/.vite/deps/@opentok_client_dist_js_opentok__js.js?v=220147db:413:23)
at publishRejection (https://site.local/node_modules/.vite/deps/@opentok_client_dist_js_opentok__js.js?v=220147db:371:19)
at MutationObserver.flush (https://site.local/node_modules/.vite/deps/@opentok_client_dist_js_opentok__js.js?v=220147db:227:21)"
Both sides of call have error showing
OT_AUTHENTICATION_ERROR: token has expired (1004)
Expected Behavior
Call connects fine.
Current Behavior
When upgrading to 4.14.5 it breaks something for us, however if we downgrade to v4.14.4 on the backend our code works fine without new packages (sodium, jwt, etc)
Not sure where this error is being caused.
Person A calls B.
A's publisher is seen by B after subscription.
B's publisher is never seen by A, both sides have error.
Environment
This behavior is seen in two systems:
Linux 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
package.lock says
Is this the correct repo?
The text was updated successfully, but these errors were encountered: