Duplicated request when using with with react-instantsearch-nextjs

[gyto]

Describe the bug
Recently I have decided to migrate/upgrade from InstantSearch to InstantSearchNext to make sure route is consistent between user interaction. However, when I deployed a code I saw a huge spike in meilisearch api when it duplicate requests for 20-30 at once (looping) I am not sure if this is react-instantsearch or meilisearch, but I have tested a algolia api and it doesnt do anything that crazy. so I am assuming something is in react instantce of meilisearch that does loop the client. Switching back to the regular InstantSearch provider works fine (in some cases, but URL is not a friend on Next.js)

To Reproduce

"use client"

...
 <InstantSearchNext
  searchClient={searchClient}
  indexName="fancy_index:created_at:desc"
  routing={true}
  future={{
    preserveSharedStateOnUnmount: true,
  }}
>
 ...SearchBox...
...Hits...
</InstantSearchNext>
...

Screenshots

Meilisearch version:
@meilisearch/instant-meilisearch v0.17.0
react-instantsearch-nextjs v0.2.0
digital ocean version of MeiliSearch v1.4.0

[curquiza]

Hello @gyto

This bug is really weird. You have to know instant-meilisearch behaves the same with InstantSearch and InstantSearchNext, and does not adapt to the client.
Are you sure you use the same version of instant-meilisearch with InstantSearch and InstantSearchNext?

[gyto]

@curquiza react-instantsearch and react-instantsearch-nextjs using different versions but yes, they are the latest (just updated this morning to latest to see if the error still persists) however, now only on remote server of Meilisearch, not locally, that so strange. To note* it only happening to react-instantsearch-nextjs and not regular instance of react-instantsearch while using digital ocean instance of meilisearch.

react-instantsearch v7.7.2
react-instantsearch-nextjs v0.2.1

[curquiza]

however, now only on remote server of Meilisearch, not locally, that so strange

Waaa getting weirder

As a warning, looks like react-instantsearch-nextjs is still experimental: https://github.com/algolia/instantsearch/tree/master/packages/react-instantsearch-nextjs

I'm really sorry @gyto I don't know what to do more to help you 😞 This is the first time someone reports an issue like this.
If anyone in the community experiences the same thing, please, join us in this conversation ❤️

[gyto]

@curquiza yes I know that package is experimental, but I technically don't have a choice to use it, because nextjs routes and react-instantsearch cannot work together and I constantly lose the URL (unusable behavior). I can create a sandbox, but I think there no point of it because it happens on the production env and local env cannot be replicated. In addition, I can submit an issue with algolia, but I think this would make no sense because they will tell me that this is not their problem and use algolia instead.

is there any way to test @meilisearch/instant-meilisearch on your end guys? or give me a clue where to start look?

[curquiza]

@gyto
I'm not sure to understand why creating a sandbox does not help. It would definitely be helpful for our developers to investigate. I'm going to be honest, we don't have a lot of bandwidth to check this, especially a usage related to an experimental package, but if we have the sandbox, we could better understand your usage and the issue.
Or a repository to reproduce the bug.
Something to reproduce your use case.

[gyto]

@curquiza I will create a sandbox in couple days, just need filter the env to show up in sandbox