Bubble Changed Home URL Variable - it broke some things

Need help
1

Just a FYI as I had to deal with it. Bubble updated how they show the Home URL variable. Before 1st June it showed like - xxxxxxx (dot) com now it shows as xxxxxxxxx (dot) com /

You may think this is a small thing but I was referencing that in some schedule API requests from the frontend to the backend and it broke some login / signup flows as I was referencing this in the API Connector to determine between my live and test versions of the app and due to the now double // it errored out. I woke up to multiple supports regarding users unable to login / register during the time when it changed.

I have now gone and made the change but why isn’t stuff like this communicated when it happens? It is kinda annoying that there isn’t a changelog / announcement when things like this happen.

2

This was reported here: Tip - a few days ago backend API URL behaviour changed

Yes, you’d be right in being frustrated this breaking change was pushed without notice.

On this, you’re much better off using ‘app version’. Always, always set the API Connector URL to yourapp.bubbleapps.io/version-[version]/api/1.1/wf/blablabla.

That means that:

  1. Even if you change your domain, the calls still work
  2. You just use ‘app version’ as a parameter in the API call and it will always work.
1 Like
3

Also, does this refer to ‘Website home URL’ used as a datasource? If so, it’s always been app.com/ for me, and I’ve verified this on an existing app which has custom logs for this operator - no change over the last two weeks.

4

Yes it is using the Website Home URL, we had it in a check user flow with [homeurl] as first part of the URL we put in API connector to run a backend workflow for something with magic links.

It was working for months until a few days ago so yes, super frustrating. Everyone was getting 404 errors and that was caused by the // so it definitely changed behavior on what we have running.

5

This is a nice tip. Thanks

6

Yeah so I think it’s not the Website home URL variable that changed. You were always making API calls to app.com//api, it’s just that Bubble allowed it. Now, it doesn’t work. Still a breaking change of course.

1 Like
7

OH FFS!!!

This is BEYOND frustrating!

My bad because I know that ‘website home URL’ inserts a / but on some particular calls I had the / at the start of the path behind the root URL. BUT it should have just not worked from the start and then it would never have been let through to the keeper :upside_down_face:

On this, you’re much better off using ‘app version’. Always, always set the API Connector URL to yourapp.bubbleapps.io/version-[version]/api/1.1/wf/blablabla.

That means that:

  1. Even if you change your domain, the calls still work
  2. You just use ‘app version’ as a parameter in the API call and it will always work.

What does that matter? Shouldn’t the ‘website home URL’ change dynamically if your domain is changed?

I just use something like ‘root URL’ param if I need it and feed in the ‘website home URL’ in front of any paths etc.

8

Yes, but just using a simple version-[version] will make you far less likely to run into issues like these :wink:

9

This topic was automatically closed after 70 days. New replies are no longer allowed.