Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Teams app redeployment requires reinstallation #11849

Open
lior-lew opened this issue Nov 21, 2024 · 3 comments
Open

Teams app redeployment requires reinstallation #11849

lior-lew opened this issue Nov 21, 2024 · 3 comments
Assignees

Comments

@lior-lew
Copy link

Steps to reproduce

  1. I wrote a Teams app which is already published in MS App store.
  2. I deployed and publish same code under a different name to my organization only.
  3. I installed the app and it is working.
  4. I made changes in the typescript code. the changes was to add more logging.
  5. I deployed the app without republishing it.
  6. tried to send a notification and the notification did not reach my Teams chat.
  7. uninstalled and installed the app again
  8. everything is working

Expected behavior

when deploying new code that doesn't affect the manifest/permission/scope ... I expect that the application will work without the need to uninstall and install it again. after all, I did not republish it.

Actual behavior

after deploy of new Azure function, the notifications are not reaching my teams chat.

Error details

none. I am just getting an error that the member is not found.

      //findMember is expecting a function that returns a predicate. therefore, we must use async function
      //to return a promise that resolves to a predicate (even if the actual operation is synchronous)
      async (m) => (m.account.userPrincipalName.toLowerCase() === userEmail.toLowerCase() || 
                    m.account.email.toLowerCase() === userEmail.toLowerCase())
    ).catch((error) => {
      context.log.error(`Error finding member ${userEmail}:`, error);
    });
Copy link
Contributor

Hi lior-lew! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

@Meghana-MSFT
Copy link
Collaborator

@lior-lew - This behavior seems to be expected. We will confirm this internally and get back to you.

@lior-lew
Copy link
Author

I do not understand why this is to be expected. if It was requiring a new publication or acceptance of new privileges, I would agree. However, if the only operations the customer need to perform is removing and installing of the app, it just causes inconvenience. moreover, if an issue is found with the code and I have many users, all of them will need to reinstall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants