Setting set_intercept_activation() on a JS CategorisedResult causes scope to claim `returned nullptr from activate` and not activate

[Stuart Langridge]

To test, add CategorisedResult()s in search() as normal, but call cr.set_intercept_activation() on that CategorisedResult. This should call the `activate()` function from the scope.initialize runtime_config. However, it instead throws errors:

Scope (your scope) returned nullptr from activate()
Scope (your scope) threw an exception from activate()

As far as I can tell, this is not being thrown by my code; it happens regardless of what I have in the activate() function, or even if I don't have one at all, and no code inside my activate() function is executed. This, in practice, means it's impossible to write a JS scope which allows tapping on a result item to do anything other than show the preview (for example, launching an app).

[Marcus Tomlinson (marcustomlinson)]

@alex: The documentation doesn’t actually mention ActivationResponse or even that activate() handlers are possible in scope.initialize(). We should fix this too.

[Alexandre Abreu (abreu-alexandre)]

@Stuart: I could repro your issue, could you check if the branch linked works for you (so that at least we have a simple common example)?