Infinite error on new Finsweet Extension App

Extension
1

Hi team,

I was super excited to see the Finsweet extension back in Webflow app form.

However, when I run the app:

  1. I open the app
  2. I click the login with Finsweet button
  3. I get this error infinitely popping up until I close the app: “Uncaught ReferenceError: Cannot access ‘g’ before initialization”

I’ve been getting this behaviour for the last week or so since it launched, I’ve also tried reinstalling the app and have tried it on other sites and get the same behaviour.

Any ideas? Anyone else experiencing this?

Error in designer
Error in designer2812×2036 503 KB

Error in console
Error in console1042×510 41.1 KB

2

Hi @lucian

Have you tried incognito?

Just need to make sure the browser is not pulling corrupted cached bundles from earlier

Please confirm

3

Hi @jesse.muiruri thanks for the reply

I can confirm I get the same behaviour in an incognito window

Thanks

4

Thanks @lucian

The team is looking into it

Will keep you posted!

5

Hey @lucian

Could you please confirm your browser?

6

Hi @jesse.muiruri, sure thing, I’m using Chrome version 142.0.7444.60 on Windows 11

7

Hey @lucian,

Our devs have been looking into this

It seems like an isolated issue since others can login just fine

Could you please test on a different browser e.g. Brave, it’ll run the chrome ext just fine

I’ve personally got it working just fine on Chrome’s latest build (as at the time of this writing) 142.0.7444.176 (64-bit)

8

Strange… I still get the same behaviour on Brave.

Maybe related to the site I’m developing in the designer or possible my Webflow/Finsweet account?

Edit: I can confirm I get the same behaviour even on a new site with a fresh install of the Finsweet Webflow app

9

Wow this is one for the books for sure!

Just to confirm, when you install the finsweet web app to test, do you authorize it to the whole webflow or just one site

1 Like
10

Wow okay, I was adding it to a single site. I just added it to the entire workspace and now it works!

Is this expected behaviour?

11

Well, great news it now works!

And no, it should work even from one site

On the face of it, it could be said that the specific site you were installing on might have some code that’s potentially clashing with the app

While in the same breath it could be said that switching the configs on install could have been the much needed kick in the pants the app/browser yearned for to fetch the latest version

Have forwarded this to devs

Thanks