Forum Discussion

Re: New Teams Personal Tab On Desktop Client App only works on first load

Your app needs admin consent hence I tried with my own personal tab. It is working fine after navigations. Could you please share video and logs of this issue at microsoftteamsdev@microsoft.com.

2 Replies

  • kjohari's avatar
    kjohari
    Copper Contributor

    Meghana-MSFT Hey Meghan, spent some time debugging my issue this week and it came down to how the new ms teams handles Shared Workers compared to previously. 

     

    My assumption to what was happening is on initial load after hard close of ms teams it instantiates the first instance of the Shared Worker so every works fine and connects as expected, however when leaving the tab I assume ms teams doesn't kill the shared worker and leaves it in an 'unconnectable' state so when i return to the tab and try to reconnect to the worker with its associated name it just fails. 

     

    This also explains why it was working inside the browser version of new ms-teams.

    I've implemented a temporary fix which will just spin up a new Shared Worker if it fails to connect to the already exisiting one but this was never an issue in the classic ms teams. Switching to using inline instead of a worker also fixes the issue fyi.

  • Meghana-MSFT's avatar
    Meghana-MSFT
    Former Employee

    Your app needs admin consent hence I tried with my own personal tab. It is working fine after navigations. Could you please share video and logs of this issue at microsoftteamsdev@microsoft.com.

    You mentioned this in your question. Could you please redirect us to those posts so that we have more information to check this issue.


    Like many recent posts my personal tab app is experiencing problems with connectivity.

     

Resources