anytype:// Invite Link always reports key parameter missing

Have you read a contributing guide?

• I have read CONTRIBUTING.md
• I have searched the existing issues and didn't find any that were similar
• I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

With the latest 0.2.0 release I am unable to join any spaces using the anytype:// format invitation link.

I was previously able to join a number of spaces and can list them via the API against anytype-cli, but that was quite a while ago. The API request still works today.

I am using this command:

docker exec anytype-headless anytype space join anytype://invite/?cid=...&key=...

And seeing this output:

✗ Invalid invite link: invite link missing key parameter

I have tried to use the https format link and that appears to work:

Joining space ... created by Owen...
✓ Successfully sent join request to space '...'

But I never receive the join request in the desktop app.

I am using a self hosted server.

I'm pretty sure the problem with the https format link is some kind of configuration issue with the cli client, but given the much simpler code that is responsible for parsing the anytype:// format urls I'm not sure what could be going on there.

I receive this error for spaces I have already successfully joined using anytype-cli.

Expected Behavior

I should be able to join the space identified by the invite link.

Steps To Reproduce

1. In Windows anytype 0.54.11 generate an invite link (should use the anytype:// format by default).
2. Attempt to join anytype-cli to that space using the required ocmmand.

Environment

- OS: Windows 11 Pro
- Version: 10.0.26200 Build 26200

Anything else?

Thanks for receiving my issue. I know Self hosted issues can be difficult and there definitely could be configuration issues at play. Here's what I know about my setup:

• I can successfully sync data to and from multiple machines for multiple spaces using my self hosted sync node.
• I can use the anytype-cli API to list the spaces it has joined.
• My desktop anytype instances tell me they can successfully sync with my self hosted sync node.
• I am using the same config yaml in both desktop and anytype-cli.
• The anytype-cli logs are less than helpful and are full of errors that are apparently expected in a self hosted environment.
• anytype-cli is currently joined to three other spaces in addition to the one created by it by default.
• my-bot is appearing as a member of the spaces it is joined to on other machines.

Start at cmd/space/join/join.go around lines 135-137 and reproduce the reported command with an anytype:// invitation link. Trace how the link's query parameters are parsed, then verify the command accepts a valid link containing cid and key and successfully sends the join request.