1

I have tested the app both in local as well as SPO workbench. Then installed in global app catalog and deployed to SPO site collection and then added to a site page.

Now my changes are not reflecting in the target site collection page once i reinstalled/redeployed the package in the app catalog.

Can some one provide the guidance or deployment steps with best practices on the SP framework.

Improve this question
2
  • Did you update your app in the site collection.?
    – Karthik Jaganathan
    May 19, 2017 at 5:00
  • yes i did several times and removing + re-adding to the page as well
    – kesava
    May 23, 2017 at 20:58

1 Answer 1

Reset to default
4

When you recompile a new SPFx solution, it will generate by default new names for bundled JS files. This means that your existing instances are pointing to older versions of the assembly.

Steps would be as follows

  1. Deploy first version to SPO - sppkg package to app catalog and host JS files from some CDN location
  2. Perform modifications in the Solution using your editor
  3. This will generate new name for JS files - technically you could use same JS file names, but that not currently (end of May 2017) supported natively by the packaging tooling
  4. Copy new JS files to your CDN location - these are now new files
  5. Upload new version fo sppkg package to app catalog
  6. Perform an update in the sites for the package files, whcih have been deployed

We are looking into simplifying this in the future in SPFx tooling with few different options. This is however the current situation.

Improve this answer
0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.