LiveKit Community

peer connection is null when other participant connected react native

Please thread your messages :pray::skin-tone-4:  

hey <@U04SGR714B0>, already got the info on the github issue. don’t need to repeat it here. there’s currently no progress at the moment, will try to get to it soon

It’s less about the number of participants, and more about the total number of tracks being forwarded through that machine. If you start to hit the resource limits of a single machine hosting multiple rooms, you’d move a room to another node. If you’re reaching the limit for a single room, then you have to figure out how to split a single room across multiple SFUs.

Also fwiw, I don’t think any product on earth has hosted 100M simultaneous participants in a live event. :upside_down_face: 

Hello <@U0411KFD5NX>, to my knowledge, the multi-home feature isn't open-source currently. Only a feature available to the LiveKit cloud service.

When I try to publish/unpublish the screenshare track, It's subscribed after publish too.
But subscribe is not working correctly.
I tried to call `setSubscribed` But it's showing `desired` status without subscribe

`setSubscribed` initiates a request to the server
from this point a publication is `desired`.
When it actually arrives, the status jumps from `desired` to `subscribed`.
`isDesired` is always `true` if the intent to subscribe has been signaled, or if `setSubscribed(false)` has not been set. explicitly

It's not converted from desired to subscribed

Can you share some of your code? That makes it easier to see what’s going on.

desired will always be true if you have `autoSubscribe` enabled - which is enabled by default

Understand.
Thanks. So it's getting desired status

`subscriptionStatus` will transition from desired to subscribed once the track actually arrives. `isDesired` will constantly be true in the autoSubscribe case

Got it. So when the track is published with autosubscribe, it's desired

actually local tracks will always be desired (and subscribed) as the concept of subscription only really makes sense for remote tracks!

The experience for a remote participant is as if the screenshare is happening at 15 FPS rather than the 30 I am trying to specify.

I'm trying to specify `resolution` to be `ScreenSharePresets.h1080fps30.resolution` so that screensharing is happening at 30fps. However, the frame rate is still very jerky.

I'm specifying resolution at every reasonable place I can think to, e,g:

```room.localParticipant.createScreenTracks({
        audio: true,
        resolution: ScreenSharePresets.h1080fps30.resolution,
      })```
```const trackDefaultOptions =  {
  audioBitrate: AudioPresets.music.maxBitrate,
  dtx: true,
  red: true,
  forceStereo: false,
  simulcast: true,
  screenShareEncoding: ScreenSharePresets.h1080fps30.encoding,
  stopMicTrackOnMute: false,
  videoCodec: 'vp8',
  backupCodec: { codec: 'vp8', encoding: VideoPresets.h540.encoding },
}

// ...

room.localParticipant.publishTrack(track, trackDefaultOptions);```


unfortunately not currently. we do not have a protocol message to notify others in the room for the current participant's connection.. this would be useful tho. something to think about

Couldn't one use the signal strength as some sort of metric.. if strength is low to none .. video is not being received .. act based on that? As a workaround? Simply something which I'm thinking.

Could be, I thought I could use ConnectionQualityChanged event but it is not emitted while users are offline. Another way I came up with is to send ping via data channel to other participants. If one doesn’t receive ping anymore then I could display ‘Connecting…’ label but that looks to naive to me.

Hey Olivier, can you share more information here?

how are you publishing your tracks? code snippets would be helpful. also take a look at <https://docs.livekit.io/client/publish/#advanced-track-management|this section>, you can customize publishing resolution/etc

Thank you very much David, we look at it and come back to you with further information 

Hi Atanu, please only post a single message/question/help request in one channel. :pray::skin-tone-4:  

if you are running the tester locally, against a VM in the cloud, you are going to run into bandwidth constraints on your network. simulating 24 publishers means you'll nee about 40Mbps of upstream. I'd suggest running the load tester in a cloud environment with 1Gbps network

cc <@U02BH3ZHJ0Y> 

Please do not pin messages in public channels. :pray::skin-tone-4:  

that shouldn't be happening. our SDKs should be backwards compatible. Can you share client logs while you are getting disconnected?

I will try to update tomorrow again and see if the problem persists

Screenshot 2023-03-11 at 18.27.43.png

Screenshot 2023-03-11 at 18.28.14.png

Are the 50 users viewing also able to publish, i. e. do they have publish permissions?

Any publish is up stream.
Subscribe is down stream.

So, in your case, initially, there is
• One publish - that is up stream
• 50 subscribe - that is all down stream
If the viewers have publish permissions and they enable camera/screen share, they become publishers and the streams they send up to the server will be up stream.

Thankyou <@U02CM28PB4Y> for resolving my doubt.

you can use <https://github.com/livekit/protocol/blob/main/livekit_egress.proto#L208> or <https://github.com/livekit/protocol/blob/main/livekit_egress.proto#L195> with the egress request

When using PiP for a video &amp; enabled adaptiveStream then the video get paused when user will change the tab or windows. Possible solution to change setting for that particular track but need to change the JS SDK little bit. I have opened a pull request here: <https://github.com/livekit/client-sdk-js/pull/617> CC: <@U02EU2ZPTQU>

Hello Guys, we just started app development for livekit.

Running load tests I am looking for metrics from livekit-cli in load-test mode.
Does livekit-cli provide metrics?? if yes, how to activate/configure it?

hi <@U04UKAQ6ASU>
we simply forgot to add this!
thanks for letting us know :slightly_smiling_face:
tracking it here: <https://github.com/livekit/components-js/pull/356>

this is merged now and will be part of the next release!

This is awesome <@U02EU2ZPTQU>! Great work :fire:!

I'm surprised that you are noticing audio degrade. Are you using a samplebuilder to reorder packets? See <https://github.com/livekit/server-sdk-go/blob/main/examples/filesaver/main.go#L100|here> for an example.

it also depends on your encode settings.

this is definitely unexpected. how do you determine that the participant doesn't appear as remote for others? does room.getParticipantByIdentity("other user") return anything?

I haven’t tried getParticipantByIdentity. I investigate what’s in room.participants map. And in this case for one of participants room.participants was missing two entries compared to room.participants in my browser.

has anyone reconnected during this period? we have not seen this reported anywhere before. 

The last time I remember nobody reconnected. The participant with the issue couldn’t see another participant X but I could (participant X wasn’t in his room.participants). Then participant X joined from mobile device (different token so let’s call him Y). I could see both X and Y but the participant with the issue could only see Y.

ok, let me know if you do manage to reproduce it.

if participant with issue refreshes.. does the participant X come back?

One time when the issue occured he was able to see everyone after switching from firefox to chrome. But he also joined a room with a new token.

hmm it sounds like it happened multiple times for the same user?

At least 3 time for this one. Each time it’s the same room, the same participant’s name, different participant’s identity.

hmm.. name should not have anything to do with it.. I wonder if you spot anything in the logs for this user..

any other things that stands out to you in terms of the device/browser the user is using?

Hello <@U01KZ61GV5Z>. I think I relied on ParticipantConnected event too much. Participants list may change during connection/reconnection without emitting this event. Now I always check room.participants list after Connected and Reconnected events and it’s been working fine so far.

load: it should be seconds to startup.
shutdown: it depends on if there are users connected to it. If so, the server would not exit until users disconnect

Are there cases when the load will take longer? I'm using docker compose at the moment, which isn't a supported platform specifically. But I've seen it take not too much time to load -&gt; 10 minutes to shutdown (without any users connected) -&gt; &gt;20 minutes to start up again. I do have a websocket connection enabled.

Are there any settings for debugging setup time?  Perhaps there are relevant metrics. Is there a better signal than SIGKILL to use? Are there wal's that should be cleared that the livekit server might be going through?

no, that should not happen. to shutdown you'd want to send SIGTERM. If you are sending SIGKILL, it would definitely terminate immediately.. OS would kill the process

image.png

I don’t believe you can run the sample from within Unity. Please correct me if I’m wrong <@U022KB72NFJ>!

Yes, with this SDK, only WebGL is supported at the moment.

The Native SDK should be ready really soon

So how should I modify and test it if I cannot run within Unity?

Hey, you can’t at the moment, we’re working on a Native SDK that allows to do that.

And you are sure you're code isn't looking at: <https://docs.livekit.io/client-sdk-js/enums/ConnectionQuality.html>?

Also does "Connected" event work? Becouse i don't received it

As suggestion, if you could share some code, maybe it would be easier to pin point the issue a bit better.

<@U032TUAL4KT> it is my code
```this.roomLiveKit.on(RoomEvent.ConnectionQualityChanged, this.handleConnectionStateChanged)

my function
handleConnectionStateChanged(ConnectionState) {
    console.log('handleConnectionStateChanged', ConnectionState);
    if (this.dev) {
        ElNotification({
            message: "Connection state changed to: " + ConnectionState,
            duration: 5000,
        });
    }
},```
then i receive excelent

with Connect somthing similar, other events that i use works fine

it is interesting/ One moment i check if it has another args)

The issue is here:
```this.roomLiveKit.on(RoomEvent.ConnectionQualityChanged, this.handleConnectionStateChanged)```

should be:
```this.roomLiveKit.on(RoomEvent.ConnectionStateChanged, this.handleConnectionStateChanged)```

Sorry I got confused here for a second. Hope this helps :slightly_smiling_face:

oh my god. what the shame. Sorry and big thanks

Hi,
How to update video resolution and simulcast setting using restapi or curl or cli

Regards,
Atanu

Anyone here who can see why the video doesn't start playing in session id: RM_jBXEeMnoVBYh ?

<@U01NZKTNE1H> <@U01KZ61GV5Z> sorry to tag you here, but I don't know who else I can reach out to for help on this issue.

Can you provide more details to what's going on? What SDK are you using, and how did you set up the server.

We use the CLI to publish a RTSP stream (using gstreamer) to a room from an IoT device. The viewer joins the room from a mobile app built upon the React SDK. We simulated with the javascript SDK, but it has the same behavior. We use the livekit cloud environment.

We have +200 devices in the field with the same setup and they are working, this is the first where we see that the video stream isn't playing. Everything else related to the connection seems to build up fine.

So the question now is: why is this happening and how can we debug the issue to learn more?

<@U01KZ61GV5Z> Is there a place in LK cloud where we can see extended logs?

I see, so the only thing that isn't working is the RTSP stream published via GStreamer? are you sending keyframes at a frequent interval?

just FYI, livekit does not manipulate the video on the server side,

<@U01KZ61GV5Z> The camera has been setup with a keyframe interval of 15 and GStreamer is just publishing the RTSP as a tcpserversink to which the CLI can connect. Setting the FPS to 15 in the CLI join room/publish command does not have effect.

it's a bit difficult for us to see what's going on with such a setup. If you can share a link to a session where video published by CLI wasn't working. I'm happy to take a deeper look at the logs to see if I can spot anything there.

my hunch is there's some difference with the frames published by GStreamer / CLI that's causing this.

Hey <@U04HKR5JXC1> we are unaware of any issues on our side. Could you share a couple of session links and timestamps where folks have reported getting disconnected?

Any client side logs would be helpful to see too.

Hi again, coming back to this, we added some metrics with the disconnections errors and started tracking. We can see the following error repeatedly: `RTCDataChannel send queue is full`  - os this queue setting something you can change from the server side?
cc <@U04U27TEU79>

This is the client side queue getting full. There is no control on server side to set the size.

What rate are you sending data at?

I think you would need something like flow control to ensure that there is no overflow - <https://developer.mozilla.org/en-US/docs/Web/API/RTCDataChannel/bufferedAmount>

thanks for the data, we are checking the client code

<@U04HKR5JXC1> I think we might not be firing that event from the LiveKit side today.. Let me know if that would be useful, I think it'll make sense to add flow control events to the JS SDK

what do you mean that you are not firing that event? you are not seeing it on some logs or metrics or did you change something server side?

Screenshot 2023-03-23 at 09.44.43.png

The RTCDataChannal issue count went down a lot, we still have some errors that we are investigating but most likely it’s an implementation issue on the client side.

sorry that I wasn't clear. RTCDataChannel uses two events for flow control:
• <https://developer.mozilla.org/en-US/docs/Web/API/RTCDataChannel/bufferedamountlow_event|bufferedamountlow>
• <https://developer.mozilla.org/en-US/docs/Web/API/RTCDataChannel/error_event|error>: this is what you saw, when too much unsent data is buffered, and the application tries to send more.
Currently neither is exposed to the end user, since we expose the data packet interface. I'm thinking it'd probably be a good idea for us to buffer up these messages internally, and/or offer feedback with <https://docs.livekit.io/client-sdk-js/classes/LocalParticipant.html#publishData|publishData>.

Thanks <@U01KZ61GV5Z> for the explanation. Yes, I think it would be good to have an event about buffer full so the client app can react and set to a state where it doesn’t send anymore until the queue is ok to receive new messages.

Hello team,
We are hosting the Metaverse Fashion Week and we are having problems with some users that get constantly reconnected, still researching the client, metrics and bugs but wanted to check if there is anything that you can check on your side and see if the cluster is working fine or do you see anything unusual?

Hey <@U04HKR5JXC1>, things looking good here. Do you have an example session of a user having issues? we can take a look on our side

also, I'm really curious about metaverse fashion week! gonna check out the event as well :blush: 

<https://events.decentraland.org/> :sunglasses:

we added the livekit session id and room id to the metrics, eventually we will be able to provide more details

we released `v1.8.0` of the client-sdk-js that exposes buffer info as events with `RoomEvent.DCBufferStatusChanged`

Hi,
I  download LiveKit server and when execute "mage" this error appears "installing wire latest
Error: CreateFile C:\Users\x\go\bin\bin\wire: The system cannot find the file specified".
what is the file does it mean?
the path exist and there is one file in side it "wire.exe"

hi <@U04UL2WJ7PU>, are you using LK Cloud or self-hosted?

Thanks for reaching out. We are using the LK Cloud. Once the room is connected, the event listener for the room is registered. The event listener then picks up the subscribed tracks, and notifies the video view to show the video track. Currently, we only have one video track (host) per room.

This doesn’t sound normal. cc <@U01KZ61GV5Z> 

hey <@U04UL2WJ7PU>  can you try to ping livekit cloud from your pc? I want to know the network latency and if there is any packet loss.

Normally, flutter, like other webrtc native apps, can subscribe to video streams in a very short period of time, unless there is a delay in signaling or transmission.

to do this, ping `https://&lt;your cloud project URL&gt;`

In addition, if you are running flutter app in debug mode, the connection speed may slow down, you can try to add --profile or --release parameter to flutter run.

I pinged livekit cloud from my pc: 91ms average with no packet loss.

I did find that it shows faster in release mode. It takes me about 1 second (or slightly above, but never less than) to get connected to the room. Is this normal? Or should it be faster?

I think a delay of around 1 second is normal, because there are several interactions to establish the peerconnection when the first signaling connection is made.

Let me guess, are you trying to develop live streaming’s flipping up and down to switch video sources?

Yes. That is what I am trying to do. By the way, to do so, should I make room instance for each room? Or can I just use one room instance to disconnect and connect each time I scroll up and down?

Using the same signaling connection to switch rooms should be the perfect solution, but livekit-server does not seem to support this scenario at present.
I think you can try let the publisher connect to the same room, then turn off the viewer’s automatic subscription, and switch the source by manually subscribing. This should be much faster than having a separate room instance for each video source.

you can also "preload" the next room, i.e. connect to the next room, subscribe to the tracks. that should give you a seamless experience there. All of these type of services (including TikTok) preload ahead of time, so that the transition would appear to be instantaneous.

``` LOG  setting audio track muted
 LOG  request allowed to bypass queue: {"canPass": false, "req": {"$case": "mute", "mute": {"muted": true, "sid": "TR_AMgEsN3j2v4iAY"}}}
 LOG  room event trackMuted {"args": [{"_events": [Object], "_eventsCount": 2, "_maxListeners": 100, "handleMuted": [Function anonymous], "handleTrackEnded": [Function anonymous], "handleUnmuted": [Function anonymous], "kind": "audio", "metadataMuted": false, "mimeType": "", "options": [Object], "source": "microphone", "track": [os], "trackInfo": [Object], "trackName": "", "trackSid": "TR_AMgEsN3j2v4iAY"}, {"_connectionQuality": "excellent", "_events": [Object], "_eventsCount": 8, "_maxListeners": 100, "allParticipantsAllowedToSubscribe": true, "audioLevel": 0, "audioTracks": [Map], "engine": [Sa], "handleDisconnected": [Function anonymous], "handleLocalTrackUnpublished": [Function anonymous], "handleReconnected": [Function anonymous], "handleReconnecting": [Function anonymous], "handleSubscribedQualityUpdate": [Function anonymous], "handleTrackEnded": [Function anonymous], "identity": "5d0d118b-f9c9-4bf5-b305-9c18d733f45c", "isSpeaking": false, "lastSpokeAt": 2023-03-19T22:53:07.233Z, "metadata": "", "microphoneError": undefined, "name": "Jonathan", "onTrackMuted": [Function anonymous], "onTrackUnmuted": [Function anonymous], "onTrackUpstreamPaused": [Function anonymous], "onTrackUpstreamResumed": [Function anonymous], "participantInfo": [Object], "participantTrackPermissions": [Array], "pendingPublishPromises": [Map], "pendingPublishing": [Set], "permissions": [Object], "reconnectFuture": undefined, "roomOptions": [Object], "sid": "PA_5dgBaM9imdS6", "tracks": [Map], "updateTrackSubscriptionPermissions": [Function anonymous], "videoTracks": [Map]}], "event": "trackMuted"}
 LOG  Error toggling mic [TypeError: undefined is not a function]
 LOG  update participant info {"info": {"identity": "5d0d118b-f9c9-4bf5-b305-9c18d733f45c", "isPublisher": true, "joinedAt": 1679266374, "metadata": "", "name": "Jonathan", "permission": {"canPublish": true, "canPublishData": true, "canPublishSources": [Array], "canSubscribe": true, "hidden": false, "recorder": false}, "region": "lapsoutha", "sid": "PA_5dgBaM9imdS6", "state": 2, "tracks": [[Object]], "version": 16}}```

<@U01KZ0SCDKL> <@U01NZKTNE1H> Open to share my code if that helps :bow:

what version of the livekit-client do you have installed?

Is there a stack trace given when the error occurs?

No stack trace other than the one shared above ^.

Is the `error toggling mic` message from your app?

CallRoom.tsx

Yep. This is my code - Error happens at line #43 and #53

Same error happens at
```await room.localParticipant.setCameraEnabled(!isCameraEnabled);```

If you take out the exception catching, does a stack trace appear in the app from the base rn error handling?

This is the trace without the catch
``` LOG  rn-webrtc:pc:DEBUG 0 addTransceiver +604ms
 LOG  rn-webrtc:pc:DEBUG 0 createOffer +122ms
 LOG  rn-webrtc:pc:DEBUG 0 createOffer OK +2ms
 LOG  rn-webrtc:pc:DEBUG 0 setLocalDescription +3ms
 LOG  rn-webrtc:pc:DEBUG 0 setLocalDescription OK +4ms
 LOG  rn-webrtc:pc:DEBUG 0 setRemoteDescription +88ms
 LOG  rn-webrtc:pc:DEBUG 0 setRemoteDescription OK +9ms
 LOG  rn-webrtc:pc:DEBUG 0 addIceCandidate +0ms
 LOG  rn-webrtc:pc:DEBUG 0 addIceCandidate +0ms
 LOG  rn-webrtc:pc:DEBUG 0 addIceCandidate +1ms
 LOG  rn-webrtc:pc:DEBUG 0 addIceCandidate +0ms
[CoreFoundation] AddInstanceForFactory: No factory registered for id &lt;CFUUID 0x6000021daf60&gt; F8BB1C28-BAE8-11D6-9C31-00039315CD46
 ERROR  Unhandled promise rejection [TypeError: undefined is not a function]
[sahaytarnapp-dev] 'Unhandled promise rejection', [TypeError: undefined is not a function]```

Does a Redbox show up when the error happens?

Simulator Screen Shot - iPhone 14 - 2023-03-23 at 13.19.59.png

if you take out the async from `toggleMic` and await from `setMicrophoneEnabled` (it’s not an async function), does the stack trace change?

I changed to this
```const toggleMic = () =&gt; {
    const isMicrophoneEnabled = room.localParticipant.isMicrophoneEnabled;
    void room.localParticipant.setMicrophoneEnabled(!isMicrophoneEnabled);
  };```
But get the same stack and error:
``` LOG  rn-webrtc:pc:DEBUG 0 addTransceiver +2s
 LOG  rn-webrtc:pc:DEBUG 0 createOffer +121ms
 LOG  rn-webrtc:pc:DEBUG 0 createOffer OK +3ms
 LOG  rn-webrtc:pc:DEBUG 0 setLocalDescription +5ms
 LOG  rn-webrtc:pc:DEBUG 0 setLocalDescription OK +2ms
 LOG  rn-webrtc:pc:DEBUG 0 setRemoteDescription +87ms
 LOG  rn-webrtc:pc:DEBUG 0 setRemoteDescription OK +7ms
 LOG  rn-webrtc:pc:DEBUG 0 addIceCandidate +0ms
 LOG  rn-webrtc:pc:DEBUG 0 addIceCandidate +1ms
 LOG  rn-webrtc:pc:DEBUG 0 addIceCandidate +0ms
 LOG  rn-webrtc:pc:DEBUG 0 addIceCandidate +0ms
[sahaytarnapp-dev] 'Unhandled promise rejection', [TypeError: undefined is not a function]
 ERROR  Unhandled promise rejection [TypeError: undefined is not a function]```

can you go back to the original try/catch version, and add `console.log(e.stack)` in the catch?

:pray:
``` LOG  TypeError: undefined is not a function
    at run (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:149215:21>)
    at ?anon_0_ (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:149918:44>)
    at next (native)
    at asyncGeneratorStep (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4551:26>)
    at _next (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4570:29>)
    at anonymous (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4575:14>)
    at Promise (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:416715:17>)
    at anonymous (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4567:25>)
    at apply (native)
    at mute (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:149923:32>)
    at ?anon_0_ (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:150887:79>)
    at next (native)
    at asyncGeneratorStep (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4551:26>)
    at _next (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4570:29>)
    at anonymous (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4575:14>)
    at Promise (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:416715:17>)
    at anonymous (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4567:25>)
    at apply (native)
    at mute (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:150890:32>)
    at ?anon_0_ (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:151780:32>)
    at next (native)
    at asyncGeneratorStep (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4551:26>)
    at _next (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4570:29>)
    at anonymous (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4575:14>)
    at Promise (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:416715:17>)
    at anonymous (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4567:25>)
    at apply (native)
    at setTrackEnabled (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:151784:42>)
    at setMicrophoneEnabled (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:151721:38>)
    at ?anon_0_ (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:409664:59>)
    at next (native)
    at asyncGeneratorStep (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4551:26>)
    at _next (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4570:29>)
    at anonymous (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4575:14>)
    at Promise (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:416715:17>)
    at anonymous (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:4567:25>)
    at apply (native)
    at toggleMic (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:409671:27>)
    at toggleMic (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:409812:35>)
    at call (native)
    at onPress (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:237269:112>)
    at apply (native)
    at invokeFunc (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:237345:26>)
    at leadingEdge (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:237351:34>)
    at debounced (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:237397:29>)
    at _performTransitionSideEffects (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:62272:22>)
    at _receiveSignal (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:62228:45>)
    at onResponderRelease (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:62095:34>)
    at apply (native)
    at invokeGuardedCallbackProd (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:62680:21>)
    at apply (native)
    at invokeGuardedCallback (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:62766:42>)
    at apply (native)
    at invokeGuardedCallbackAndCatchFirstError (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:62769:36>)
    at executeDispatch (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:62833:48>)
    at executeDispatchesInOrder (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:62850:26>)
    at executeDispatchesAndRelease (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:63956:35>)
    at executeDispatchesAndReleaseTopLevel (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:63963:43>)
    at forEach (native)
    at forEachAccumulated (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:63292:22>)
    at runEventsInBatch (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:63974:27>)
    at runExtractedPluginEventsInBatch (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:64033:25>)
    at anonymous (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:64014:42>)
    at batchedUpdates$1 (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:74604:20>)
    at batchedUpdates (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:63945:36>)
    at _receiveRootNodeIDEvent (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:64013:23>)
    at receiveTouches (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:64056:34>)
    at apply (native)
    at __callFunction (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:2715:36>)
    at anonymous (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:2476:31>)
    at __guard (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:2666:15>)
    at callFunctionReturnFlushedQueue (<http://localhost:8081/index.bundle?platform=ios&amp;dev=true&amp;minify=false&amp;modulesOnly=false&amp;runModule=true&amp;app=com.upexpat.app.dev:2475:21>)```