Sendbird UIKit React v2 (with NextJS) error: Command received no ack

AM_Youandx · July 8, 2022, 2:53pm

When attempting to execute this working example for UIKit React v2 with NextJS on my local machine, I encounter the following error every time, without fail:

SendBirdException: Command received no ack.

I am running Node v16.13.0 and NPM v8.2.0. The only way in which I alter the example when running it locally, is that I use NPM for installation and execution instead of Yarn.

My understanding is that it is related to some networking issue, but the local network is functioning perfectly, as far as I know.

Help would be greatly appreciated. Thank you in advance.

abdulrahim · July 17, 2022, 9:00am

Hey, I am also having the same issue here with Next.js and Sendbird UI Kit for React v2, any chance you figured how to solve this issue ?. Not only that also QueryInProgress Exception with scrolling through list of users to add. How can we at least handle the Exceptions so it won’t break the app ?

Sravan_S · July 18, 2022, 5:27am

Hello, I am sravan, I am a developer in React UIKit team, we are looking into this and update you as early as possible

abdulrahim · July 18, 2022, 4:54pm

Okay, good to know at least the team knows about it

rony · July 25, 2022, 1:37pm

Hi @Sravan_S do you have any update regarding SendBirdException: Command received no ack in NextJS?

Sravan_S · July 29, 2022, 5:02am

We are working on a fix, will try to include in a release today(uikit v3) for v2, probably next week

rony · July 29, 2022, 7:49am

@Sravan_S any reason why this is happening? I’ve tried the dynamic import but still it exists

Sravan_S · July 29, 2022, 8:50am

So, this ack error happens because, there are some exceptions(some of them are internal) thrown from SDK(mostly from flaky websocket connections), I have not seen these errors appear as a big popup in production builds, it should only appear on codesandbox and nextjs local version

For the ones that are not internal, they should be inside try..catch or next.then.catch. I have included those in the fix. But, I suspect there are a few ones that are internal which we cannot catch from uikit/application side. I even tried to add error boundary to catch them, but it didnt work well

So, I will release a release candidate for v3 today, need to test that for a day or and see if the internal errors occur. If the internal errors occur often, we will have to clean it from SDK side

rony · August 1, 2022, 2:42pm

@Sravan_S thank you for your kind answer. let us know if the changes are deployed on V2.~
Thanks!

Sravan_S · August 2, 2022, 7:01am

So, update, we found the root cause for this in SDK. Its a large work, will update here when it is fixed on SDK side

Sravan_S · August 2, 2022, 12:40pm

This is because of StrictMode in React 18, it will not affect your production build, but we will include a fix in 3.0.2

github.com/facebook/react

Bug: useEffect runs twice on component mount (StrictMode, NODE_ENV=development)

opened 03:38PM - 05 May 22 UTC

closed 04:11PM - 05 May 22 UTC

cytrowski

Status: Unconfirmed Resolution: Expected Behavior

React version: 18.0.x, 18.1.x, 18.2.x ## Steps To Reproduce 1. Visit provi…ded sandbox 2. Open console and observe logs displayed twice. 3. Click the button and observe the rendering log happens twice, the effect log happens once. Link to code example: https://codesandbox.io/s/react-18-use-effect-bug-iqn1fx ## The current behavior The useEffect callback runs twice for initial render, probably because the component renders twice. After state change the component renders twice but the effect runs once. ## The expected behavior I should not see different number of renders in dev and prod modes. ## Extras The code to reproduce: ```jsx import { useEffect, useReducer } from "react"; import "./styles.css"; export default function App() { const [enabled, toggle] = useReducer((x) => !x, false); useEffect(() => { console.log( "You will see this log twice for dev mode, once after state change - double effect call" ); }, [enabled]); console.log("You will see this log twice for dev mode - double rendering"); return ( <div className="App"> <h1>Hello CodeSandbox</h1> <h2>Start editing to see some magic happen!</h2> <button onClick={() => toggle()}> Toggle me: {enabled ? "on" : "off"} </button> </div> ); } ```

minhdat97 · August 15, 2022, 9:33am

Hi Sravan,
I using @sendbird/uikit-react version 3.1.0, but still showing error message like that

My project enviroments following:

React: ^17.0.2,
@sendbird/uikit-react: ^3.1.0

Sravan_S · August 22, 2022, 12:48am

This one, is a packet loss exception leak. It wont break your app in production(the overlay for this error receive is only for dev. builds in nextjs and CRA)
We are working with chat SDK to fix it, I will mention here once we have a solution

hskim · August 25, 2022, 5:02am

Hi Sravan,
I also using @sendbird-uikit / React Uikit V2 with Next.js, and I still encounter below error message:

I am running my project with below enviroments:

Node v16.13.0
React 17.0.2
Next 12.1.0
Yarn 1.22.17

Could you let me know when this error sort out?

Sravan_S · August 25, 2022, 5:31am

Yes, I will reply when it is sorted out. Its the same issue

abdulrahim · October 8, 2022, 9:22am

It’s been 3-4 months now, still no fix

emora · May 5, 2023, 8:54pm

Any update? @Sravan_S ? Getting this error and i’d like to figure out why

Sendbird UIKit React v2 (with NextJS) error: Command received no ack

Not finding what you need