Summary
In the new app builder, a published app loads fine when opened in a Safari browser tab, but launching it from an iOS home-screen icon (standalone/PWA mode) returns "Not found - Bundled app not found, please re-publish your app," and republishing does not resolve it.
AI Response
This maps to a known Safari/WebKit issue with the new app builder: a home-screen (standalone PWA) launch runs in an isolated storage context with no existing Retool session cookies, so the platform can't resolve/authenticate the published bundle and falls back to a 'not found' error. Retool engineering has been actively addressing this class of WebKit authentication failure, and in reported cases it cleared up on its own after a fix. In the meantime, clearing cookies/site data and removing then re-adding the home-screen icon (or first signing in via a normal Safari tab) is the workaround that has restored access. This is a platform hosting/auth-layer behavior rather than something fixable in the app's own code.
Sources
New Retool Beta Apps don't work in safari and duck duck go browsers
A staff-confirmed known issue where new app builder apps fail to authenticate on Safari/WebKit while classic apps work; Retool shipped a fix and clearing cookies/incognito restored access.
Documents how WebKit's isolated cookie handling on Safari/iOS blocks Retool session resolution, corroborating the root cause of a standalone launch being unable to identify the published app.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a 
, 
, or 
. Or by marking this post as the "Solution"! Let us know if you have any feedback here. 