Quick Update:
According to Salesforce, their R&D has identified a list of plausible changes that may have caused this issue. They are continuing to investigate in order to find a patch that fixes the issue. We will update you as things progress.

Quick Clarification on what this means if your org is on Spring 17:

• Already have Skuid installed? You are good to go and can keep working with your Skuid pages without issue. The problem will only affect if you try to upgrade your Skuid version. 


• Do not have Skuid installed? Unfortunately, you will not be able to install Skuid for the time being. 

Any update on this yet? Thanks.

Hi Skuid Community~

The Workaround
Salesforce provided a workaround for Skuid to test last night. Since then, our developers have been hard at work implementing that workaround and testing it out. Unfortunately, the workaround can only be applied to one Skuid version at a time.

Where We Are At

• We are currently verifying whether or not the workaround works with Brooklyn Iteration 3. As soon as it is available to be installed, we will notify the community.


• Skuid is continuing to engage Salesforce’s R&D department to address the root cause of the problem.

Hi Karen,

Could you provide insight on the change that occurred and caused issues?

Hi Skuid community!

Exciting news! Utilizing the workaround provided by Salesforce, Skuid developers now have Brooklyn Iteration 3 ready for everyone to download from the Skuid Releases page. As always, Skuid recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment.

What does this mean for your organization?
If your org is on Winter '17:

• Not using Skuid yet? You can install any version of Skuid. 


• Already using Skuid? 

1. You can continue to use the Skuid version you are on without problem.


2. You can upgrade to any version of Skuid after the one you are currently on.

• Not using Skuid yet? You are only able to install Brooklyn Iteration 3. 


• Already using Skuid? 

1. You can continue to use the Skuid version you are on without problem.


2. Looking to upgrade? Regardless of what Skuid version you are currently on (Superbank, Banzai, Rockaway, Brooklyn), you will only be able to upgrade to Brooklyn Iteration 3.  

We will continue to keep you updated as to where things are at with our Salesforce case. We hope to be able to update the community soon about a patch from Salesforce that addresses the root problem.

Is there any update? I’m eager to update my ORG

Hi Community~

There were changes in the back end architecture of the Salesforce Spring '17 release that prohibited installing certain versions of Skuid. Unfortunately​,​ the patch that Salesforce released to address the root cause of this issue ​did not successful​ly address the issue​.
 
What does that mean for installing Skuid since all orgs are now on Spring ‘17? 
The workaround that Salesforce provided can only be applied to one Skuid version at a time​ and it cannot be applied to all released versions of Skuid​. To minimize confusion, all versions and their accompanying release notes will be viewable from the Skuid releases page, but only versions to which the workaround has been applied will have install links.

• Running Rockaway? We know that many of you are still using Rockaway so we have applied the workaround to the latest version of Rockaway: Rockaway ​Iteration 14. 


• Running Brooklyn? You can upgrade to ​any version of ​Brooklyn ​beginning with Iteration 3.