search

skrafft / react-native-jitsi-meet

React native wrapper for Jitsi Meet SDK
Apache License 2.0
285 stars 349 forks source link

featureFlags caching #161

Open batuhansahan opened 4 years ago

batuhansahan commented 4 years ago

i have added chat.enabled,true in call function and chat.enabled,false in audioCall function

but when i join with .call() function it shows chat box and leave the conference(still in app but i leave conference with endCall()) and join another conference with audioCall() it still remembering chat.enabled=true is it caching in somewhere how to dynamicly change flags,

note:i tried in reverse , if i close app and join audioCall chat.enabled=false but if i join another conference with .call() it stills chat.enabled=false so in reverse its same.

call function

  ...
 RNJitsiMeetConferenceOptions options = new RNJitsiMeetConferenceOptions.Builder()
       .setRoom(url)
       .setFeatureFlag("chat.enabled",true)
       .setUserInfo(_userInfo)
       .build();
  ...

audioCall function

  ...
 RNJitsiMeetConferenceOptions options = new RNJitsiMeetConferenceOptions.Builder()
       .setRoom(url)
       .setFeatureFlag("chat.enabled",false)
       .setUserInfo(_userInfo)
       .build();
  ...

@skrafft

zhenghow93 commented 2 years ago

I'm having the same issue with Android. Had to restart metro bundler (for debug build) or restart app (for release build) in order for the new feature flag to take effect. Still trying hard to find out the cause. =(

It works perfectly fine with iOS though.