Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After upgrading from Scout 10.11.4 to 10.11.6 I started having issues with Algolia.
I believe the issue is due to bugs introduced in #872 which added support for Algolia v4, but also broke support for Algolia v3. #881 has also been opened as other people have run into the same issue.
When I first saw the error I thought it was because I still had Algolia v3, so I bumped straight to v4 and then got another error.
I've tested these fixes locally using both Algolia v3 and v4 and my search results are working again where previously they were not.
It appears the PR made mistakes:
config
helper was used,id
/secret
were provided as separate arguments,$config
(the Laravel configuration array) and$configuration
(the Algolia search config object)