8000 Flag explorer stopped working · Issue #128 · vercel/flags · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Flag explorer stopped working #128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
dewinterjack opened this issue May 3, 2025 · 8 comments
Open

Flag explorer stopped working #128

dewinterjack opened this issue May 3, 2025 · 8 comments

Comments

@dewinterjack
Copy link

Hi,

The flag explorer in the vercel toolbar has stopped working for us. It just shows loading and I cannot see any errors in the browser console.

Image
I thought the issue would be fixed by upgrading to v4 but the issue still persists.

We are using edge config and I also tried moving us to the edge config adapter.
Any help would be appreciated.
@AAorris
Copy link
Contributor
AAorris commented May 3, 2025

Besides updating the package version there are some necessary steps to successfully upgrading — Have you checked the steps documented here? Guides: Upgrade to v4

Do you see any errors in the network tab?

@dewinterjack
Copy link
Author

I have followed the upgrade guide and am not seeing any errors in the network tab. The flags endpoint is responding with status 200. It looks like the flags are working it is just the overrides and the flags explorer which is not picking them up.

My flags file has a few exports like this:

export const isMaintenanceModeEnabled = flag({
  adapter: edgeConfigAdapter(),
  key: "maintenance-mode",
  description: "Flag for enabling maintenance mode",
  options: [
    { label: "Hide", value: false },
    { label: "Show", value: true },
  ],
});

I have tried without the edgeConfigAdapter and still nothing:

import { get } from "@vercel/edge-config";
export const isMaintenanceModeEnabled = flag({
  key: "maintenance-mode",
  async decide() {
    const value = await get(this.key);
    return value ?? false;
  },
  description: "Flag for enabling maintenance mode",
  options: [
    { label: "Hide", value: false },
    { label: "Show", value: true },
  ],
});

@AAorris
Copy link
Contributor
8000 AAorris commented May 6, 2025

Thanks for sharing, but I'll need some different info to best help you.

That info would be what your .well-known/vercel/flags route looks like, rather than the flag definitions. Send that over if you can 🙏

Additional details could be the response headers from the .well-known/vercel/flags network request. Should contain x-flags-sdk-version on successful requests after following the migration guide.

Besides that, you can try disabling the Vercel extension in your browser if you use it (See if there are any more details in the network tab)

Let me know what you find

@dewinterjack
Copy link
Author
dewinterjack commented May 7, 2025 •
edited
Loading

Ok so I have identified that it is an issue with my chrome. It is working for me in firefox and it is working for my teammate on chrome. I tried resetting the cache and everything in the application tab in the chrome dev tools. I do not use the chrome extension. I appreciate this may not be the correct place if the issue is not related to the flags package and is just a toolbar issue. The rest of the toolbar is working fine it is just the flags explorer that is constantly loading. If there is somewhere else I should submit this issue please let me know.

If it is still relavant here is the code for the route (however it seems this is not the issue as my teammate can load the flags correctly):

import { createFlagsDiscoveryEndpoint, getProviderData } from "flags/next";

import * as flags from "../../../../utils/feature-flag";

export const GET = createFlagsDiscoveryEndpoint(() => getProviderData(flags));

@AAorris
Copy link
Contributor
AAorris commented May 9, 2025

That looks great 👍

Last idea here for now — Does disabling all other chrome extensions help?

I'll circulate your experience internally and hopefully we can ship better feedback in the UI at a minimum, if not find and solve the problem. It must be very discomforting to see an endless loading state.

@dferber90
Copy link
Collaborator

@dewinterjack Could you try if using the Vercel Chrome extension resolves the problem for you? I have seen a similar case this week. This is not meant to be the permanent solution but will help us narrow down why this is happening for you.

@dewinterjack
Copy link
Author

Ok installing the chrome extension has fixed the issue I was experiencing.
Thanks.

@dferber90
Copy link
Collaborator

@dewinterjack could you try again without the chrome extension and see if it is working for you even then now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dferber90 @AAorris @dewinterjack
0