Re: App deployement

dariusw · 03-01-2024 04:16 AM

I faced strange and crucial problem. Google support gave up and redirected me to Specialists Team. Im waiting for response but for the meantime I keep trying to understand that issue. First of all:

1. I have users I shared app with, stable version access

2. Stable version is present

3. Every possible configuration checked and fine

The issue is that everybody can see different app version after deployement is done. For me it is latest one because Im an author. For one user there is warning that sample app cant save changes (i have sample apps switched off). For third one there is some very old version on the screen. I have found one discussion on forum and there was similar problem that users could see different versions with different table structures which was crushing app. It looks similar and it was not solved. How it is possible that the same link can send to different app versions no matter what sharing configuration is done? Is there anybody facing the same issue? Please let me know even small suggestions. Half of the organization is waiting for app deployement and Im stacked, Google support gave up, Specialists Team... there is only mail from their side that issue is opened. I tried to reset and set every possible configuration many times but it is not working. It is continuously making everything to not to listen my setup.

AleksiAlkio

Have you thought to upgrade the app so they would all then start from the same version?
https://support.google.com/appsheet/answer/10105386?hl=en&sjid=11710882817275555064-EU

dariusw

Thank you. I got this idea today and told it to my Admin. It is a plan for monday if there is no action taken by Specialist Team from Google. But it is crazy to do like that. How to keep working with app if I cannot give stable version to the users and work with app further. It kills idea to use that solution in organizations. It is to big responsibility. There is aproblem now that every usercan see other app version calledby the same link. Its crazy. It is huge bug and its unacceptable. I lost 3 monts of work, a lot of people are waiting, Target date is expired and no proper solution. I read a lot about similar problem lasting for 4 years by now. Method you advised are "rescue mode" but it is not acceptable on corpo background.

AleksiAlkio

I just thought this as a temporary solution if there is something wrong with the app itself. With this test you could check if it is or is it something different.

dariusw

People are discussing how to add "refresh=1&wipe=1 " to url for users. Iwantto try but Im notsure it issolution. One guy sent a post and told it worked for him.

dariusw

I have just receive answer from Google support:

"We would like to inform you to remove all the users from the Application Shared list, then forward that to make the application a stable version of the application, then share the application with the users again, and ask app users to clear their browser cache first before using the application.

Because sometimes, due to cache history, such an issue arises.

Please ask the user to perform the above steps; if the user is still facing the same issue, then please let us know so that we can escalate further.

Could you please also ask the users to sync the application once, and after that, try to use the application?

However, if you have any other issue that needs further assistance, feel free to connect by replying back to this email or via chat.

Thanks,

AppSheet support team "

dariusw

That aswer from Google is a joke for me. What kind of solution it is. Do I really have to run all over company to take care about peoples browsers? How can I controll that? And what if I have done some next changes? Again the same. This app is sending workflow to High Management for decicion and what do I have to say for them? Sory about those 100 mistakes this month again but we have to clear browser cash again and again ang more frequently. Is that really such a problem that cant be solved for years? Its an security bridge. One of my users could see very old app version with acces to forbidden for him data. And it can happen again and again. And solution is clear and clear that cashe?