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

Self Hosted Retool
1

Hello there,

We upgraded self-hosted retool to 3.64-edge last week and everything was just fine, but today we started to get the error right after the login page submitted:
image

As I can see in most cases the solution is to upgrade to newer version, but in this case our version is the latest one already.

We rebuilt the docker containers, but this came up empty.

Anything we can do to fix that?

Any help will be much appreciated.

Thank you.

1 Like
2

We also tried to downgrade to 3.52.6-stable but that didn't help.

3

It appeared, the issue happened right after we invited additional member to Retool, I logged in the database directly and deleted the invite: DELETE FROM public.user_invites WHERE id=xx;

After that the issue was resolved. I can replicate it on my end. Is this something what should happen? Is there a way to avoid that?

4

Hi @Dima_Borodin,

Thanks for reporting these details! It looks like a Retool bug :disappointed: I'll reach out when I get an update internally

5

Bumping this. Exact same situation as @Dima_Borodin except deleting the invite does not fix it for me. Was on 3.52.0-stable, ran into the error, upgraded to 3.62 edge and then to 3.52.7-stable. Still have issues.

6

Thanks, @Kenorn,

Our team is looking into it!

7

Hi @Kenorn and @Dima_Borodin Are you still experiencing this error?

If so, would is possible for you to send us a screen recording of this error, including the URL browser bar in the recording? Additionally, would you be able to send us a HAR file of the behavior?

To generate a .har file, we just need you to:

  1. Open the network tab of devtools
  2. Ensure you are recording the network requests
  3. Refresh the page
  4. then export the .harfile

Thanks!

8

Hi @Tess it started working around 1 week ago. Not sure why?

Thanks!

9

@Tess , it seems the root of the issue was in user limit of the self-hosted version.