SharePoint SPFx Application Shows Updated Version at Global and Site Level, but Application Changes Are Not Reflected

Question

SharePoint SPFx Application Shows Updated Version at Global and Site Level, but Application Changes Are Not Reflected

Ankit Mulewa 0

We are experiencing an issue with our SharePoint SPFx solution, which is distributed through Microsoft AppSource.

We recently released Version 1.21 with new functionality. One of our clients successfully upgraded to Version 1.21, and the solution details also show Version 1.21. However, the newly added functionality from Version 1.21 is not appearing in this client's production environment. The solution is still behaving like the previous version.

The same Version 1.21 release is working correctly for another client.

The affected solution is running in a production environment, so we cannot remove or reinstall the existing solution for troubleshooting.

We would like to understand why the solution shows Version 1.21, but the expected Version 1.21 functionality is not being loaded in this production tenant.

Is there a supported way to resolve this issue and ensure that the latest Version 1.21 functionality is correctly loaded in the existing production installation without removing and reinstalling the solution?

Any guidance on how to troubleshoot and resolve this issue would be appreciated.

0 comments

1 answer

Your answer

Answer 1

Good day Ankit,

Just to gently clarify before going any further, this forum is separate from Microsoft Support. I don’t have the ability to access or investigate individual accounts because this is a user‑to‑user support forum.

I recommend the following checks:

Option 1: Check which JavaScript bundle is being loaded

Open the affected SharePoint page in Microsoft Edge or Google Chrome.

Press F12, or right click the page and select Inspect, then open the Network tab.

Enable Disable cache and refresh the page.

Filter the results for JS files and identify the solution bundle being loaded.

Compare the bundle URL and file content with a tenant where Version 1.21 is working correctly.

Review the Console tab for any loading, permission, or asset related errors.

This is the most important step because it confirms whether the page is loading the Version 1.21 bundle or an older version.

Option 2: Test in an InPrivate or Incognito window

This helps determine whether cached content is affecting the application behavior.

Open the affected page in an InPrivate or Incognito session.

Compare the bundle URL from that session with the URL loaded during a normal browser session.

Option 3: Contact Microsoft Support

Since this issue requires investigation within the affected tenant, I recommend opening a support request through the Microsoft 365 admin center > Support > Help & Support.

Turn off the "Support Assistant" feature.

Use the keyword "Support" to quickly bypass automated suggestions > Select Contact Support.

User's image

Provide a detailed description of the issue, including the troubleshooting steps already completed.

Attach relevant screenshots, browser console errors, network traces and any other findings.

Additionally, sharing your preferred contact times may help the support team handle the case more efficiently.

A technical support engineer can perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis.

If you have any questions, please don’t hesitate to reach out at any time.

Thank you for your patience and understanding.

If you have any extra questions about this answer, please click "Comment".