I can’t enter some of my channels/spaces on my phone. I don’t know what is causing this, everything is synced on my Mac but I can’t access it on my phone.
How To Reproduce It
open the app
try to enter any of your spaces.
Image or Video
The Expected Behavior
To be able to access all my channels on my Android
Additional Context
It wasn’t the case a couple of weeks ago and I have no idea what is causing this. It started by me not being able to access my main private Space ( the first space I’ve created on Anytype) and now one by one I can’t access other too. I could see and use the “nightly space” for instance, now I can’t.
I even uninstalled and reinstalled it again but with no prevail. Like the video bellow, I even recieve the notifications from my spaces, but I can’t access or open them. The flashing screen after I tap on the notification remained like this and nothing changed. I forced close the app and opened it again.
Device
Huawei P30 Pro
OS
Android 10, EMUI 12
Anytype Version
0.42.15
Network Mode
AnySync
Technical Information
OS version: darwin arm64 26.1.0
App version: 0.51.42-alpha
Build number: build on 2025-12-05 14:11:19 +0000 UTC at #b8c0e16d02c524edaae63d17749cee4f2282bdd5
Library version: v0.46.0
Anytype Identity: A88ZQg1KjcrgvxBHMLu7G1RUSAqN3Ut8bSAf1GhcBmFgbDya
Analytics ID: 0ab193d4-c094-450d-bb76-c756c6c372eb
Device ID: 12D3KooWAkjsB9HrDRXx8yczSYmvoYzUo45KjmKLmGdLsWGgG5Pc
Ethereum Address: 0x8F846acAe46B84c4a75b606B74C6398A8542A3d9
Yes, I tried everything. Clearing the cache, the data and eventually uninstalling and reinstalling it. But I just can access many of my spaces and channels on my phone . It’s really annoying.
It used to happen a while back, probably around 6-7 months ago if I’m not mistaken but it got fixed. As it’s really hard for you guys to replicate, I know it won’t be easy to fix. But I’m willing to help the team in whatever capacity they require because as the app got more polished, I started using it more and more.
Hi, yes, the issue is clearly related to the state of spaces on the device. There is an option to collect debug logs, but to do that we need to release a new build. I’ll add this capability in the coming days, and then we’ll be able to capture the logs and check what’s going on.
Sorry, the release was slightly delayed due to the holidays. I’m planning to ship it later this week.Right now I’m trying to understand, based on possible errors, why Spaces are not opening. If I figure it out, we’ll try to resolve the issue remotely; if not, we’ll need to collect logs in the release.
Hi, I seem to be having the same issue. Except I can fix it by logging out and back in, which fixes it for a while. It usually comes back in under a week though.
I’m planning to release a beta version today (0.44.5-beta). It will include the ability to collect debug logs, so we can better understand what’s happening with spaces.
You’re already in the Closed testing – Nightly | Beta testers group, right?
If not, I can add you, and then you’ll receive the beta build.
For this, I’ll need your Google account email — please send it to me in a private message.
After installing, please run the Debug Stat command (
How to access Debug Screen
Open the Profile screen (tap your avatar on the Vault screen).
In MISC, tap the MISC section 5 times — a new Debug button will appear and persist after app restart.
Tap the Debug button to open the Debug screen).
Please send the generated log to us by email ([email protected] [please add “for Roman H” to Subject]) or directly to me via a private message on the forum.
We also need the Space ID of the affected Spaces — you can find it in the Space settings: tap the three dots in the top-right corner and select Space Information - Space ID.
Yes, I’m already in the closed testing - Nightly group and I’ve updated via the Play Store. I’ve sent you a message in the forum along with the Debug stat. Hope it helps!
according to user logs, they have spacestore db corrupted on their device. They can remove App Data and start the app again. So it will fetch from the network again. Make sure they have some space available.
@requilence@konstantiniiv Thanks for getting back to me. I’m happy to hear that the team is working on a more user-friendly situation for the future. However, I didn’t understand what I have to do here. By ‘App Data’, you are referring to any specific folder on my Android phone or my Mac, or are you referring to uninstall Anytype from my Mac completely, along with deleting all the folders related to it on my Mac and installing it again? Could you please clarify this a bit more?
I got the same Issue. Only the Spaces created in the app work and are able so be accessed on the desktop. I use Windows 11 and a Android Phone ( Samsung Galaxy S24FE). I tried the steps from Filip. Does not work, same issues.
Ok, I get it, just a simple clear data procedure. It was weird that uninstalling and reinstalling the app didn’t work but clearing the data did since they should do essentially the same thing!
But, after clearing the data and entering the app, it indeed worked. I could not only see all my channels, but also access them. But, there’s two issues.
Since my main space is absolutely huge, it takes forever to sync which is fine. What is not fine is that when I got to my main space and let it sync, it crashes my phone and the phone restarts itself. I’ve also reported this a while back in the nightly group of Slack I guess to @eugene about memory leak in Android.
Sometimes, after the restart, when I enter the Anytype again, it gets stuck on the splash screen and doesn’t get into my vault. To get it working again, I have to ‘clear data’ again.
Lastly, a couple of times, after the crash and restart, when I enter the Anytype, the same channels won’t get opened again through the vault. I have to clear the data again and do the whole procedure once more.
It normally wouldn’t be a problem but because of huge size of my main space, it crashes again and again. Basically while it’s syncing I can’t stay in the Anytype more than a couple of seconds before it crashes and force my phone into a restart.
There is one way to investigate the OOM issue on Android. But it’s not technically very simple . I wrote up a description of how to use GitHub - anyproto/any-sync-tools: Configuration builder for Any-Sync nodes , which was created by our middleware team. If we manage to do it, we should be able to make progress in understanding the issue on your huge account.