This App have been deployed and used for the last 5 years, but today it sys this???
1 Like
What it shows in the editor? Any other error message?
1 Like
Probably due to a security violation.
Go to Workspace Admin â AppSheet, and Turn OFF AppSheet Core Security.
1 Like
You should be able to identify that from the error message. Now it doesnât say anything about it.
1 Like
Yeah, we should, and we should have been warned before hand before suddenly introducing such a disruptive change, and we should have had clearer error messages to save us time from trying to figure out what happens.. lot of things should have happened including not running into this issue from the first place.
Anyway, hereâs resolution that I had to look for:
Add AppSheet to Google Workspace - Google Workspace Admin Help
4 Likes
It was announced in this forum earlier. Though it would be nice to have that info directly, I agree.
3 Likes
Thanks Aleksi!
I totally agree. I just had a client impacted by this. AppSheet seems to use a âslam and jamâ approach to submitting their changes. For platform that has tens of tens of thousands of App Creators, hundreds of thousands of end usersâŚit is NOT an acceptable approach. In this Day and Age, we should not be affected by app down times - regardless if it is communication problem or not.
I donât think any of the other Google tools experience these types of issues and I have to believe it is because they perform proper QA testing before releases.
5 Likes
The issue my client is having is that the app is NOT based on a Workspace account but rather an an independent Gmail account.
EDITED: For any reading⌠this error seems based on the logged in user NOT the App Creator. Not sure of the impact when the the AppCreator is based on a Workspace account but NONE of the logged in users are. I suspect the same problem since many functions are submitted with the App Creator as the user.
4 Likes
With regard to AppSheet I see filmsy QA and clumsy change management processes. Iâve been an avid Google Products user and promoter for years and this is very disappointing. Iâve never seen such disregard for paying customers. I was lucky to have been working on the app at the same moment of the impact, and was lucky the customer had made me a superadmin account on his own Workspace, so by the time he called I could tell him it would be up again in a couple of minutes.
You donât need a Workspace account to be an app creator, but you need it to resolve this issue. They have created an interruption that is even outside the hand of app creators to handle! Very very disappointing..
2 Likes
This is the clue provided through the AppSheet Editor, no comment. The âLearn Moreâ link takes you to how to define Governance Policies; a completely irrelevant subject here.
2 Likes
In the app editor, when you click the âXâ icon at the top right (next to the âSAVEâ button), it will show you the exact policy error and will provide you a link to the relevant HC article.
This is a part of the Workspace AppSheet Core security setting rolled out this week: https://www.googlecloudcommunity.com/gc/Announcements/New-AppSheet-Core-security-setting-rolling-out-info-for-app/td-p/621091.
If your Workspace admins allow your apps to be shared externally, please ask them to turn off the AppSheet Core security setting in the Workspace admin console.
1 Like
Hi @Joseph_Seddik , @WillowMobileSys - youâre right about the unhelpful error messages, looking into correcting those.
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, and Iâm sorry you both were affected, especially since youâve been part of the AppSheet product/community for so long - if youâre still encountering issues due to this, please let me know.
High level, there are steps being taken to improve how AppSheet is available for Workspace customers, how features/rules apply to different license types, and how user activity is better visible to account owners/admins, all with the goal of making the AppSheet licensing more intuitive and consistent with Workspace - this is a lot of work, but should reduce these situations in the long run where itâs hard to detect users that may be affected by updates like this.
2 Likes
It seems my clients have been affected by this issue today. I am unsure how to correct it and where exactly I need to go to fix it. Is this a Google login thing on my end as the app creator, or is there an area on AppSheet that I need to find? Please help.
2 Likes
Hi @peterdykstra I am still having this issue. Mine was defaulted off since I have been with appsheets since 2017. I turned it on and back off in an attempt to see if that helped and it is still blocking users with the security core violation
Thank you @peterdykstra
1 Like
The bigger problem is that most Citizen Developers do not have access to GWS admin console. The features of Appsheet are available to general users to make the effort to build. They do not have exposure to GWS Admin . They would never know.
5 Likes
Who reads the forum daily? Its just a forum. What a waste of time to have to do this. I have GCP and GWS administrators with core updates and actions that need to be taken have messaging them directly. Especially in advance. I agree with @Joseph_Seddik , we are lucky we have SuperAdmin and Admin status to know where to look
4 Likes
