Skip to content
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.

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

Website search is broken #2151

Open
1 task
andreyc0d3r opened this issue Apr 3, 2024 · 3 comments
Open
1 task

Website search is broken #2151

andreyc0d3r opened this issue Apr 3, 2024 · 3 comments

Comments

@andreyc0d3r
Copy link

What version of React, ReactDOM/React Native, Redux, and React Redux are you using?

  • React:
  • ReactDOM/React Native:
  • Redux:
  • React Redux:

What is the current behavior?

search doesnt work https://react-redux.js.org/

What is the expected behavior?

expected working search

Which browser and OS are affected by this issue?

chrome

Did this work in previous versions of React Redux?

  • Yes
@timdorr
Copy link
Member

timdorr commented Apr 3, 2024

I don't think I have access to the right Algolia projects, but we just need to set the app ID that was removed in this commit: 1bd4b25

cc: @markerikson

@markerikson
Copy link
Contributor

Yeah, the Algolia setup has been broken or weird for the last year or so.

We've got 2-3 different projects in Algolia. There was an old-style key for an old project and some kind of upgrade/migration step that didn't get done by their deadline. I thought I fixed it with a new key after talking to support, but maybe that didn't work right?

@kurenov
Copy link

kurenov commented Aug 27, 2024

Hey guys,

Looks like the appId is still required for the current setup. With the current config appId: ' ', requests fail because the appId is used in the URL generation https://{APPLICATION_ID}.algolia.net.

When I reverted the value for appId based on 1bd4b25, I no longer got the DNS error above. However, there is new 400 error:

{
  "message": "indexName is not valid",
  "status": 400
}

Based on this support article, this error occurs in two cases:

  1. indexName does not match the indexName issued in your DocSearch acceptance email
  2. incorrect API key is used

Then I tried to fetch all indecies via GET https://g15kg9hemq.algolia.net/1/indexes?x-algolia-api-key=2d058d216b7fd5d68d481fd48ee72c06&x-algolia-application-id=G15KG9HEMQ which resulted in 403 error below:

{"message":"Invalid Application-ID or API key","status":403}

Looks like the App ID & API key are no longer valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants