Pod

Available as Markdown and JSON. Pod is also available over MCP.

Reported issues for mcp by Buoy-gg

Pod holds 17 of 19 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to mcp by Buoy-gg.

Most discussed

Cant install query-client correctly

I'm getting the following issue when starting my app:

Image

I deleted all my node_modules and created a new prebuild. I manually installed @react-buoy/shared-ui.

Using expo 52 with old architecture.

Can sombody help me?

Greetings, Max

Read the thread · 2025-10-23 · closed · external user · 20 comments

Expo 53 & React native 0.79.1 Render Error

Pressing the Bubble (floating action button) crashes the app with the following red-screen error:

No QueryClient set, use QueryClientProvider to set one

Read the thread · 2025-04-25 · closed · external user · 16 comments

is this work at bare react-native

Hi i want to know that is this tool will work react native cli project, because i have tried it and showing error related expo-clipboard , because our app is in react native cli

Read the thread · 2025-11-26 · closed · external user · 15 comments

The "to" argument must be of type string. Received undefined

I am trying to use this in an Expo app. Here's my top level _layout:

<SafeAreaProvider>
      <GestureHandlerRootView style={{ flex: 1 }}>
        <NetworkErrorBoundary>
          <QueryClientProvider client={queryClient}>
            <PushNotificationProvider>
              <ThemeProvider value={DARK_THEME}>
                <StatusBar style="light" />
                <Stack
                  screenOptions={{
                    headerShown: false,
                    gestureDirection:…

[Read the thread](https://github.com/Buoy-gg/buoy/issues/47) · 2025-10-25 · closed · external user · 11 comments

### Response Body is empty

When opening a network log, all response bodies are empty.

<img width="300" height="930" alt="Image" src="https://github.com/user-attachments/assets/be1a10b9-c164-4db4-aad7-e85675a54a56" />

When copying the full request, it shows this weird `blob response`.

Response Data

json "[blob response]" 


[Read the thread](https://github.com/Buoy-gg/buoy/issues/57) · 2025-11-09 · closed · external user · 8 comments

### Installs fine, but does not show any tools

I have an Expo SDK 54 app, with expo-router and custom dev builds. I followed your setup instructions on README, got not errors whatsoever, but I get no tools to show up. Seems like auto detection is broken? I am not really sure how to debug this.

<img width="300" alt="Image" src="https://github.com/user-attachments/assets/9058e5e6-735b-42b3-a9d4-cc2657edd260" />

I've tried to do manual `apps` prop like mentioned in README, but no success:

```ts
import {FloatingDevTools as…

[Read the thread](https://github.com/Buoy-gg/buoy/issues/61) · 2025-11-11 · closed · external user · 7 comments

### [Feature Request]: Ability to open RQ DevTools without needing the bubble

Hi! 
Thanks a lot for creating this library.

I've a small feature request, it'd be great if the package provided some API to trigger opening and closing of the devtool without needing the bubble. We maintain a floating toolbar in our app of our internal devtools and could definitely use such API to include RQ in that

Cheers

[Read the thread](https://github.com/Buoy-gg/buoy/issues/29) · 2025-06-08 · closed · external user · 7 comments

### Allow not to pull `expo` in ejected RN projects

Thanks to https://github.com/LovesWorking/react-native-react-query-devtools/issues/7 last RN can install `react-native-react-query-devtools` without a problem.
Though if 1.3.0 is installed in ejected RN project it adds `expo` as a dependency when it's not needed.
`react-native-react-query-devtools` uses expo only for `Clipboard` functionality. 
I'd like to ask what is the opinion of authors:
- it's ok that `expo` is added, just ignore it.
- may be another Clipboard library can be used,…

[Read the thread](https://github.com/Buoy-gg/buoy/issues/13) · 2024-07-26 · closed · external user · 7 comments

## Most recent

### FloatingDevTools does not connect to MCP broker in release builds (externalSync is dev-gated)

## Problem

`FloatingDevTools` from `@buoy-gg/core` (tested with v7.0.22) hard-gates the `<AutoExternalSync>` component behind `__DEV__`:

```js
// FloatingDevTools.js (line in render)
const isDevelopment = typeof __DEV__ !== "undefined" && __DEV__;
// ...
isDevelopment && externalSync !== false && isExternalSyncAvailable() && <AutoExternalSync ... />

This means that in release / production builds (__DEV__ === false), the socket connection to the Buoy Desktop broker (port 42831) is…

Read the thread · 2026-08-19 · open · external user · 2 comments

Network calls to grpc-web

I am not using standard HTTP API calls for data fetching, instead I use gRPC-Web, with ConnectRPC as the mechanism. It still uses expo/fetch function to hit the API, all on top of react-query. Here's an example of calling an RPC without useQuery:

// createGrpcClient.ts
import {DescService} from '@bufbuild/protobuf';
import {createClient} from '@connectrpc/connect';
import {createGrpcWebTransport} from '@connectrpc/connect-web';
import…

[Read the thread](https://github.com/Buoy-gg/buoy/issues/62) · 2025-11-11 · closed · external user · 3 comments

### Show graphql operation name instead of endpoint path

In a GQL app, all network calls are `/api/graphql` so the network tool is less useful (e.g. you have to open the request body to see what query/mutation is called)

<img width="300" height="1167" alt="Image" src="https://github.com/user-attachments/assets/ef7b4c5a-8edd-47f8-9139-8b5ffa19b787" />

<img width="300" height="1167" alt="Image" src="https://github.com/user-attachments/assets/3de30943-2353-4369-8064-0179d66891fa" />

Ideally it shows the operation (i.e. query or mutation) name (e.g.…

[Read the thread](https://github.com/Buoy-gg/buoy/issues/56) · 2025-11-07 · closed · external user · 6 comments

### copybutton can not work in expo projects.

source code is at : packages/shared/src/utils/loadOptionalModule.ts

added some code to debug:
`
const dynamicImportLoader = (() => {
  try {
    return new Function("moduleName", "return import(moduleName);");
  } catch (error) {
    console.error("🚀 ~ dynamicImportLoader ~ error:", error)
    return null;
  }
})();`

output:
 ERROR  🚀 ~ dynamicImportLoader ~ error: [SyntaxError: 1:31:Invalid expression encountered]

[Read the thread](https://github.com/Buoy-gg/buoy/issues/41) · 2025-10-21 · closed · external user · 3 comments

### [Feature Request] Changing position of inspectors

Hi! I'm a big fan of this library. Thank you always for maintaining such a great library.

What I feel pain now is, I cannot touch any bottom tab button while opening network inspectors. I hope there's position switching feature for bottom sheet only inspectors.

or is there anything that I'm missing?

[Read the thread](https://github.com/Buoy-gg/buoy/issues/39) · 2025-10-16 · closed · external user · 4 comments

### Network inspector pending forever when using axios

## 🐞 Issue Description

The Network Inspector stays in a pending state indefinitely and never completes — even after the request has already succeeded or failed. This issue only occurs when fetching data with Axios, while requests made using Node’s native fetch API work as expected.

---

## ✅ Steps to Reproduce

1. Clone the repo and install dependencies  
2. Follow the README setup instructions  
3. Make a network request using `axios`  
4. Open the **Network inspector**  

**Observed…

[Read the thread](https://github.com/Buoy-gg/buoy/issues/36) · 2025-10-01 · closed · outside contributor · 4 comments

### DevTools icon visible but does not open after upgrade; persists even after downgrade

#### Description
After upgrading to the latest version of `react-native-react-query-devtools`, the DevTools icon (bubble) appears on the screen as expected, but clicking or tapping it does not open the DevTools panel. The app doesn't crash, but there's no response—no modal, no error logs in the console, and no visible changes.  

This issue started immediately after the upgrade. Even after downgrading to a previous version, the problem persists.

**To Reproduce**  
Steps to reproduce the…

[Read the thread](https://github.com/Buoy-gg/buoy/issues/30) · 2025-07-30 · closed · external user · 3 comments

### Dev tools showing in production

I was expecting behaviour to be same as the official dev tools, but the tools are not being automatically excluded from production builds.

[Read the thread](https://github.com/Buoy-gg/buoy/issues/26) · 2025-04-19 · closed · external user · 4 comments

### Dev Tools shows [object Object] for query keys

Hi there! Thanks so much for building this package. It is very helpful. However I've run into an issue with it when using query keys that have objects in them. This is the way react-query recommends building query keys (e.g. ['book', { userId: 'xxxx' }]), but when I use keys like that in my app, they show as ["book, [object Object]"] in the dev tools. I think there is an issue in the `displayValue` function, or wherever that query key is gotten from the QueryClient and put in state. I took a…

[Read the thread](https://github.com/Buoy-gg/buoy/issues/15) · 2024-11-16 · closed · external user · 5 comments

The remaining reports are on [the project's issue tracker](https://github.com/Buoy-gg/buoy/issues).