Incompatible with laravel/scout v10.11.6

[jayan-blutui]

• Laravel version: 11.31.0
• Algolia Scout Extended version: latest
• Algolia Client Version: 3.x (same as this extension)
• Language Version: 8.2

Description

The latest version of Laravel Scout v10.11.6 has the following error:

Class Algolia\ScoutExtended\Engines\AlgoliaEngine contains 2 abstract methods and must therefore be declared abstract or implement the remaining methods (Laravel\Scout\Engines\AlgoliaEngine::performSearch, Laravel\Scout\Engines\AlgoliaEngine::deleteIndex)

A possible fix for this issue is to use the new class called Algolia3Engine which was created in laravel/scout#872 instead of the AlgoliaEngine which is now an abstract class.

Steps To Reproduce

Update to latest version of Laravel Scout.

[CNSam]

Can confirm this issue too

[kaioken]

Same, can confirm this issue too

[jonathan-bird]

+1 on this issue, running same versions including v3.x of Algolia client

[ericlbarnes]

Came to report the same. 😅

[Eyad-Bereh]

Today I've just had the same issue with my Laravel application, the way I ended up solving the issue is by hardcoding the version of laravel/scout inside the composer.json file to 10.11.5:

"laravel/scout": "10.11.5"

[kaioken]

@Eyad-Bereh same here

[avdheshsolanki]

Yes, same here, please fix it.

[Eyad-Bereh]

I don't know what I'm missing here exactly, but converting an instantiatable class into an abstract class seems like a breaking change to me, and so it should've been done in a major release and not break the entire thing by releasing this breaking change in a minor version

[mariuscucuruz]

As suggested by Eyad-Bereh a quick fix is to downgrade Laravel Scout to v10.11.5.

#347 (comment)

composer update laravel/scout v10.11.5

I've submitted PR #348 to do just that.

[mattmcdonald-uk]

PR #348 is a useful workaround, but it doesn't fix this problem, so should the issue be closed ?

[el-klo]

PR #348 is a useful workaround, but it doesn't fix this problem, so should the issue be closed ?

The issue is fixed in #348. Updating through composer will fix the issue.

[mattmcdonald-uk]

PR #348 is a useful workaround, but it doesn't fix this problem, so should the issue be closed ?

The issue is fixed in #348. Updating through composer will fix the issue.

PR #348 just locks composer to an older version of laravel/scout which isn't a long-term solution.

[Eyad-Bereh]

PR #348 is a useful workaround, but it doesn't fix this problem, so should the issue be closed ?

The issue is fixed in #348. Updating through composer will fix the issue.

PR #348 just locks composer to an older version of laravel/scout which isn't a long-term solution.

It's definitely not a long-term solution, it's just a workaround until a permanent solution is implemented, but the current situation is somewhat severe and people are having their applications breaking down over this issue.

[DevinCodes]

The issue is not fixed long-term indeed, the PR was a temporary fix for now. Github automatically closed the issue when merging the PR I suppose, so I'm reopening it for now!

[mariuscucuruz]

So the issue is that algolia/scout-extended v3.1.0 is not compatible with Laravel Scout v10.11.6. This is a compatibility issue with Scout (versions 10.11.6 and newer). This particular issue is now considered fixed in #348 with a minor release, i.e. v3.1.1, by limiting what version of Scout it can use - call it dependency mitigation. By my definition, this issue should be closed.

Addendum
There might be plans for future major releases that will work with newer versions of Scout (they might even come with limitations of their own). But you'll need to wait for such a release (if you want it to work with newer versions of Scout), otherwise use v3.1.1.