Can't remove participant from call

Nothing happened during executing removeParticipant method from call

Minimal steps to reproduce

// Adding participant to call by phoneIdentifier 
const phoneIdentifier = { phoneNumber: <phoneNumber> };
const participantIdentifier = call.addParticipant(phoneIdentifier, { alternateCallerId: { phoneNumber: <azureCommunicationServicePhoneNumber> }});
// addParticipant executed

........


// Removing participant from call by participant Phone Identifier 
await call.removeParticipant(participantIdentifier ); // starts executing, but not finishes

Any log messages given by the failure

Error doesn't occur, just function doesn't work.

Expected/desired behavior

'removeParticipant' method remove participant from call by participantIdentifier

communication-services-javascript-quickstarts/join-calling-to-teams-meeting at main · Azure-Samples/communication-services-javascript-quickstarts (github.com)

It's running in local but when he tries to host it in AppService it showing below error.

bundle.js:2 

       Uncaught SyntaxError: Invalid or unexpected token (at bundle.js:2:17413)

and also the run syntax npx webpack-dev-server --entry ./client.js --output bundle.js --debug --devtool inline-source-map is not working with latest node version

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

• Checkout the code, run it using webpack command
• Copy Paste a token retrieved from Communication Server

We ONLY can call the echo service...

Any log messages given by the failure

Expected/desired behavior

Please add minimal example when we call a 'colleague' who has a team tab open.
What is required to call 'as a user' to another 'user'?

using the utility on our Communication Service, it is totally unclear where is the link with a teams user/active directory and having this demo working.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

from console:
node issue-access-token.js

Azure Communication Services - Access Tokens Quickstart
Encountered an error
RestError: Denied by the resource provider.
{
"name": "RestError",
"code": "Denied",
"statusCode": 401,
"request": {
"url": "https://*****.europe.communication.azure.com/identities?api-version=2022-10-01",
"headers": {
"content-type": "application/json",
"accept": "application/json",
"accept-encoding": "gzip,deflate",
"user-agent": "azsdk-js-communication-identity/1.2.0 core-rest-pipeline/1.12.1 Node/v18.16.0 OS/(x64-Linux-6.2.0-34-generic)",
"x-ms-client-request-id": "d7e43fba-d52d-4648-9046-db0230301385",
"authorization": "REDACTED"
},

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

npm install the repo
launch app on localhost:3000 , on chrome and/or edge
click on camera button to turn on camera
allow use of camera
observe the bug, video stream is not turned on, although camera LED physically lights up

Any log messages given by the failure

Expected/desired behavior

camera feed is streamed and displayed onto videogallery component

OS and Version?

Windows 10

Versions

latest version from git

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Hi team,

have a question to you. I had a look at the Azure Communications UI Library and the samples available for PSTN voice calls have no such control.

We are using this composites sample - https://azure.github.io/communication-ui-library/?path=/docs/quickstarts-pstn--page

I wonder if you have a component example that can be easily integrated into the PSTN voice call sample so we can demo this to a customer?

Also, the sample is not working for us following the steps. Apparently is complaining about the type of the locator, which is expecting a CallAdapterLocator.

Argument of type '{ userId: CommunicationUserIdentifier; displayName: string; credential: AzureCommunicationTokenCredential | undefined; alternateCallerId: string; locator: { ...; }; }' is not assignable to parameter of type 'Partial'.
Types of property 'locator' are incompatible.
Type '{ participantIds: string[]; }' is not assignable to type 'CallAdapterLocator | undefined'.

Thanks

Please provide us with the following information:

Whenever I make a call to my personal phone number and I disconnect it, the call does not get hung up at the application end. Instead, it calls my number again. The only way to disconnect is by clicking the hang up button in the application.

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Deployed the code samples from the documentation with latest SDK version.
Tested the application.

Any log messages given by the failure

No error logs.

Expected/desired behavior

Once the call has been disconnected by the callee, the application should not call back automatically.

OS and Version?

Windows 11.

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

npx webpack-dev-server --entry ./client.js --output bundle.js --debug --devtool inline-source-map
navigate to localhost:8080
Paste teams link and thread id link
Have tried unescaped and escaped variants of teams and thread id link
Connects successfully to teams - shows waiting in lobby -
can successfully admit user into teams lobby from teams
Send a message from index.html page - nothing received in Teams
Send a messages from Teams to acs user - nothing received in Teams
Web Browser console shows that user token is successfully created, thread id is also successfully created however
403 Forbidden Error : Initiator does not have permission to perform requested operation

Any log messages given by the failure

Console
403 Forbidden Error : Initiator does not have permission to perform requested operation

Expected/desired behavior

Should be able to post chat message from ACS to Teams and vice versa

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 10

Versions

Mention any other details that might be useful

Teams interop form was submitted and activated sucessfully on tenant - also I am global Teams Admin. Teams video/audio calling from other Hero sample(s) works as expected - issue seems to be with chat only.

Thanks! We'll be in touch soon.

When I create a Token using the JS SDK CommunicationIdentityClient I use the line:

const userToken = await tokenClient.getToken(user, ["chat", "voip"]);

the token get created, but it does not get the acsScope coorrectly.

If you put the token in the https://jwt.io/ page the "acsScope" shows only "voip"

What could be the problem?

Blazor is Microsoft future Web strategy, we need these File Sharing UI Component samples migrated to Blazor

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

When sending a message to a non-existent email, I get the status "Succeeded".

Any log messages given by the failure

Expected/desired behavior

I would like to get the status that the email has not been delivered or status "Failed"

OS and Version?

Windows 11.

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

I want to call with an ACS resource related to my Microsoft Teams user (add-1-on-1-cte-video-calling). So to get the right ACS token, I wanted to get mine with the tool: manage-teams-identity-mobile-and-desktop

All environment variables are set, and it runs on the URL http://localhost:3000
http://localhost:3000/redirect is set on the Azure portal as a Single page application redirect URL for my Teams BOT.
So everything should be okay, but when I run this, after login my Teams User the callback URL called back, but not with the AccessToken, but this error

{"errorCode":"network_error","errorMessage":"Network request failed. Please check network trace to determine root cause. | Fetch client threw: Error: HTTP status code 400 | Attempted to reach: https://login.microsoftonline.com/[MY_TENANT_ID_HIDDEN]/oauth2/v2.0/token","subError":"","name":"ClientAuthError"}

Teams Bot has all the necessary permissions.

This issue is for a: (mark with an x)

- [ x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

• run manage-teams-identity-mobile-and-desktop
• login with my Teams user
• get back the error above

Any log messages given by the failure

Expected/desired behavior

• I would like to get back the ACS access token of the impersonated Teams User

OS and Version?

• Windows 11

Versions

• code was downloaded a couple days ago

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I used the statefulChatClient demo from this repo.
https://github.com/Azure-Samples/communication-services-javascript-quickstarts/tree/main/ui-library-starting-with-chat-stateful
I used the code of the demo and added it to my existing project without any changes.
When i start and load the chat screen it works but sometimes while loading previous messages it just crashes wit a messages: See below
It seems to get the token and then it starts loading the messages and at a certain point it just crashes and shows me the message.

It might be related to this Azure/communication-ui-library#506
Not sure

Any log messages given by the failure

Unhandled Rejection (TypeError): Cannot read properties of null (reading 'scrollTop')
(anonymous function)
src/components/MessageThread.tsx:705
fulfilled
http://localhost:3000/static/js/5.chunk.js:120977:24
This screen is visible only in development. It will not appear if the app crashes in production.
Open your browser’s developer console to further inspect this error.  Click the 'X' or hit ESC to dismiss this message.

Also in the console the following error appears:

Uncaught (in promise) TypeError: Cannot read properties of null (reading 'scrollTop')
    at MessageThread.tsx:705:1
    at Generator.next (<anonymous>)
    at fulfilled (MessageStatusIndicator.tsx:166:1)

Expected/desired behavior

This should not happen

OS and Version?

Windows 10. Google chrome

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Hi,

I am trying to implement Teams interop with ACS calling SDK (web) when i use the 1.5.4-beta.1 i am having the error
"callClient.createTeamsCallAgent is not a function" while i can instantiate createTeamsCallAgent with version 1.7.0-alpha.20220718.1.

I am trying to test the transfer feature (with Teams identity)

can you please help which version of the web calling SDK i should use ?

@xixian73 can you support please ?

Many thanks !

I am not able to run the
@azure/communication-react module in my vue js project they throwing an error as
Uncaught (in promise) TypeError: dispatcher is null
Can u please help me out

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report 
- [ ] feature request
- [X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

https://azure.github.io/communication-ui-library/?path=/story/quickstarts-statefulclient--page

Any log messages given by the failure

I can see previously shared files on a thread from when we tested the ChatComposite capabilities for file sharing. But can't seem to find any implementation of this functionality for the stateful clients.

Expected/desired behavior

Is there a similar sample for file sharing using the stateful chat components ?

OS and Version?

Windows 10.

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Hi,

I'm trying to get a token for the ACS API dynamically, instead of going to Azure Portal and using the "Identities & User Access Tokens" generate button and pasting them in the apps.

I already have a ReactApp that uses Azure AD and MSAL...

ReactDOM.render(
    <React.StrictMode>
        <MsalProvider instance={msalInstance}>
            <App />
        </MsalProvider>
    </React.StrictMode>,
    document.getElementById("root")
);

Trying to find out what are the next steps I saw this code that is for node in JS. Think that something like this can be implemented on the App.js and pass it as a props to all the other controls.

async function createIdentityAndIssueToken(resourceEndpoint) {
    const client = new CommunicationIdentityClient(resourceEndpoint, credential);
    return await client.createUserAndToken(["chat"]);
}

Is there any example or clear documentation on how to create a Token based on an Azure AD identity?

Thanks for the great work!

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

run : npx webpack-dev-server --entry ./client.js --output bundle.js --debug --devtool inline-source-map

Any log messages given by the failure

Unable to parse endpoint metadata

Expected/desired behavior

Start the call

OS and Version?

Windows 10

Versions

1.0.0

Mention any other details that might be useful

Hi! I am trying to call a peer over 'add-1-on-1-video-calling' sample and I just started code as it is described by running:

npx webpack-dev-server --entry ./client.js --output bundle.js --debug --devtool inline-source-map

Application is built but I can not start a call after setting 'userIdToCall' variable to any string value. Is it Skype account name or is it a mail? Whatever I tried, I am getting a warning like: "Unable to parse endpoint metadata". This is a message which is a bit suspicious since it is not clear to understand easily;

call = callAgent.startCall([{ communicationUserId: userToCall }], placeCallOptions );

Can you define what should I set to this variable?

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

OS and Version?

IOS 12.2

Mention any other details that might be useful

JS framework: Angular 11+
Iphone 8
Browser: Safari
Please provide a list of supported devices (IOS
and Android)
Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1. Open add-1-on-1-voice-calling sample project with the terminal window.
2. Run npm i on the directory of the project to install dependencies
3. Run the following command.
   npx webpack-dev-server --entry ./client.js --output bundle.js --debug --devtool inline-source-map
   An error has occured.

Any log messages given by the failure

Would you like to install serve? (That will run npm install -D @webpack-cli/serve) (yes/NO) : yes
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/webpack
npm ERR! dev webpack@"^4.46.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"5.x.x" from @webpack-cli/[email protected]
npm ERR! node_modules/@webpack-cli/serve
npm ERR! dev @webpack-cli/serve@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\osamum\AppData\Local\npm-cache_logs\2023-03-31T06_12_02_739Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user01\AppData\Local\npm-cache_logs\2023-03-31T06_12_02_739Z-debug-0.log
undefinedWould you like to install serve? (That will run npm install -D @webpack-cli/serve) (yes/NO) : yes
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/webpack
npm ERR! dev webpack@"^4.46.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"5.x.x" from @webpack-cli/[email protected]
npm ERR! node_modules/@webpack-cli/serve
npm ERR! dev @webpack-cli/serve@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\user01\AppData\Local\npm-cache_logs\2023-03-31T06_12_02_739Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User01\AppData\Local\npm-cache_logs\2023-03-31T06_12_02_739Z-debug-0.log
undefined Would you like to install serve? (That will run npm install -D @webpack-cli/serve) (yes/NO) : yes
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/webpack
npm ERR! dev webpack@"^4.46.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"5.x.x" from @webpack-cli/[email protected]
npm ERR! node_modules/@webpack-cli/serve
npm ERR! dev @webpack-cli/serve@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\User01\AppData\Local\npm-cache_logs\2023-03-31T06_12_02_739Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User01\AppData\Local\npm-cache_logs\2023-03-31T06_12_02_739Z-debug-0.log
undefined

Expected/desired behavior

The sample application runs fine.

OS and Version?

Windows 11 + Microsoft Edge

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

1. Clone the add-1-on-1-video-calling repo.
2. Follow the instructions on the sample README to install packages and run the app.

Any log messages given by the failure

N/A

Expected/desired behavior

Sample works by following instructions.

Actual behavior

User token must be added to Line #55.

OS and Version?

GitHub Codespaces

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

in file add-1-on-1-video-calling/webpack.config.js line 19, thml should be changed to html.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Try to run ui-library-starting-with-chat-stateful sample after providing endpointUrl, userAccessToken, userId (not sure what this was so I provided Identity field value from Identity and User Access blade on Communication Service Resource), threadId (it's not explained anywhere how to generate Thread Id. So I ran add-chat quick start which generates thread id internally and copied that thread id here), displayName (I used my name here).

Any log messages given by the failure

running the quick start gives this error on the browser

Unhandled Rejection (ChatError): ChatThreadClient.listMessages: {
"CommunicationError": {
"Code": "Forbidden",
"Message": "The initiator doesn't have the permission to perform the requested operation.",
"Details": []
}
}
toChatError
src/ChatContext.ts:378
375 | }
376 | const toChatError = (target: ChatErrorTarget, error: unknown): ChatError => {
377 | if (error instanceof Error) {

378 | return new ChatError(target, error);
379 | }
380 | return new ChatError(target, new Error(${error}));
381 | };"../../acs-ui-common/src"
View compiled
ChatContext.
http://localhost:3000/static/js/vendors~main.chunk.js:230460:29
230457 | try {
230458 | return yield f(...args);
230459 | } catch (error) {
230460 | const chatError = toChatError(target, error);
| ^ 230461 | this.setLatestError(target, chatError);
230462 | throw chatError;
230463 | }
View source
rejected
http://localhost:3000/static/js/vendors~main.chunk.js:230161:32
This screen is visible only in development. It will not appear if the app crashes in production.
Open your browser’s developer console to further inspect this error. Click the 'X' or hit ESC to dismiss this message.

Expected/desired behavior

The quick start should run as explained in the documentation.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
macOS Monterey

Versions

version 12.3.1

Mention any other details that might be useful

The documentation (and code) for quick starts is not well done which would impact the adoption of this solution.

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

git clone https://github.com/Azure-Samples/communication-services-javascript-quickstarts.git
npm i
npx webpack-dev-server --entry ./client.js --output bundle.js --debug --devtool inline-source-map

Any log messages given by the failure

PS D:\Github\communication-services-javascript-quickstarts\add-1-on-1-video-calling> npm i
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.

added 624 packages, and audited 625 packages in 7s

30 packages are looking for funding
run npm fund for details

9 vulnerabilities (1 low, 1 moderate, 7 high)

To address issues that do not require attention, run:
npm audit fix

To address all issues (including breaking changes), run:
npm audit fix --force

Run npm audit for details.
PS D:\Github\communication-services-javascript-quickstarts\add-1-on-1-video-calling> npx webpack-dev-server --entry ./client.js --output bundle.js --debug --devtool inline-source-map
i ｢wds｣: Project is running at http://localhost:8080/
i ｢wds｣: webpack output is served from /
i ｢wds｣: Content not from webpack is served from D:\Github\communication-services-javascript-quickstarts\add-1-on-1-video-calling
node:internal/crypto/hash:69
this[kHandle] = new _Hash(algorithm, xofLen);
^

Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:69:19)
at Object.createHash (node:crypto:133:10)
at module.exports (D:\Github\communication-services-javascript-quickstarts\add-1-on-1-video-calling\node_modules\webpack\lib\util\createHash.js:135:53)
at NormalModule._initBuildHash (D:\Github\communication-services-javascript-quickstarts\add-1-on-1-video-calling\node_modules\webpack\lib\NormalModule.js:417:16)
at handleParseError (D:\Github\communication-services-javascript-quickstarts\add-1-on-1-video-calling\node_modules\webpack\lib\NormalModule.js:471:10)
at D:\Github\communication-services-javascript-quickstarts\add-1-on-1-video-calling\node_modules\webpack\lib\NormalModule.js:503:5
at D:\Github\communication-services-javascript-quickstarts\add-1-on-1-video-calling\node_modules\webpack\lib\NormalModule.js:358:12
at D:\Github\communication-services-javascript-quickstarts\add-1-on-1-video-calling\node_modules\loader-runner\lib\LoaderRunner.js:373:3
at iterateNormalLoaders (D:\Github\communication-services-javascript-quickstarts\add-1-on-1-video-calling\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
at Array. (D:\Github\communication-services-javascript-quickstarts\add-1-on-1-video-calling\node_modules\loader-runner\lib\LoaderRunner.js:205:4) {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v18.17.0

Expected/desired behavior

http://localhost:8080/ throw exception

OS and Version?

Windows 2022 Server

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Trying Sample: ui-library-add-call-recording.
Run it locally and when I click the start recording button
An error occurs at this point.
/api/startRecording
var startRecordingResponse = await callAutomationClient.GetCallRecording().StartAsync(recordingOptions).ConfigureAwait(false);

[2024-01-16T05:31:33.394Z] Executed 'startRecording' (Failed, Id=f8d195c3-a594-4542-9d76-13f136813fed, Duration=15ms)
[2024-01-16T05:31:33.398Z] System.Private.CoreLib: Exception while executing function: startRecording. System.Private.CoreLib: The input is not a valid Base-64 string as it contains a non-base 64 character , more than two padding characters, or an illegal character among the padding characters.

It seems like there is nothing wrong with the connection string passed to new CallAutomationClient, but what does the error mean?

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Install Add Chat folder

Any log messages given by the failure

Cannot GET/ at the localhost:8080 page

Expected/desired behavior

Open up the chat quickstart page

OS and Version?

Windows 10

Versions

npm V 7.21, Node 16.2, Webpack 5.32

Mention any other details that might be useful

Creating a folder called public and putting the html index there fix the issue

---

Thanks! We'll be in touch soon.

This issue is for a:

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Hi guys I have a found a typo in your webpack configuration that is blocking the app from runing:

Any log messages given by the failure

Webpack error when tyrint to run the app

ERROR in unable to locate 'communication-services-javascript-quickstarts/add-1-on-1-video-calling/index.thml' glob

Expected/desired behavior

Expect to run the app successfully.

there are examples for JS and .net like communication-services-javascript-quickstarts

Description

There is a noticeable lack of detailed examples and documentation for using the REST API and Golang with Azure Communication Services to send emails. This issue aims to request the creation of comprehensive guides and examples similar to the existing JavaScript quickstarts, but tailored for Golang and REST API usage.

Issue Type

• feature request

Minimal Steps to Reproduce

Not applicable as this is a documentation and example request.

Log Messages

Not applicable.

Expected/Desired Behavior

Provision of REST API examples and Golang documentation that includes:

• Authentication methods
• Request headers and bodies setup
• Response handling

OS and Version

Not applicable.

Versions

Not applicable.

Additional Details

These resources will enable developers to integrate email functionalities using Golang or direct API calls effectively, enhancing the utility of Azure Communication Services in diverse development environments.