Hi all,
I am wondering if anyone else can’t open ...
# ask-questionsw
wooden-fountain-97161
07/21/2024, 7:04 PMHi all,
I am wondering if anyone else can’t open the Chrome Dev Tools plugin.
Running a NextJS App v14 App Router. Have tried both on Arc and Chrome.
Have added the api link and secret to the plugin settings. Also, the enableDevMode attribute is set to true. Not sure what I am doing wrong. I am not self-hosting GrowthBook. Any advice is greatly appreciated!
Getting the following error
> Unable to locate GrowthBook SDK instance. Please ensure you are using either the Javascript or React SDK, and Dev Mode is enabled.
f
fresh-football-47124
07/21/2024, 7:05 PM
Are you getting an error?
w
wooden-fountain-97161
07/21/2024, 7:05 PMJust edited the message to include the error.
wooden-fountain-97161
07/21/2024, 7:06 PMI have followed both the guide and reviewed the example repo on GitHub.
wooden-fountain-97161
07/21/2024, 7:27 PMQuick question? Does the plugin work with localhost or needs to be a prod url?
f
fresh-football-47124
07/22/2024, 2:48 AM
it works for either
w
wooden-fountain-97161
07/22/2024, 2:51 AMAny ideas on what else I can do to troubleshoot?
wooden-fountain-97161
07/22/2024, 2:51 AMI’ve been dealing with this issue since Friday.
f
fresh-football-47124
07/22/2024, 2:52 AM
is this public?
w
wooden-fountain-97161
07/22/2024, 2:53 AMIt’s not public but its not something super sensitive. I can init a new repo and copy over the relevant files if you’d like.
wooden-fountain-97161
07/22/2024, 2:55 AMGive me a few I will do that to see if it works in a newly inited app with the same setup but redacted.
f
fresh-football-47124
07/22/2024, 2:55 AM
I would make sure that devmode is enabled
fresh-football-47124
07/22/2024, 2:55 AM
and that growthbook init is called
fresh-football-47124
07/22/2024, 2:56 AM
you can share the implementation if you like, I can take a look - but if this was working, and then stopped, it might be something else
w
wooden-fountain-97161
07/22/2024, 2:56 AMIt never worked.
f
fresh-football-47124
07/22/2024, 2:56 AM
ah, well, that's easier
w
wooden-fountain-97161
07/22/2024, 2:56 AMScreenshot 2024-07-21 at 21.56.48.png
f
fresh-football-47124
07/22/2024, 2:57 AM
What does this look like in the rendered html?
fresh-football-47124
07/22/2024, 2:57 AM
oh wait
fresh-football-47124
07/22/2024, 2:57 AM
you're using this serverside
fresh-football-47124
07/22/2024, 2:58 AM
the devtools only works for client side
w
wooden-fountain-97161
07/22/2024, 2:59 AMNow thats something I couldn’t find anywhere in the docs or github 🙂
f
fresh-football-47124
07/22/2024, 2:59 AM
ah
w
wooden-fountain-97161
07/22/2024, 2:59 AMOkay cool so its not broken
f
fresh-football-47124
07/22/2024, 3:00 AM
yes, sorry about that
w
wooden-fountain-97161
07/22/2024, 3:01 AMSo In order to make it work, I need to follow the client or client-optimized examples found in GitHub?
wooden-fountain-97161
07/22/2024, 3:42 AMGot it working now! Thanks for all the help!
wooden-fountain-97161
07/22/2024, 3:43 AMRemoved the original screenshot because the keys were exposed!
f
fresh-football-47124
07/22/2024, 6:05 AM
👍
w
wooden-fountain-97161
07/23/2024, 2:02 PMOk so I got everything setup based on the examples, and have the chrome plugin working and its been helpful. I’ve noticed that when I manually enable a specific feature or experiment its starts re-rendering that component, and the dev tools keeps refreshing each second or so.
wooden-fountain-97161
07/23/2024, 2:02 PMNot sure what I am doing wrong, would like it to render only once. It has something to do with the useMemo and useEffect.
wooden-fountain-97161
07/23/2024, 2:05 PMThis is the page.tsx
wooden-fountain-97161
07/23/2024, 2:06 PMThis is the hero-wrapper.tsx
wooden-fountain-97161
07/23/2024, 2:06 PMThis is the hero.tsx
wooden-fountain-97161
07/23/2024, 2:08 PMThis is how the dev tools plugin is acting
wooden-fountain-97161
07/23/2024, 2:09 PM@fresh-football-47124 No rush on a response, but if you can give me some advice, would be awesome.
44 Views