Skip to content
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

🐛 [BUG] - Video Call Request fails after init #1385

Open
kinga112 opened this issue Aug 15, 2024 · 2 comments
Open

🐛 [BUG] - Video Call Request fails after init #1385

kinga112 opened this issue Aug 15, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@kinga112
Copy link

Expected Behaviour

Setup for video call works as written in docs.

Current Behaviour

call fails when sending request to recipient(s) after init.

Video.js:288 error in request ReferenceError: process is not defined
at resume (_stream_readable.js:832:1)
at Readable.resume (_stream_readable.js:824:1)
at Readable.on (_stream_readable.js:753:1)
at Video. (Video.js:191:1)
at Generator.next ()
at fulfilled (tslib.es6.mjs:118:41)

[41148:0814/222453.962304:ERROR:socket_manager.cc(141)] Failed to resolve address for ec2-54-210-214-72.compute-1.amazonaws.com., errorcode: -105

Reproduction steps

Follow docs for video setup. 
1. Setup stream.
2. Init video.
3. Request call.

Screenshots

No response

Relevant Logs

Video.js:288 error in request ReferenceError: process is not defined
    at resume (_stream_readable.js:832:1)
    at Readable.resume (_stream_readable.js:824:1)
    at Readable.on (_stream_readable.js:753:1)
    at Video.<anonymous> (Video.js:191:1)
    at Generator.next (<anonymous>)
    at fulfilled (tslib.es6.mjs:118:41)

[41148:0814/222453.962304:ERROR:socket_manager.cc(141)] Failed to resolve address for ec2-54-210-214-72.compute-1.amazonaws.com., errorcode: -105

Dapp Env

Staging (staging.push.org)

Browsers

No response

@kinga112 kinga112 added the bug Something isn't working label Aug 15, 2024
@kinga112
Copy link
Author

When changing ENV to DEV, I get this error which seems more promising.
ChatId not found between local user (address1) and recipient (address2).

Are different ENV running different versions of push?

@kinga112
Copy link
Author

kinga112 commented Aug 15, 2024

I guess a chatId is needed although the docs say it is not required. When adding a chatId of the group the call is requesting, I still get errors.

Here are the rules I use for the chatId:

const rules: VideoNotificationRules = {
      access: {
        type: VIDEO_NOTIFICATION_ACCESS_TYPE.PUSH_CHAT,
        data: {
          chatId: chatId,
        },
      },
    }

The errors generated from the VideoV2 request:

Video.js:288 error in request ReferenceError: process is not defined
    at resume (_stream_readable.js:832:1)
    at Readable.resume (_stream_readable.js:824:1)
    at Readable.on (_stream_readable.js:753:1)
    at Video.<anonymous> (Video.js:191:1)
    at Generator.next (<anonymous>)
    at fulfilled (tslib.es6.mjs:118:41)

[54328:0815/103133.284801:ERROR:socket_manager.cc(141)] Failed to resolve address for ec2-54-210-214-72.compute-1.amazonaws.com., errorcode: -105

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant