- My goal: to view my app publicly with no login required.
- Issue: I’ve changed the sharing settings to Public, when I view the app it is a black screen with the Retool logo in the bottom left and nothing else.
- Steps I've taken to troubleshoot: Used the AI chat to help troubleshoot.
- Additional info: Cloud.
1 Like
Just tested it using v1 of the Retool App builder and I can see the public page, however for my apps that were built using the v2 new Beta App builder its not working for those.
Welcome to the community, @dalem!
Ah that's what I was going to ask! Sharing via public URL isn't yet supported in the new app builder, but we plan on shipping that functionality soon after launch. I can follow up here with updates!
Thanks Darren for the reply! Ah that’ll be it then 
any possible roadmap date on public sharing for v2?
I'm not aware of a specific date, @dalem, but will reach out internally. At a high level, though, it's definitely one of the features that is targeted for the post-launch beta phase.
Hey @Darren just wondered if you were able to find a date at all for the public sharing feature? Thanks very much!
Nothing concrete, @dalem! The relevant ticket is still sitting in the backlog but will get picked up quickly post-launch. As soon as that happens, I'll have a much better idea of the timeline and will give you an update here. 
Following… the new App Builder created an incredible form I needed, but it’s useless until I can share it via a public URL 
1 Like
Could it be converted into a custom component for import into a classic app?
I don't think there's going to be a decent workaround here, unfortunately. I have added your comments to the internal tracking ticket, @pmadden, and will give y'all an update as soon as I can!
1 Like
Thanks! Any rough idea on when beta → launch will take place? Know it’s tough to predict but trying to gauge if this builder beta is like a 6 week type of thing, or 6 months…
Not committing to anything, but public URL support - not just the beta period - should be significantly closer to the former than the latter. 
1 Like
Well now. I’m glad I checked around about the public URL for apps built in the new builder. I was so excited, I forgot to check the URL in a test incognito, and luckily, a friend told me the link was going to Retool login. I think Retool should have made it crystal clear that if you built the app, no one would come until an “official” launch. I’ve been struggling for weeks in Classic trying to vibe code this app. Yes, I have put in a ticket also. I can’t wait…
I was just about to respond to you in a separate thread, @LBCooper! We know there is a ton of interest in being able to share what you've built and we'll be working hard on this particular feature. I'll add your notes to the internal tracking ticket and provide an update here as soon as I can.
I know you all meant well. But I have been through hell with Classic not allowing screenshots and now the new and improved app builder not allowing public links.
1 Like
I can certainly understand and appreciate the frustration. 
We'll let you know as soo as this goes live.
I’m having trouble with an app I had retool make and I wonder if this is the same issue as theis post topic. Here is the message i was told to past in the forum:
"My R2 public embed URL (/embedded/public/...) shows a blank screen. The browser console shows: 'Unsafe attempt to load URL from frame... Domains, protocols and ports must match'. The app is being served from retool-edge.com in a cross-origin iframe. The iframe URL contains parentOrigin= but the R2 runtime expects retool-parent-origin= and retool-iframe-hosted-mode=true. Without those params the app falls back to direct API calls which fail cross-origin."
Caveat: I’m not a developer or programmer, I’m just trying to get a simple utility for myself and coworkers.
Welcome to the community, @Nicholas_Martin! It does sound like you're running into the same limitation. Apps created via the new builder don't yet support sharing via public URLs, but it is on the roadmap and coming soon.
Out of curiosity, how did you generate an embed URL in the first place?
Your chat machine did it. I just watched. I’m trying to make a desktop list widget that syncs across multiple users in real time (everyone sees all the changes). I didn’t want all the users to have to get a Retool account to use the app which is what led to this.
Ah got it - despite the guardrails we've put in place, the app building agent does sometimes hallucinate. In this case, it made a wrong assumption and tried to generate a public URL in the same way we do for classic apps. Thanks for reporting in!