Coder Social home page Coder Social logo

azure-samples / communication-services-web-calling-hero Goto Github PK

View Code? Open in Web Editor NEW
97.0 35.0 151.0 9.72 MB

Hero sample to showcase web calling capabilities for Azure Communication Services

License: MIT License

JavaScript 14.83% HTML 0.59% TypeScript 83.76% CSS 0.82%

communication-services-web-calling-hero's Introduction

page_type languages products
sample
typescript
nodejs
azure
azure-communication-services

Deploy to Azure

Group Calling Sample

Overview

This is a sample application to show how we can use the @azure/communication-react package to build a calling experience. Learn more about the Azure Communication Services UI Library. The client-side application is a React based user interface. Alongside this front-end is a NodeJS web application powered by ExpressJS that performs functionality like minting new user tokens for each call participant.

Additional documentation for this sample can be found on Microsoft Docs.

Before contributing to this sample, please read our contribution guidelines.

Homepage

❤️ Feedback

We appreciate your feedback and energy helping us improve our services. If you've tried the service, please give us feedback through this survey.

Prerequisites

Code structure

  • ./Calling/src/app: Where the client code lives
  • ./Calling/src/app/App.tsx: Entry point into the calling sample
  • ./Calling/src/app/views/HomeScreen.tsx:
  • ./Calling/src/app/views/CallScreen.tsx:
  • ./Calling/src/app/views/EndCall.tsx:
  • ./Calling/src/app/views/UnsupportedBrowserPage.tsx:
  • ./Server: server code
  • ./Server/appsettings.json: Where to put your azure communication services connection string

Before running the sample for the first time

  1. Open an instance of PowerShell, Windows Terminal, Command Prompt or equivalent and navigate to the directory that you'd like to clone the sample to.

    git clone https://github.com/Azure-Samples/communication-services-web-calling-hero.git`
  2. Get the Connection String from the Azure portal. For more information on connection strings, see Create an Azure Communication Resources

  3. Once you get the Connection String, add the connection string to the samples/Server/appsetting.json file. Input your connection string in the variable: ResourceConnectionString.

  • There are two other properties in the appsettings.json file (EndpointUrl, AdminUserId). For the Calling Hero Sample these two properties are unnecessary. We use this file with our chat hero sample and that is where those strings are used.

Local run

  1. Install dependencies

    npm run setup
  2. Start the calling app

    npm run start

    This will open a client server on port 3000 that serves the website files, and an api server on port 8080 that performs functionality like minting tokens for call participants.

Troubleshooting

  1. The app shows an "Unsupported browser" screen but I am on a supported browser.

    If your app is being served over a hostname other then localhost, you must serve traffic over https and not http.

Publish to Azure

  1. npm run setup
  2. npm run build
  3. npm run package
  4. Use the Azure extension and deploy the Calling/dist directory to your app service

Additional Reading

communication-services-web-calling-hero's People

Contributors

alex-kwan avatar alkwa-msft avatar anjulgarg avatar armansabaa avatar carocao-msft avatar communication-ui-bot avatar dailam-msft avatar ddematheu2 avatar dependabot[bot] avatar dmceachernmsft avatar edwardlee-msft avatar jamesburnside avatar leahmaestri avatar mgamis-msft avatar microsoft-github-operations[bot] avatar microsoftopensource avatar porternan avatar prabhjot-msft avatar prprabhu-ms avatar ralphgabrinao avatar reedruddy avatar salujamanish avatar timheuer avatar vhuseinova-msft avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

communication-services-web-calling-hero's Issues

Non-react version availability

Just wondering if there is a non-react version floating around? I hate to be that guy... but man... that's a whole new can of worms if you're a 1 man band.

Microphone selection does not work

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

Create sample app and deploy (either local on Azure)
Ensure you computer has more than one possible Microphone
Run app and try to select and use the 2nd, 3rd or 4th mic attached to your system.
Only the first is recognized now matter what you select initially or during the call that first Microphone in the list is used.

Any log messages given by the failure

None

Expected/desired behavior

Should be able to use any of the available microphones

OS and Version?

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

Versions

Mention any other details that might be useful

Zap me on corpnet if you need more!


Thanks! We'll be in touch soon.

Recording file is empty

Hi, i am using

"@azure/communication-calling": "^1.4.4" followed the VS/ Sample client Solution and created implemented.

All working fine but in BLOB storage the MP4 is empty (black screen), no audio also. how can i troubleshoot this issue ?

Regards.

Prevent user from accidentally leaving ACS call

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

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

Minimal steps to reproduce

I'm trying to find a way to prevent user from accidentally leaving ACS call (using Javascript Call SDK). Right now clicking refresh page will make the user leave the ACS call immediately (with no "Are you sure?" message).

I have tried to prevent default behaviour for onbeforeunload event, for example with the following code in React:

  useEffect(() => {
    window.onbeforeunload = (event) => {
      event.preventDefault();
      return "";
    };
    return function allowRefresh() {
      window.onbeforeunload = null;
    };
  }, []);

On attempt to leave page, the browser will popup a confirmation window ("Are you sure you want to leave the page?"). But clicking Cancel on the popup makes the call disconnect anyway (even though the user chose not to leave page). If this doesn't work, is there any way to prevent user from accidentally leaving ACS call?

Expected/desired behavior

The ACS call is NOT disconnected when clicking Cancel in Chrome confirmation popup.

OS and Version?

Windows 10

Customization for echobot 8:echo123

Is there any chance to simply customize echo bot that called by 8:echo123? Under customization I mean change default language from English to another one and modify text script?

If not, can you please provide some information how to create such echo bot by myself?

iOS 14.6 + Safari not loading

Learn more about browsers and platforms supported by the web calling sdk

That is the message I'm receiving after I click Start Call. No issues in Chrome on the iOS device.

I am using a straight Azure Deploy (Not forked). Everything works in a browser on the desktop. However some issues on iOS Safari

Is there something I need to enable for iOS to use this sample? Thanks for your assistance.

Unable to publish azure application

We are not able to publish this application on our production server.
We are getting following error continuously.

The command "npm run build" exited with code 1. Calling
Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory Calling EXEC 0
1: 00007FF6406B481F napi_wrap+110783
2: 00007FF640657F26 v8::base::CPU::has_sse+61862
3: 00007FF640658E26 node::OnFatalError+294
4: 00007FF640F323BE v8::Isolate::ReportExternalAllocationLimitReached+94
5: 00007FF640F1718D v8::SharedArrayBuffer::Externalize+781
6: 00007FF640DC02CC v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1516
7: 00007FF640DCB6EA v8::internal::Heap::ProtectUnprotectedMemoryChunks+1258
8: 00007FF640DC8829 v8::internal::Heap::PageFlagsAreConsistent+2457
9: 00007FF640DBD3D1 v8::internal::Heap::CollectGarbage+2049
10: 00007FF640DBB5D5 v8::internal::Heap::AllocateExternalBackingStore+1349
11: 00007FF640DDBA3B v8::internal::Factory::NewFillerObject+203
12: 00007FF640B0A0B1 v8::internal::interpreter::JumpTableTargetOffsets::iterator::operator=+1409
13: 00007FF640FBB27D v8::internal::SetupIsolateDelegate::SetupHeap+465325
14: 0000010F5A3E3FD8
RpcIpcMessagePortClosedError: Process 26036 exited with code "134" [null]
Issues checking service aborted - probably out of memory. Check the memoryLimit option in the ForkTsCheckerWebpackPlugin configuration.
If increasing the memory doesn't solve the issue, it's most probably a bug in the TypeScript or EsLint.
Failed to compile.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! errno 1
2>Build failed. Check the Output window for more details.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
npm ERR! [email protected] build: react-scripts build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Build fails on communication-calling package

- [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

node_modules/@azure/communication-calling/dist-esm/sdk.bundle.js:18:13900: error: Cannot assign to "i" because it is a constant

Expected/desired behavior

Project builds

OS and Version?

Windows 10

Versions

1.0.0

Mention any other details that might be useful

I created and with:

npm init @vitejs/app peerque --template vue-ts

Then I added following packages to package.json to be able to test SDK functions.

    "@azure/communication-calling": "1.0.0",
    "@azure/communication-common": "1.0.0",
    "@azure/communication-identity": "1.0.0"

I have a simple page that imports @azure/communication-calling but when I try to build project it fails with error hat I wrote above.

When I change const to let in the source code build passes. I don't know if it is related to my tsconfig.json or not. I will share it just in case.

{
  "compilerOptions": {
    "target": "esnext",
    "module": "esnext",
    "moduleResolution": "node",
    "strict": true,
    "jsx": "preserve",
    "sourceMap": true,
    "resolveJsonModule": true,
    "esModuleInterop": true,
    "lib": ["esnext", "dom"]
  },
  "include": ["src/**/*.ts", "src/**/*.d.ts", "src/**/*.tsx", "src/**/*.vue"],
  "exclude": ["node_modules", "dist"]
}

Thanks in advance

Checking if we could access to audio stream

Hi,

I'm trying to integrate azure speaker service to this sample in order to authenticate the person. Now for that we need access to audio stream of participant, so I wanted to check if there's a way to handle the audio stream and send it to azure speaker service from this sample

Video is not relayed from Android to desktop client

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. Deploy the solution
  2. Create a meeting with a desktop client
  3. Join the room with a mobile client
  4. Mobile client video is never shown on the desktop client

Any log messages given by the failure

log.browser.ts:10 azure:ACS:warning 06/04/2021, 17:30:49:456 CallClient3:CallStack:MA:webrtc2-1:SSM Sender with media type Video does not exist, do not update media stream

Expected/desired behavior

Mobile video is shown on desktop client when video is turned on

OS and Version?

Windows 10 (Chrome 89.0.4389.114, 32 bit)
Android 10 (Chrome 87.0.4280.141)

Versions

Latest version cloned from github

Mention any other details that might be useful

I tried both WLAN and mobile networks. From desktop client to desktop client everything seems to work.


Thanks! We'll be in touch soon.

Test Issue for Github bot to Teams 2

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.

Got 403 error when join with teams meeting link

Error description

Error occurs when trying to join to the meeting with Microsoft Teams meeting link

Minimal steps to reproduce

  1. Download communication-service-web-calling-hero
  2. Create Azure Communication Service and copy Connection String
  3. Configure communication-service-web-calling-hero with Connection String from previous step.
  4. Start meeting in Microsoft Teams and copy meeting link.
  5. Modify /communication-services-web-calling-hero/blob/main/Calling/ClientApp/src/core/sideEffects.ts file on 333 line to join to meeting with Team Meeting link instead of groupId:
 call = await callAgent.join({meetingLink: "TEAM_MEETING_LINK"}, callOptions);
  1. Run communication-service-web-calling-hero application
  2. Click on "Start call" button from screenshot and then error occurs.

Screenshots

image
2.
image
3.
image

  1. Error Response
    image

  2. BTW in Microsoft Teams Admin Center Setting for Meeting to allow external users to join a meeting was enabled

image

Expected/desired behavior

Connect to Teams Meeting via Communication Service through communication-service-web-calling-hero app like external user.

OS and Version

Windows 10
Chrome Version 89.0.4389.114 (Official Build) (64-bit)

Versions

"@azure/communication-calling": "1.0.0",
"@azure/communication-common": "1.0.0",
"@azure/communication-identity": "1.0.0",

npm run build breaks

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. Clone Repository
  2. run npm run build
  3. Update typescript version to e.g. 3.8.3 to get rid of issues with jest-diff
  4. run npm run build again

Any log messages given by the failure

1: .../node_modules/jest-diff/build/diffLines.d.ts:8:13 - error TS1005: '=' expected
2: TypeScript error in .../communication-services-web-calling-hero/Calling/ClientApp/src/containers/GroupCall.ts(39,26):
Property 'streams' does not exist on type 'StreamsState'.
3: TypeScript error in .../communication-services-web-calling-hero/Calling/ClientApp/src/core/RemoteStreamSelector.ts(63,20):
Member 'dominantParticipantsCount' implicitly has an 'any' type.

Expected/desired behavior

The build is successful

OS and Version?

Windows 10

Versions

node v15.13.0
npm 7.7.6

Mention any other details that might be useful

After updating typescript version to 3.8.3 and fixing the issues in groupcall.ts and remotestreamselector.ts everything seems to work normally


Thanks! We'll be in touch soon.

Sample not working in mobile web (Chrome and Safari)

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

Deploy sample on azure web app and open in browser, only first page displays, if you try starting a call it says "Learn more about browsers and platforms supported by the web calling SDK""

Any log messages given by the failure

Expected/desired behavior

It should allow to start and participate in call from mobile

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
iphone 6S .. chrome browser

Versions

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Don't put the local video stream in the redux store

We need to store the state if the camera is desired to be in use.

We can't store complex objects into the redux store so we want to store the video device info and create a local video stream object when we need to use it.

Broken repo link on 'Before running the sample for the first time'

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 you follow the steps on the 'Before running the sample for the first time' on:
#2. git clone https://github.com/Azure/Communication.git
That git repo, no longer contains the calling samples as of Oct 22, 2020.

Any log messages given by the failure

No error message, just the calling samples are missing.

Expected/desired behavior

I expect the calling sample to be included when I clone that repo

OS and Version?

not applicable

Versions

not applicable

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Does not seem to work with ios mobile safari or android mobile chrome

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.

I can't hear sound from android web browser

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

Window web browser can't hear sound from android web browser.
But android web browser can hear sound from window web browser.

Any log messages given by the failure

None

Expected/desired behavior

Window user can hear sound from android web browser.

OS and Version?

Windows 10 / Android 10

Versions

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Giving Screen control while screen share

Please provide us with the following information:

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

- [ ] bug report -> please search issues before submitting
- [x] 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.

a TEST ISSUE

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.

IOS 12.2 (iPhone 8) video call isn`t working.

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.
Image from iOS (1)

CallClient is trying to reinitialize whenever I resize the window while the configuration page is loaded

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 the sample app as is.
  2. Click the button to start a call
  3. When the configuration page is loaded, resize the browser window and a new call client will try to be created, when one already exists. This will throw the error in the console.

Any log messages given by the failure

index.js:1 Error: A Call Agent instance has already been created.Please dispose of it before creating a new Call Client instance
at f. (sdk.bundle.js:247)
at Generator.next ()
at sdk.bundle.js:247
at new Promise ()
at o (sdk.bundle.js:247)
at f.createCallAgent (sdk.bundle.js:247)
at f. (sdk.bundle.js:4)
at Generator.next ()
at sdk.bundle.js:4
at new Promise ()
at i (sdk.bundle.js:4)
at f.o.value (sdk.bundle.js:4)
at sideEffects.ts:155
console. @ index.js:1
(anonymous) @ sideEffects.ts:226
async function (async)
(anonymous) @ sideEffects.ts:113
(anonymous) @ index.js:8
initCallClient @ Configuration.ts:33
(anonymous) @ Configuration.tsx:61
commitHookEffectList @ react-dom.development.js:22030
commitPassiveHookEffects @ react-dom.development.js:22064
callCallback @ react-dom.development.js:336
invokeGuardedCallbackDev @ react-dom.development.js:385
invokeGuardedCallback @ react-dom.development.js:440
flushPassiveEffectsImpl @ react-dom.development.js:25392
unstable_runWithPriority @ scheduler.development.js:697
runWithPriority$2 @ react-dom.development.js:12149
flushPassiveEffects @ react-dom.development.js:25361
(anonymous) @ react-dom.development.js:25240
workLoop @ scheduler.development.js:641
flushWork @ scheduler.development.js:596
performWorkUntilDeadline @ scheduler.development.js:203

Expected/desired behavior

I do NOT expect a new call client to be created ever time the browser window resizes.

Mention any other details that might be useful

This error causes problems downstream with the acs user showing as not online. See this for an example of a downstream problem. Azure/Communication#114

Calling Hero does not run setup with node v17+

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
- [X] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

On node versions 17 and 18, npm run setup does not

Any log messages given by the failure

#Npm debug log

0 verbose cli /home/copennin/.nvm/versions/node/v17.9.1/bin/node /home/copennin/.nvm/versions/node/v17.9.1/bin/npm
1 info using [email protected]
2 info using [email protected]
3 timing npm:load:whichnode Completed in 0ms
4 timing config:load:defaults Completed in 4ms
5 timing config:load:file:/home/copennin/.nvm/versions/node/v17.9.1/lib/node_modules/npm/npmrc Completed in 2ms
6 timing config:load:builtin Completed in 3ms
7 timing config:load:cli Completed in 5ms
8 timing config:load:env Completed in 3ms
9 timing config:load:file:/mnt/c/Users/copennin/Code/Sandbox/communication-services-web-calling-hero/Server/.npmrc Completed in 0ms
10 timing config:load:project Completed in 58ms
11 timing config:load:file:/home/copennin/.npmrc Completed in 0ms
12 timing config:load:user Completed in 2ms
13 timing config:load:file:/home/copennin/.nvm/versions/node/v17.9.1/etc/npmrc Completed in 0ms
14 timing config:load:global Completed in 0ms
15 timing config:load:validate Completed in 2ms
16 timing config:load:credentials Completed in 3ms
17 timing config:load:setEnvs Completed in 2ms
18 timing config:load Completed in 86ms
19 timing npm:load:configload Completed in 86ms
20 timing npm:load:mkdirpcache Completed in 5ms
21 timing npm:load:mkdirplogs Completed in 2ms
22 verbose title npm install
23 verbose argv "install"
24 timing npm:load:setTitle Completed in 2ms
25 timing config:load:flatten Completed in 6ms
26 timing npm:load:display Completed in 11ms
27 verbose logfile logs-max:10 dir:/home/copennin/.npm/_logs
28 verbose logfile /home/copennin/.npm/_logs/2022-06-22T23_45_27_778Z-debug-0.log
29 timing npm:load:logFile Completed in 13ms
30 timing npm:load:timers Completed in 0ms
31 timing npm:load:configScope Completed in 0ms
32 timing npm:load Completed in 122ms
33 timing arborist:ctor Completed in 2ms
34 silly logfile start cleaning logs, removing 1 files
35 silly logfile done cleaning log files
36 timing idealTree:init Completed in 2645ms
37 timing idealTree:userRequests Completed in 1ms
38 silly idealTree buildDeps
39 timing idealTree:#root Completed in 2ms
40 silly fetch manifest @typescript-eslint/parser@^5.0.0
41 timing arborist:ctor Completed in 0ms
42 http fetch GET 200 https://registry.npmjs.org/@typescript-eslint%2fparser 12823ms (cache revalidated)
43 silly fetch manifest eslint@^6.0.0 || ^7.0.0 || ^8.0.0
44 http fetch GET 200 https://registry.npmjs.org/eslint 151ms (cache revalidated)
45 timing idealTree Completed in 15780ms
46 timing command:install Completed in 15839ms
47 verbose stack Error: could not resolve
47 verbose stack     at PlaceDep.failPeerConflict (/home/copennin/.nvm/versions/node/v17.9.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/place-dep.js:549:25)
47 verbose stack     at PlaceDep.place (/home/copennin/.nvm/versions/node/v17.9.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/place-dep.js:199:21)
47 verbose stack     at new PlaceDep (/home/copennin/.nvm/versions/node/v17.9.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/place-dep.js:73:10)
47 verbose stack     at /home/copennin/.nvm/versions/node/v17.9.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:990:31
47 verbose stack     at Array.map (<anonymous>)
47 verbose stack     at Arborist.[buildDepStep] (/home/copennin/.nvm/versions/node/v17.9.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:990:8)
47 verbose stack     at async Arborist.buildIdealTree (/home/copennin/.nvm/versions/node/v17.9.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:218:7)
47 verbose stack     at async Promise.all (index 1)
47 verbose stack     at async Arborist.reify (/home/copennin/.nvm/versions/node/v17.9.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:153:5)
47 verbose stack     at async Install.exec (/home/copennin/.nvm/versions/node/v17.9.1/lib/node_modules/npm/lib/commands/install.js:156:5)
48 verbose cwd /mnt/c/Users/copennin/Code/Sandbox/communication-services-web-calling-hero/Server
49 verbose Linux 5.10.102.1-microsoft-standard-WSL2
50 verbose node v17.9.1
51 verbose npm  v8.11.0
52 error code ERESOLVE
53 error ERESOLVE could not resolve
54 error
55 error While resolving: �[1m@typescript-eslint/eslint-plugin�[22m@�[1m5.8.1�[22m
55 error Found: �[1m@typescript-eslint/parser�[22m@�[1m4.33.0�[22m�[2m�[22m
55 error �[2mnode_modules/@typescript-eslint/parser�[22m
55 error   �[33mdev�[39m �[1m@typescript-eslint/parser�[22m@"�[1m^4.12.0�[22m" from the root project
55 error
55 error Could not resolve dependency:
55 error �[35mpeer�[39m �[1m@typescript-eslint/parser�[22m@"�[1m^5.0.0�[22m" from �[1m@typescript-eslint/eslint-plugin�[22m@�[1m5.8.1�[22m�[2m�[22m
55 error �[2mnode_modules/@typescript-eslint/eslint-plugin�[22m
55 error   �[33mdev�[39m �[1m@typescript-eslint/eslint-plugin�[22m@"�[1m^5.8.1�[22m" from the root project
55 error
55 error Conflicting peer dependency: �[1m@typescript-eslint/parser�[22m@�[1m5.29.0�[22m�[2m�[22m
55 error �[2mnode_modules/@typescript-eslint/parser�[22m
55 error   �[35mpeer�[39m �[1m@typescript-eslint/parser�[22m@"�[1m^5.0.0�[22m" from �[1m@typescript-eslint/eslint-plugin�[22m@�[1m5.8.1�[22m�[2m�[22m
55 error   �[2mnode_modules/@typescript-eslint/eslint-plugin�[22m
55 error     �[33mdev�[39m �[1m@typescript-eslint/eslint-plugin�[22m@"�[1m^5.8.1�[22m" from the root project
55 error
55 error Fix the upstream dependency conflict, or retry
55 error this command with --force, or --legacy-peer-deps
55 error to accept an incorrect (and potentially broken) dependency resolution.
55 error
55 error See /home/copennin/.npm/eresolve-report.txt for a full report.
56 verbose exit 1
57 timing npm Completed in 16324ms
58 verbose unfinished npm timer reify 1655941528224
59 verbose unfinished npm timer reify:loadTrees 1655941528271
60 verbose unfinished npm timer idealTree:buildDeps 1655941530922
61 verbose unfinished npm timer idealTree:node_modules/@typescript-eslint/eslint-plugin 1655941530928
62 verbose code 1
63 error A complete log of this run can be found in:
63 error     /home/copennin/.npm/_logs/2022-06-22T23_45_27_778Z-debug-0.log


# npm resolution error report

2022-06-22T23:45:44.074Z

While resolving: @typescript-eslint/[email protected]
Found: @typescript-eslint/[email protected]
node_modules/@typescript-eslint/parser
  dev @typescript-eslint/parser@"^4.12.0" from the root project

Could not resolve dependency:
peer @typescript-eslint/parser@"^5.0.0" from @typescript-eslint/[email protected]
node_modules/@typescript-eslint/eslint-plugin
  dev @typescript-eslint/eslint-plugin@"^5.8.1" from the root project

Conflicting peer dependency: @typescript-eslint/[email protected]
node_modules/@typescript-eslint/parser
  peer @typescript-eslint/parser@"^5.0.0" from @typescript-eslint/[email protected]
  node_modules/@typescript-eslint/eslint-plugin
    dev @typescript-eslint/eslint-plugin@"^5.8.1" from the root project

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Raw JSON explanation object:

{
  "code": "ERESOLVE",
  "edge": {
    "type": "peer",
    "name": "@typescript-eslint/parser",
    "spec": "^5.0.0",
    "error": "INVALID",
    "from": {
      "name": "@typescript-eslint/eslint-plugin",
      "version": "5.8.1",
      "location": "node_modules/@typescript-eslint/eslint-plugin",
      "isWorkspace": false,
      "dependents": [
        {
          "type": "dev",
          "name": "@typescript-eslint/eslint-plugin",
          "spec": "^5.8.1",
          "from": {
            "location": "/mnt/c/Users/copennin/Code/Sandbox/communication-services-web-calling-hero/Server"
          }
        }
      ]
    }
  },
  "dep": {
    "name": "@typescript-eslint/parser",
    "version": "5.29.0",
    "whileInstalling": {
      "name": "@typescript-eslint/eslint-plugin",
      "version": "5.8.1",
      "path": "/mnt/c/Users/copennin/Code/Sandbox/communication-services-web-calling-hero/Server/node_modules/@typescript-eslint/eslint-plugin"
    },
    "location": "node_modules/@typescript-eslint/parser",
    "isWorkspace": false,
    "dependents": [
      {
        "type": "peer",
        "name": "@typescript-eslint/parser",
        "spec": "^5.0.0",
        "error": "INVALID",
        "from": {
          "name": "@typescript-eslint/eslint-plugin",
          "version": "5.8.1",
          "location": "node_modules/@typescript-eslint/eslint-plugin",
          "isWorkspace": false,
          "dependents": [
            {
              "type": "dev",
              "name": "@typescript-eslint/eslint-plugin",
              "spec": "^5.8.1",
              "from": {
                "location": "/mnt/c/Users/copennin/Code/Sandbox/communication-services-web-calling-hero/Server"
              }
            }
          ]
        }
      }
    ]
  },
  "current": {
    "name": "@typescript-eslint/parser",
    "version": "4.33.0",
    "location": "node_modules/@typescript-eslint/parser",
    "isWorkspace": false,
    "dependents": [
      {
        "type": "dev",
        "name": "@typescript-eslint/parser",
        "spec": "^4.12.0",
        "from": {
          "location": "/mnt/c/Users/copennin/Code/Sandbox/communication-services-web-calling-hero/Server"
        }
      }
    ]
  },
  "peerConflict": {
    "current": {
      "name": "@typescript-eslint/parser",
      "version": "4.33.0",
      "location": "node_modules/@typescript-eslint/parser",
      "isWorkspace": false,
      "dependents": [
        {
          "type": "dev",
          "name": "@typescript-eslint/parser",
          "spec": "^4.12.0",
          "from": {
            "location": "/mnt/c/Users/copennin/Code/Sandbox/communication-services-web-calling-hero/Server"
          }
        }
      ]
    },
    "peer": {
      "name": "@typescript-eslint/parser",
      "version": "5.29.0",
      "whileInstalling": {
        "name": "@typescript-eslint/eslint-plugin",
        "version": "5.8.1",
        "path": "/mnt/c/Users/copennin/Code/Sandbox/communication-services-web-calling-hero/Server/node_modules/@typescript-eslint/eslint-plugin"
      },
      "location": "node_modules/@typescript-eslint/parser",
      "isWorkspace": false,
      "dependents": [
        {
          "type": "peer",
          "name": "@typescript-eslint/parser",
          "spec": "^5.0.0",
          "error": "INVALID",
          "from": {
            "name": "@typescript-eslint/eslint-plugin",
            "version": "5.8.1",
            "location": "node_modules/@typescript-eslint/eslint-plugin",
            "isWorkspace": false,
            "dependents": [
              {
                "type": "dev",
                "name": "@typescript-eslint/eslint-plugin",
                "spec": "^5.8.1",
                "from": {
                  "location": "/mnt/c/Users/copennin/Code/Sandbox/communication-services-web-calling-hero/Server"
                }
              }
            ]
          }
        }
      ]
    }
  },
  "strictPeerDeps": false,
  "force": false,
  "isMine": true
}

Expected/desired behavior

npm run setup completes as expected

OS and Version?

Windows 10 and Ubuntu 20.04 WSL 5.10.102.1-microsoft-standard-WSL2 #1 SMP x86_64 GNU/Linux

Versions

These versions do not work:
07:21:47 copennin@Copennin-Work-SurfaceBook communication-services-web-calling-hero ±|main ✗|→ nvm list
v17.9.1
v18.2.0
v18.3.0

This node version works:
node -v
v14.19.3

Mention any other details that might be useful


Thanks! We'll be in touch soon.

Deploy to Azure not working

Although there is a button called 'deploy to azure' in README.md, the following error is received once redirected to azure:

There was an error downloading the template from URI 'https://raw.githubusercontent.com/Azure-Samples/communication-services-web-calling-hero/main/deploy/azuredeploy.json'. Ensure that the template is publicly accessible and that the publisher has enabled CORS policy on the endpoint. To deploy this template, download the template manually and paste the contents in the 'Build your own template in the editor' option below.

Test Issue for Github bot to Teams

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.

Black video view on both device and laptop

Describe the bug

One or both of the video vies are black when making the call. It works occasionally, but it should be reliable.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy app
  2. Start call from laptop
  3. Join from phone
  4. One or both screens are black. If not from start it happens when switching camera.

Expected behavior

Expected both video views to work smooth.

Screenshots

Here is what I see on laptop:

az com

Here is what I see on iPhone:

IMG_2312

Desktop (please complete the following information):

  • OS laptop: Pop OS (linux)
  • Version: "20.10"
  • Browser: Chrome

Smartphone (please complete the following information):

  • IOS software version: 14.4.2
  • Safari

Logs
I see some

Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

on client in browser logs.

fail: Microsoft.AspNetCore.SpaServices[0] 'react-scripts' is not recognized as an internal or external command,

When run "dotnet build", it retuned "okay".
However, when run "dotnet run", it returned the following error msg.

fail: Microsoft.AspNetCore.SpaServices[0]
'react-scripts' is not recognized as an internal or external command,

  operable program or batch file.
  npm ERR! code ELIFECYCLE

npmfail: Microsoft.AspNetCore.SpaServices[0]
npm ERR! errno 1
npm ERR! [email protected] start: rimraf ./build && react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

fail: Microsoft.AspNetCore.SpaServices[0]
npm ERR! A complete log of this run can be found in:

Any suggestion would be helpful!!
Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.