App versioning - confusing alerts

My app has versions.
After releasing a new minor patch, this alert is shown:

It's a bit confusing.

"No release published yet".

Ahh, yep, v0.1.9 is published...

From memory, this alert used to be displayed only if you were not using versions. Now it's displayed permanently. Is this intended behavior?

3 Likes

Hey @hansontools - thanks for reaching out. My guess is that you just need to refresh the page, as you shouldn't be seeing that message if the v0.1.9 release was already published. That does seem to be a reproducible bug, though. I'll document it internally and let you know when it's been fixed. :+1:

Been happening to me too. Several times in the last few days. Sure refreshing the browser fixes it, at the expense of losing all sorts of state. :firecracker:

2 Likes

Whenever I attempt to publish any of my apps, I get the following error message:

Does anyone know what would be causing this?

Hi @tomm, I just merged your question into this existing topic so you can track the status of this bug here.

Furthermore, if in this state you try to use the "Latest version" :arrow_forward: button, it doesn't load the newest version in a new tab (with ?_releaseVersion=latest in the URL), but rather the Published version (so, no version param in the URL).

Screenshot 2025-09-09 at 4.58.09 PM

Until you refresh the page, of courseβ€”then it works again.

Maybe an obvious side effect, but worth noting nonetheless.

1 Like

Also experiencing this bug on all apps regardless of refresh

Just to clarify, @kyleteal, are you seeing the No release published yet message even after refreshing the page?

Sorry, after a refresh it goes away, but then publishing again causes it to come back

Ah okay, that is unfortunately the same buggy behavior that others are describing. The new release is actually being created and published, but the UI gets out of sync. We're actively tracking this and will hopefully be able to share an update soon.

2 Likes

Adding to the chorus.

1 Like

Hey all - the 3.278 release contains a fix for this particular issue. Please let us know if you continue to notice any odd behavior!