Latest vs Stable Version Error

JMPeterson · 02-15-2023 01:51 PM

I ran into an issue where users are seeing changes that have not yet been pushed to the "Stable" version of an application. We set the "Stable" version for all users, with the only exception being the developers seeing the "Latest" version. As of 2/08 some users are able to access and see the "Latest" version changes that we have not pushed to "Stable" yet. I have verified that the app version they are running matches the assigned "Stable" version and not the current "Latest" version.

Am I not understanding how "Stable" vs "Latest" should function? We have not had this issue up until now. Being able to assign a "Stable" version and still be able to make changes on the app without impacting our field users has been a huge benefit so far.

Marc_Dillon

Can you describe what the changes are? It certainly doesn't sound like you're mistaken in your understanding. Are you assigning versions manually per user, or are you using domain auth with different groups? I suppose that last one actually shouldn't even matter though, as you said you confirmed the version numbers.

JMPeterson

The Stable version is the default version for all our users, anyone with access to any other version is manually and individually assigned through the editor.

Specifically in this case the Stable version has a set of options for the user to select, "Not Started", "In Progress", and "Completed". We also have some show/hide conditions based on these selections. Moving forward we want to update those options to "Not Reviewed", "Reviewed" and "Completed" with the associated show/hide conditions updated. I had the new options ready in the AppSheet editor, just not published to the end user. It was brought to my attention earlier today that certain fields were not working or visible to our end users as they normally are, and a quick look at the database showed that some of the data reflected the new options, "Not Reviewed", "Reviewed" and "Completed". The live show/hide conditions rely on the original terms, "Not Started", "In Progress", and "Completed".

Another thought occurred to me that I want to do some more testing on. We do have some bots and API hooks firing off in the background. I'm curious if somehow those APIs are utilizing the Latest version instead of the Stable. We have not experienced this before, so any additional ideas on where to look, test or verify is appreciated!

dbaum

@JMPeterson wrote:

I'm curious if somehow those APIs are utilizing the Latest version instead of the Stable.

I would like to think that any webhook is fired in the context of the app version that triggered it and that the app version invoked as a result of any API call is governed by the RunAsUserEmail property in the API request.

You could check the audit log, which may include app version information within the details of its entries.

JMPeterson

Great idea!

I did check and the error log for the webhook shows "AppTemplateVersion": "1.000248" which is consistent with the assigned Stable version of the app. The specific error is; Error: "Webhook HTTP request failed with exception The remote server returned an error: (400) Bad Request. "

However when I check the associated REST API invoke error I get "AppTemplateVersion": "1.000271" which is the Latest version where I had the changes queued up. The specific error for the REST API invoke is "Error: Row having key '0c0b90b7' in table 'asset' containing value 'Not Started' in field 'execution_status' failed 'Valid_If' condition", which is what we would expect because of the differences between those two versions.

I'm not sure if anyone else is in a position to verify, but it does look like a bug has been introduced. I will need to go back in the logs to see if I can pinpoint when this might have started happening. I appreciate the feedback!

Steve

Please contact AppSheet Support for help with this.

TPBuncey

I'm just wondering if you ever managed to get to the bottom of this issue?

I'm currently having exactly the same problem - my users are able to see changes that have not yet been pushed to the stable version of my app.

JMPeterson

This was the solution they pointed me towards and this looks to have worked for me. I was unaware of this as an option beforehand.

I would like to suggest these things:-
i) Go to Security.
ii) Go to "Domain Authentication".
iii) Go to "Authentication Groups" > App Version.
iv) Set it to "Stable".

I am keeping a close eye on it.

dbaum

Thanks so much for sharing this nooks-and-crannies-of-AppSheet reminder. I was not tracking this detail, and just found that I needed to fix it.