Hey, I’m having problem loading the app after I published it successfully. The error message just kept saying Something went wrong, Refresh the page to try again.
I email support but there was no reply, is there anyone i can contact.
Also how can i download the entire code after i build the app in retool?
Thanks for reaching out, @Shu_Ting_Wen! Welcome to the community.
I see the breakage report that you submitted and it looks like the team is already digging into it. I'm sure Jay will follow up as soon as there is news to share, but I'll keep an eye on it as well. As for exporting your app, you can find the option here:
Thanks alot, loving the new app builder, I did not build previously on retool as it could not meet the design expectations i wanted, now its amazing. Also, I love how its an internal tool for just my organisation when i publish the app.
Glad to hear it! In this particular case, it looks like importing an app that references localStorage is probably the root cause. We make a small note of that limitation here, but it's theoretically only an issue when using a custom domain.
My recommendation is to prompt the app builder to replace any utilization of localStorage with a more durable storage solution like RetoolDB!
Hey @Shu_Ting_Wen - it sounds like you were able to resolve this. I'll mark the above as the "Solution" unless you want to share any additional insight into the steps that you took!
Hey Darren, I have the same issue and the dev console also points towards the localStorage issue. Is there any way to fix without prompting? I don’t have any credits available and have used my API budget already.
I assume you're also using a custom domain, @JaredStufft? The quick and dirty fix would be to disable that and republish the app.
As far as credits are concerned, though, I actually see an unused pack associated with your org that was purchased 7/28. Does that sound right? I can alternatively give you some credits to sort it out.
To your primary point, though, the only way to resolve this without prompting (or disabling custom domains) is to manually modify the underlying code. I can provide more guidance with that, but simply commenting out the offending lines would be a good validation of the root cause analysis.
Ah okay - I'm guessing that the system I was looking at logged the click, then.
How are you currently utilizing localStorage? Ultimately, the sandboxing we currently do for custom domains prevents the app from hitting any browser APIs, meaning the most direct replacement would probably be RetoolDB.
Have you previously expressed interest in the Retool CLI? I can probably get you access, as that would definitely be the cleanest way to get this done until we enable file creation via the UI.