SPFx Copilot Apps Cache Old Versions of Javascript 24+ hours

[SimonDoy]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

None

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

Microsoft Edge - Version 151.0.4129.101
SPFX 1.24.0-beta.2

Describe the bug / error

I have been evolving the MyDay sample and adding in a MS Graph data source.
The Copilot App works beautifully in the Copilot Dashboard but would not work in the M365 Copilot App or https://m365.cloud.microsoft.
After releasing a few different versions, I realised that the version being loaded was stuck on an old version.
Following new solution, copilot component ids, deleting the agent, solution etc. I deployed a new version and it was still loading the old code.

However, running from Copilot App in MS Teams the new code was loading and the app was working.

Finally, this morning (after about 36 hours or so) the app is working in the M365 Copilot browser but not in the M365 Copilot App
This will be difficult for developers to evolve their solutions if they are testing things out in the proper apps before releasing to the organisation.

I have tried deleting browser cache, running in new browser work profile etc to make sure its not client side cache.

Steps to reproduce

1. Build your Copilot App
2. Deploy Copillot App and run in M365 Copilot App
3. Update Copilot App, increase versions of solution and agent, deploy solution, add to teams, and run in M365 Copilot App and see old code running.

Expected behavior

New code is loaded following new solution deployment.

Working in M365 Copilot Website.

Not working M365 Copilot App

[Ashlesha-MSFT]

I was able to reproduce this issue in my tenant after updating the existing deployed package without uninstalling it.

The updated component loads successfully in the browser and displays CACHE TEST 4 - NEW CODE, as shown in the attached screenshot. However, the same agent encounters an error when tested in the desktop app.

This indicates host-specific behavior: the latest package works in the browser but fails in the app. I will raise a bug with the relevant engineering team for further investigation.

[SimonDoy]

Thanks Ashlesha-MSFT

[VesaJuvonen]

Hi Simon Doy (@SimonDoy),
can you provide a bit more details on the model as they are different owners on different sides of the journey.

• What exactly was changed - did you do modifications with parametrization of the component? - That will generate different json file for MCP Apps and the new mapping will take a while to reset the changes - this is something which we are changing
  • If you simply change the UX JavaScript - to change what is rendered - that should definitely not happen as the code is served directly from the SharePoint App Catalog - without any caching. That's on us to check
• Can we get HAR file and console log - saved as a file

Hopefully you can still repro this and have time to share the assets. You know my email - you can share that directly with me if works. We definitely want to look more detailed on what happens here.

[SimonDoy]

Hey Vesa Juvonen (@VesaJuvonen)
Of course! Let me pull that together, might struggle over the next day or so but will put sometime in the diary to do on Friday.