Issue with unpacking pages in skuid version 11.2.16 and 11.2.18

  • 3
  • Problem
  • Updated 6 months ago
  • Solved
We were using skuid page packs as a migration process between environments without any issue on 11.2.9. Upgraded to 11.2.16 and page unpacking has stopped working. Tried to upgrade to 11.2.18 and still not working. This is a major issue since our developers do not have access to make skuid page changes in production and we use skuid page packs for migrations.

While unpacking pages see the following information message "Refreshing Pages in selected Static Resources ...." but it stays at that forever without proceeding to unpack.
Photo of Jayesh Bhatnagar

Jayesh Bhatnagar

  • 636 Points 500 badge 2x thumb
  • frustrated

Posted 6 months ago

  • 3
Photo of Mark DeSimone

Mark DeSimone, Official Rep

  • 12,066 Points 10k badge 2x thumb
Hello Jayesh,

I wanted to let you know that we are looking into a possible root cause for this, and we will keep you posted here as we learn more. To clarify, are you experiencing this issue in 11.2.16 and 11.2.18, but NOT in 11.2.9? And, is your production org affected, or is a sandbox affected?
Photo of Jayesh Bhatnagar

Jayesh Bhatnagar

  • 636 Points 500 badge 2x thumb
That is correct, it worked perfectly in 11.2.9. Issue started after we upgraded to 11.2.16. Tried upgrading to 11.2.18 after issue was identified to see if it was resolved. But issue exists in 11.2.18 as well.
Photo of Zach McElrath

Zach McElrath, Employee

  • 53,432 Points 50k badge 2x thumb
Jayesh, I believe we have identified the root cause of the issue and the fix will be delivered in 11.2.19, stay tuned.
Photo of Jayesh Bhatnagar

Jayesh Bhatnagar

  • 636 Points 500 badge 2x thumb
I see that the 11.2.19 release is out. But based on the bug descriptions associated with that release it does not look like the fix for the page pack issue made it in that release. Can you confirm?
Photo of Zach McElrath

Zach McElrath, Employee

  • 53,432 Points 50k badge 2x thumb
Jayesh, yes, the page pack issue fix was addressed in CORE-2276, which is part of 11.2.19.