Skip to content
Snippets Groups Projects
  1. Mar 29, 2021
  2. Mar 23, 2021
  3. Mar 22, 2021
  4. Mar 19, 2021
  5. Mar 18, 2021
  6. Mar 10, 2021
    • Anton Georgiev's avatar
      Bump up version to 2.2.36 · f4ba2e87
      Anton Georgiev authored
      f4ba2e87
    • Anton Georgiev's avatar
      Merge pull request #11608 from mariogasparoni/issue-11307-2.2 · 741130b0
      Anton Georgiev authored
      Observe both added and changed events when user joins
      741130b0
    • Mario Jr's avatar
      Observe both added and changed events when user joins · 1a75800d
      Mario Jr authored
      Depending on the sequence of events on the server, user sometimes is
      added to the users collection with the name information, and sometimes this
      information is updated in a second moment. Once we need the username
      to show the push notification, we observe changes on this field for both
      added and changed event.
      
      Closes #11307
      1a75800d
    • Anton Georgiev's avatar
      Merge pull request #11601 from mariogasparoni/backport-11533-to-2.2 · acbdf831
      Anton Georgiev authored
      Fix audio and push alerts for user join
      acbdf831
    • Anton Georgiev's avatar
      Merge pull request #11587 from mariogasparoni/fix-11333 · 38f11dbd
      Anton Georgiev authored
      Improve the way store information about breakout audio transfer
      38f11dbd
    • Mario Jr's avatar
      Fix audio and push alerts for user join · 9c92c14a
      Mario Jr authored
      When validating tokens, the dummyUser created at the beginning is set
      with validated=true. This means there won't be the state change that used
      to occur from validated:false to validated:true (which detects the moment
      joined the meeting) , therefore the alert code that expects for this change
      won't run.
      To fix this for audio alerts, we now detect when user join by observing
      additions in Users's collection. This is actually good because we start
      observing this only once (in componentDidMount), differently we used to do,
      by calling this every time the tracker was activated.
      
      To distinguish between the user addition that initially populates user's
      collection from those that happens after user join (which are the ones we
      want), we store the initial state (at componentDidMount) and compare it
      with new additions. If the user added is present at the initial state,
      then it is an addition to populates the collection, otherwise this is a real
      user addition (happened after user joined the meeting)
      
      Partially fixes #11399
      9c92c14a
  7. Mar 08, 2021
  8. Mar 05, 2021
  9. Mar 04, 2021
  10. Mar 03, 2021
  11. Mar 02, 2021
  12. Feb 26, 2021
  13. Feb 24, 2021
  14. Feb 23, 2021
Loading