-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XMLHttpRequest is not defined #19
Comments
Hi @Belephor92, Thank for you reporting an issue and helping improve Kaltura! To get the fastest response time, and help the maintainers review and test your reported issues or suggestions, please ensure that your issue includes the following (please comment with more info if you have not included all this info in your original issue):
and paste the output.
For general troubleshooting see: If you only have a general question rather than a bug report, please close this issue and post at: Thank you in advance, |
This is rather a bug than a question. |
Hi @Belephor92! I am experiencing the same issue as you. |
Hi @shugli,
The startKalturaSession function starts the session. Here is an example for a call that we do:
|
Thanks @Belephor92 ! But are you still using the Typescript client lib? Because this looks more like the nodeJS implementation, or? |
Ok, solution proposed in tensorflow/tfjs#514 (comment) actually did the job!!!! |
Subject of the issue
When calling this.client.request(new SessionStartAction(authData)) I receive the error "XMLHttpRequest is not defined"
I checked the configuration with the start Kultura Session guide from the workflow section and the connection itself should work.
Your environment
Steps to reproduce
Set up the library as described in https://developer.kaltura.com/workflows/Generate_API_Sessions/Authentication;step=1
Expected behaviour
I should receive the token
Actual behaviour
I get following error:
ReferenceError: XMLHttpRequest is not defined
at C:\Career Partner\Projects\idss-discovery\node_modules\kaltura-typescript-client\adapters\adapters\utils.ts:102:15
at new CancelableAction (C:\Career Partner\Projects\idss-discovery\node_modules\kaltura-typescript-client\cancelable-action.ts:23:26)
at Object.createCancelableAction (C:\Career Partner\Projects\idss-discovery\node_modules\kaltura-typescript-client\adapters\adapters\utils.ts:101:17)
at KalturaRequestAdapter.transmit (C:\Career Partner\Projects\idss-discovery\node_modules\kaltura-typescript-client\adapters\adapters\kaltura-request-adapter.ts:22:21)
at KalturaClient.request (C:\Career Partner\Projects\idss-discovery\node_modules\kaltura-typescript-client\kaltura-client-service.ts:96:48)
at new VideoSearchService (C:\Career Partner\Projects\idss-discovery\src\domain\modules\video-search\video-search.service.ts:32:17)
at Injector.instantiateClass (C:\Career Partner\Projects\idss-discovery\node_modules@nestjs\core\injector\injector.js:290:19)
at callback (C:\Career Partner\Projects\idss-discovery\node_modules@nestjs\core\injector\injector.js:77:41)
at Injector.resolveConstructorParams (C:\Career Partner\Projects\idss-discovery\node_modules@nestjs\core\injector\injector.js:118:24)
at Injector.loadInstance (C:\Career Partner\Projects\idss-discovery\node_modules@nestjs\core\injector\injector.js:81:9)
I tried adding XMLHttpRequest manually using npm install to the project and added it as dependency in util.js in my node_modules.
The error disappeard but when starting the connection I get another error: KalturaclientException that contains the correct response token. I guess this behavior comes from the manually installed XMLHttpRequest package.
Do you have any idea how to fix my problem?
Thanks in advance,
best regards,
Tony
The text was updated successfully, but these errors were encountered: