Beets plugin doesn't appear in output of beet --version when attempting to update for breaking changes in 2.4.0

[Neurrone]

I'm attempting to update Beets-audible to be compatible with the breaking changes in 2.4.0.

However, after fixing the various issues, the plugin doesn't appear in the list of plugins:

> uv run beet -v --version
user configuration: /home/dickson/.config/beets/config.yaml
data directory: /home/dickson/.config/beets
plugin paths: ['/home/dickson/source/beets-audible']
Loading plugins: audible, edit, fromfilename, scrub
Sending event: pluginload
library database: /home/dickson/.config/beets/library.db
library directory: /home/dickson/audiobooks
Sending event: library_opened
beets version 2.4.0
Python version 3.12.4
plugins: edit, fromfilename, scrub
Sending event: cli_exit

It only appears in the "Loading plugins" line, but not in the second last line which shows the list of plugins it loads. This is confirmed by adding print statements in the __init__ method, which shows that it didn't execute when I attempt to import audiobooks using this plugin.

What am I missing?

If I update the plugin to deliberately cause a syntax error, it creates a stack trace as I expect, so I'm very sure that it is definitely seeing the file.

[Neurrone]

This was caused by not implementing the item_candidates function. The resulting exception probably got swallowed, which is confusing because there is no feedback at all about what went wrong.

Anyhow, managed to resolve it.