Forum Discussion
File handler configuration does not update
Hi team,
We recently had an integration with Microsoft file handler.
During the deployment of the application, we encountered some issues, so we updated the file handler configuration via the manifest file.
Some users who installed our application still see the old file handler configuration and are experiencing problems because of it. They want to either update it to the latest configuration or remove it completely so they can continue their work normally.
We did try to guide them to reset the file handler cache as in:
https://learn.microsoft.com/en-us/onedrive/developer/file-handlers/reset-cache?view=odsp-graph-online
But seems like only some of them got the updated config, while the rest keep getting the old one, even after 1-2 weeks.
Do you have any advice on how to completely resolve this issue?
- Prasad_Das-MSFTMicrosoft
Thank you for your inquiry about your Teams app development issue! To assist you better, could you please provide the following details?
- Reproduction Steps: Please share the steps you took to encounter the issue.
- Documentation Links: Any specific documentation you followed that relates to your problem.
- ToanTranCopper Contributor
Hi Prasad,
Thank you for following up on this issue. Below are the requested details:
**Reproduction Steps:**
1. A user installs the Lumin file handler integration for OneDrive.
2. We updated the file handler configuration in the Azure App Registration (e.g., updated `logo` in the manifest).
3. While some users receive the updated configuration after clearing the file handler cache, others continue to see the old configuration despite:
- Following the steps in this documentation: https://learn.microsoft.com/en-us/onedrive/developer/file-handlers/reset-cache?view=odsp-graph-online
- Clearing their browser cache and restarting OneDrive.
- Removing the application.
4. Even after 1–2 weeks, some users are still stuck with the outdated configuration.**Expected Behavior:**
- Users should see the updated file handler configuration once the cache is reset.**Actual Behavior:**
- Some users cannot clear the old configuration and experience the outdated file handler behavior.**Documentation Followed:**
- [Resetting the File Handler Cache](https://learn.microsoft.com/en-us/onedrive/developer/file-handlers/reset-cache?view=odsp-graph-online)
- [Azure App Registration and Manifest Updates](https://learn.microsoft.com/en-us/entra/identity-platform/reference-app-manifest#addins-attribute)**Additional Details:**
- App Name: Lumin
- App ID: 2997c98e-9b39-4f93-9378-35cf0644cbf3
- The updated configuration has been verified in Azure App Registration, and it works for some users.
- Affected users come from multiple tenants, with inconsistent results.Could you advise on additional steps or perform a manual backend cache invalidation for the affected tenants?
Best regards,
Toan- Prasad_Das-MSFTMicrosoft
Apologies. This team can only help with questions related to building apps for the Microsoft Teams platform.
Could you please consider posting your query to any of the following channel?For Microsoft Teams product issues/failures your tenant Admin can reach out to Microsoft 365 Product Support.
For general questions about Microsoft Teams please post your question on Microsoft Teams Community