Default object type keeps changing to page

What’s The Bug?

As title says.

How To Reproduce It

Open object
See that it’s a page and not a note

The Expected Behavior

I would expect my object type to be note

Device

MacBook Pro 13-inch, M1, 2020

OS

Sequoia 15.1.1

Anytype Version

0.43.34-beta

Network Mode

AnySync

Technical Information

OS version: darwin arm64 15.1.1
App version: 0.43.34-beta
Build number: build on 2024-12-11 19:46:40 +0000 UTC at #555d2665f9c65012234f54d09741be51b74b94a5 (dirty)
Library version: v0.38.4
Anytype Identity: A7JGAn8YT1NKSJaNSMMzsKCyxZvE6JW33nsax4z9VkndkrRC
Analytics ID: ae233490-9c4e-4e20-a986-0cc255483c70
Device ID: 12D3KooWBn9BjxvdRoGeiwHNCr6vzy1cN1RutDUrfficrAdazfp1

I can’t reproduce this in the same version. Where exactly are you creating the objects from, and where exactly did you set the default type in?

I believe this is an ongoing bug. Every time I change or update the version of Anytype on MacOS, it reverts my default object type setting at space, from custom object type back to Page Type.

I thought this was never resolved and so I didn’t report/update. (The current behaviour is not Note Type but Page Type though)

P.S. This is one of the reason why I have reduced my testing on pre-release. I don’t want to keep changing my default object type.

Created them by clicking the plus button and by clicking command+n. Default type I set is note, but it keeps producing pages instead, and I have to keep going back and manually changing it. I think I’ve done it three times now?

Also, while I have you here, please do address this: Content wrap in Sets. Thanks a ton, Filip!

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.

Hi. I now also have this problem with the newest version 0.44.20-beta (the beta one before this had this too). Every time I open or reload Anytype the Object Type default will always revert back to Page, which is quite annoying.
EDIT: Still there in 0.44.21-beta

Like what @Kadisra reported, this is an increasing problem in v.0.45.0. With every reloading of Anytype, and sometimes space switching and Raycast extension usage, default object type is reverted to Page.

Found the problem with initialisation and fixed

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

Oh good. I just came to report this.

Do you have an ETA when it will be in a new release? Its still not in 0.45.3 and its really annoying.

One/two weeks, alpha and beta builds will be earlier. The problem is in the space switching mechanism which initialises selected type incorrectly. Using cmd + r to reload page after switching space should fix this bug as a temporary solution.

Ok. Thanks for the Info, but no, reloading does not fix it. Even when using Ctrl+R (I’m on Windows) the default object type is always reverting back to Page even if in the same space.

I see, we will try to make new pre-release version faster but we have some technical stuff to test right now.

It’s not just about switching spaces—even if I stay in the same space, changing the default object type from Page to other types doesn’t work at all with just Cmd + R. This is actually annoying as I am practising zettelkasten method - I would definitely not like to create every note as a “page” when I already have a self-defined type for that. Hope AnyTeam will fix it in the coming versions.

This is still an issue

In which version?

I’m seeing this issue in 0.45.3.

At the moment, my workaround is to manually change the default type from Page each time I start my computer in the morning.

Yep, still happening here for me also 45.3.
Very annoying.