Teams Retains Stale App Metadata After Removing and Re-uploading a Sideloaded App

After the app is removed and subsequently re-uploaded, Microsoft Teams appears to retain stale application metadata or session information from the previous installation. This may include the previous app identity, bot or static tab references, and WebView session state.

As a result, Teams may display errors such as "This app can't be found" or prevent navigation to the Messages/Chat section, even though the application configuration and React routing are functioning correctly.

The issue appears to occur particularly when the application is re-uploaded using the same manifest version. Completely quitting and restarting Teams may temporarily resolve the problem.

Expected Behavior

After removing a sideloaded app and uploading it again, Teams should load the latest application configuration and should not retain stale metadata or session state from the previous installation.

Actual Behavior

Teams may continue using stale app metadata or session state after the app has been removed and re-uploaded, resulting in navigation failures or "This app can't be found" errors.