Andy Wilson

@Haroenv It's always canRefine false, for all of the different attributes it can be. ``` algoliasearch.umd.js:1809 POST https://-dsn.algolia.net/1/indexes/*/queries?x-algolia-agent=Algolia%20for%20JavaScript%20(4.14.0)%3B%20Browser%3B%20instantsearch.js%20(4.43.1)%3B%20react%20(17.0.2)%3B%20react-instantsearch%20(6.30.2)%3B%20react-instantsearch-hooks%20(6.30.2)%3B%20JS%20Helper%20(3.10.0) net::ERR_NAME_NOT_RESOLVED eval @ algoliasearch.umd.js:1809 send @ algoliasearch.umd.js:1777 e @ algoliasearch.umd.js:500 eval @...

I thought that, but i have the appId, apiKey, and indexName all in the correct places if im correct. So the algoliaSearch function takes the appId and the apiKey and...

I will try manually putting them in rather than waiting for the api to pull it from our db

Yeah i get the same results. Are there any config differences i need to make to the algolia index to enable the hooks to work or should they work the...

ok ill have another look thanks for your help ill update the ticket with what i find.

Ok so something a little stranger is that useRefinementList works for the listable options with the exact same config yet useRange does not.

> This may be a bug because we need to add a check based on `results.__isArtificial` in `connectRange()`: https://github.com/algolia/instantsearch.js/blob/cf738b50d36c99c12995c79157920748094b4a7c/src/connectors/range/connectRange.ts#L428-L438 Im guessing its due this comment as I can't think of...

As if thats the only difference between the connectRange and useRange that would be my first point of call.

@Haroenv I have found one thing by changing branch and going back to connectRange the currentRefinement comes back as undefined, undefined for min and max. whereas the min and max...

something else i just noticed even though we can refine is connectRange, canRefine is still false but allows the refine function to work thus allowing the range to work.