search

push-protocol / push-sdk

Push SDK is a growing Monorepo of packages that provide solutions for a wide range of development tasks one might come across while building on top of Push protocol. It is a Javascript-based group of packages that enables easy usage of imperative communication tools for Web3
Other
66 stars 48 forks source link

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

Open kinga112 opened 4 weeks ago

kinga112 commented 4 weeks ago

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 commented 4 weeks ago

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 commented 4 weeks ago

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