Help please

[Bjarne_Allerup]

This App have been deployed and used for the last 5 years, but today it sys this????

[Aurelien]

Thank you for the quick response @peterdykstra .

t's not a client in the sense of "I share an app to them", but rather "I help them to implement their own AppSheet platform internally".

From what I understood, they may encounter a situation by the time they get back to office. (Timezone UTC+1 here,  almost midnight).

[Joseph_Seddik]

@peterdykstra @ccchen_google @zito 

Unfortunately, the problem is still ongoing and having a wide impact that for me has become just unmanageable!! I have disabled Core Security in all GWS belonging to my customers. However, they have external users who are also using GWS and now are completely blocked.

It is impossible to ask them all to contact their IT and do the required change. My customers use the apps for Supplier Management and Customer Management, and they give access to a wide array of external users who are NOT IT staff, would NOT even know who is managing their IT and might NOT even know what a Google Workspace is. They are NOT supposed to go through all of this meaningless-nonsense to them, while trying to use a tool essential for their daily jobs. 

Please roll back this change COMPLETELY and ASAP!! 

Thanks in advance for your assistance and understanding.

[WillowMobileSys]

---

@peterdykstra wrote:

Some context in case it's helpful: there was significant prep put into ensuring minimal users were affected by the rollout of this Core license inclusion in Workspace + new security setting. Unfortunately there were edge cases that were really hard to account for

---

@peterdykstra  I sincerely appreciate the response.  Having been in software development for over 25 years, I know the difficulties of trying to account for every use case.  For AppSheet, as a retail development platform, those circumstances are increased by 100,000+ fold.  It is probably safe to say that you will NEVER fully identify all use cases.

A large portion of AppSheet apps are business daily-transaction apps. That is why AppSheet should NEVER take a black or white stance on new setting changes when first released.  In other words, Errors that will halt the app should ALWAYS be rolled out FIRST as "soft" warnings - e.g. "An error has occurred, please notify the App Creator, press ok to continue using the app." (obviously in a more detailed description!!)

It is a win-win-win...AppSheet has reports of unexepected possible app stoppage,  the App Creator becomes aware of the new setting and can change as needed for their app AND MOST IMPORTANTLY, the end user is able to continue using the app with minimal disruption.

Once there is some comfort that the settings issues are resolved, then AppSheet can switch the error to a hard stop as planned.

This is really the only way to manage these situations to prevent end user disruptions.