Last used space is not the space shown at application startup when there are multiple instances of Anytype

What’s The Bug?

Last used space supposed to be space shown when Anytype is started up, or after refreshes. However, this is not a consistent behaviour when there are multiple instances of Anytype.

Attempted reasons but couldn’t reproduce the exact behaviour:

  • It respects the switched space in first opened instance of Anytype
  • It respect the last switched/opened space in the last opened instance
  • It might be the last used space before last exiting Anytype
  • Mouse clicking to switch space vs keyboard shortcut switching space

Remarks: I previously reasoned this to be last switched space being the opened space at startup, but after several testing, I think this is also not the actual reason.

How To Reproduce It

  1. Have 3 or more spaces in Anytype
  2. Try switching spaces in one instance, then go to another instance and refresh. Repeat a few times on different instances.
  3. Sometimes last used/switched space is displayed; sometimes not.
  4. (Sometimes) After a few switching, the supposedly “last used space” is stuck with one Space.

Image or Video

In this video, around 0:22-0:47, last used space was working.. but before that and after that, it wasn’t.

The Expected Behavior

Last used space is shown at startup / refresh.

However, ideally, I prefer to be able to decide which space is supposed to be opened (just like homepage). So I could make a quick note in Space 2, but then continue to work majorly on Space 1.

Additional Context

This has been previously reported by @crystaln in a discussion post. Feel free to add any information.

I believe this issue is derived from the UI/UX that each instance of Anytype is independent to other instances

Device

MacBook Air M1

OS

Sequoia 15.1.1

Anytype Version

v.0.45.3

Network Mode

Irrelevant

Technical Information

OS version: darwin arm64 15.1.1
App version: 0.45.3
Build number: build on 2025-02-17 15:22:27 +0000 UTC at #f1ceda0a1457dbf982d8b3fd8479ccdcb95df6d3 (dirty)
Library version: v0.39.11

This report has been added to our issue tracker and received by the Development Team.

This issue has been fixed by the Development Team and will be implemented in an upcoming release.