Error on Retool: Cannot destructure property 'basename' of 'i.useContext(...)' as it is null

💬 Self Hosted Retool
1

Hi Retool Support Team,

I'm experiencing an error when trying to access my Retool app. The page fails to load and shows the following message:

Something went wrong
Cannot destructure property 'basename' of 'i.useContext(...)' as it is null.

Here is a screenshot of the issue for reference:

image
image1250×650 14.7 KB

This issue is blocking usage of the application. I’ve already tried refreshing the page and clearing cache, but the problem persists.

Could you please take a look and advise on how to resolve this?

Best regards,
Inpyo Lee
inpyo.lee@datarize.ai

2

Hello @Inpyo_Lee Welcome to the community,

Clear cache and refresh the page and login once again it might be work.

3 Likes
3

Hello, thank you for your reply.

I’ve tried clearing the cache and refreshing the page, but unfortunately it’s still not working. Is there anything else I can try?

4

@Inpyo_Lee

Have you logout from the retool and once again refresh ?

2 Likes
5

Unfortunately, the issue occurs immediately after logging in, so I’m not able to log out manually.
However, I’ve already cleared the cache, cookies, and local storage, and the problem still persists.

6

@Inpyo_Lee

  • Inspect Retool Queries/Resources: Check if initial queries are failing or returning unexpected data, disrupting app load.
  • Review Initialization Logic: Examine Retool's app settings and any custom scripts for errors during startup.
  • Check Browser Console (Before Refresh): Look for JavaScript errors in the browser console before refreshing the Retool error page.
  • Simplify the App: Create a basic test app to isolate if a specific component or query is causing the issue.
  • Contact Retool Support: If the error persists, report it as a potential Retool platform issue.
3 Likes
7

CleanShot 2025-04-04 at 11.35.10
CleanShot 2025-04-04 at 11.35.10644×508 6.9 KB

Hey! This is happening to my companies instance too! Seems like this is a widespread problem! Can you please escalate this!

We have not done any recent upgrades and retool started giving this error today. We tried to upgrade to the latest stable but still we get this error.

Something else, not sure if its related to this. But I did notice my Team license was set to Free even though we just payed for an annual Team license in January 2025 (2-3 months ago) and should be good till January 2026. I'm not sure if this is related in some way, I bring it up because:

  1. I saw the self hosted billing page 500 Internal Server errors when I was checking it this Monday March 31st.
  2. And some of my employees who are still logged can only see an editor only view of the app.
1 Like
8

Same here. This morning we started to get this error, it is strange that somehow seems to be related to license expiration even though in our case it's up for renewal on July/2025.

So far we have tried restarting the app, restored from a previous version, cleared cached and still getting the same issue.

9

Sorry the license thing could be a red-herring, I'm not sure about it...

Retool On-prem Portal is showing the correct plan for me now, when it wasn't a couple of hours ago.

But even so, my instance is still broken (even clearing cache, logout/login, etc) Just wanted to include as much info as possible!

10

Hey all! Thanks for surfacing this issue - it does seem to be affecting a subset of self-hosted customers and may be tied to billing/licenses. We're digging into it now and will provide an update here as soon as we know more.

UPDATE:
We identified a misconfigured billing state as the likely cause of this particular issue and have rolled out a fix on our end. Please try logging in and let us know if you notice any aberrant behavior going forward.

Note that you may need to force a sync with our license key servers if you're seeing the same behavior. The most reliable way to do this is to restart the instance, but it can also be done via the Advanced Settings page.

4 Likes