Once you close Anytype app and reopen it later, you can't open the app

Tamalika · March 19, 2024, 4:26pm

I had the sane issue. On windows 11 as well. I have the Anytype app pinned to the taskbar. If I close the app, Then click the app icon in the task bar to open the app again, nothing happens. I found, Like is mentioned here in the comments, if I go to the icon tray in the task bar, I can see that Anytype is running in the background. Then I can open the app again from the “hidden app” tray.

I think this is related to other bug reports and feature requests. e.g,

https://community.anytype.io/t/option-to-quit-anytype-when-pressing-the-close-x-button/8053

I was just about make the seme bug report.

Good-day.

Hexara · March 20, 2024, 12:45am

Idk if this is related, if I double click the the app icon to run it the first time, it runs normally but if I double double click (4 clicks or 2x starting the app), the app won’t run at all, not even in the tray icons and I have to end it from the task manager to be able to run it again.

sturdily · March 27, 2024, 11:50am

In my case, I can run it again if I right click on the system tray and choose “open Anytype”.

But closing Anytype with “Ctrl+Q”, allows Anytype to always start (because it exits everything, frontend and server)

mitumial · December 6, 2023, 5:48pm

I can’t open Anytype on my desktop. Works fine on cellphone.

HOW TO REPRODUCE IT

Open Anytype
See an error and generated crash log file

ADDITIONAL CONTEXT
crash_2023-12-06T17_30_07.log (2.2 KB)

SYSTEM INFORMATION

OS:
Windows 10 Home 64-bit
Anytype Version:
v.0.36.0

micklat · April 5, 2024, 7:34am

What’s The Bug?

when I close anytype main’s window (but it’s still in the tray), and try to re-start the app by executing the AppImage, it fails to open a window.

How To Reproduce It

open anytype using the AppImage
close anytype main window (but don’t click quit from the tray icon)
try to run the AppImage again

The Expected Behavior

The main app window should open.

Additional Context

output to shell:

10:33:18.664 › [Api].exit, relaunch: false
[Api].exit, relaunch: false
10:33:18.667 › [Api].shutdown, relaunch: false
[Api].shutdown, relaunch: false

The log directory contains only 0-byte files.

Device

linux desktop (Manjaro)

OS

manjaro linux 23.1.4

Anytype Version

0.39.0

Technical Information

OS version: linux x64 6.6.19-1-MANJARO
App version: 0.39.0
Build number: build on 2024-03-05 15:37:42 +0000 UTC at #a7986fffadcc2031b1eb3372265db5dda05f4c6d
Library version: v0.32.1
Anytype Identity: A6Pz8ZcuTra8sAEXZuTCkLxXnSQhHYmGDDQrN9W8VywtKbWf
Analytics ID: caf948e4-1140-4287-8d4e-7363d22bca05
Device ID: 12D3KooWFrp8AAZSwu6aVpeSpjj5wKcsMPK9Mhu3JYhJ4gt6Jak5

Angelo · May 15, 2024, 1:47pm

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

Code-Jack · May 29, 2024, 9:23am

The issue is still there in v0.40.27-beta

After closing the program, this is what my taskmanager shows:

Only after shooting the processes it becomes possible to start Anytype again.

Filip · May 29, 2024, 9:33am

Can you please share your technical details? I’m guessing you’re on Windows?
How are you trying to re-open the app? Does Anytype still show up in the system tray, and can you re-open it from there?

Code-Jack · May 29, 2024, 9:43am

As always:

OS version: win32 x64 10.0.19045
App version: 0.40.27-beta
Build number: build on 2024-05-28 10:47:41 +0000 UTC at #df0b26ef822cfff617560fc48d829a59c37f0335 (dirty)
Library version: v0.34.0-rc5
Anytype Identity: AAtt6aReARByswg2CbvZhveoJEEcnydfDu7U2VAkgJALsE7D
Analytics ID: 8a514008-4f5d-40d3-970f-a0d241b63af2
Device ID: 12D3KooWGqd6JSafCCcEwvnke5JAVgBNnuR9gGQeSBQ5HdUboWtG

And yes, after closing the program it is still shown in the system tray.
And no, I can’t restart it from there.
Normally I start it with a double click on the icon on my windows desktop.

In my opinion it is simply so that Anytype uses some parallel threads, but ending Anytype doesn’t terminate them properly before it ends itself.
I know the nasty problem from one of my own Python programs (there I was able to solve it, after a while) but I can’t say anything about the language “C”.

In Python there are different ways to “end” or “close” or “kill” or “terminate” a thread. But there is only one way to do it properly.
I suppose we have the same issue here.
The programmers don’t use the correct way, or not the correct command.

In Python was the point to start Threads as “Daemon”. This makes it possible to kill it together with the main program.
But this way also has it’s downsides. It is not recommended for threads that write on filesystem or so. Because killing while writing data → problem!
One needs to set the thread in a save sate before killing, by self.is_running = False
This stops the thread in a safe way. But it is still there, until you close the main program.

Fazit (for Python):
– Start a thread as “Daemon”
– For ending: First set it into a safe state (self.is_running = False).
– Then kill the main program. The already stopped thread will die together with it.

Filip · May 29, 2024, 10:01am

@Bug_Detectives Does anyone else uses Win? Can you please try checking if this has been fixed for you?

Shampra · May 29, 2024, 11:09am

I confirm the problem with older version (which I should have confirmed beforehand, but…).
With the latest version (0.40.27-beta) on test since this morning, so far I haven’t had the problem.

Hexara · May 29, 2024, 2:11pm

Same here, reproducible on 0.40.8 but not on latest beta.

archerallstars · June 1, 2024, 3:44pm

What’s The Bug?

The app refuses to reopen its UI from the icon after closing to system tray. The only way to reopen the already running app is from the system tray menu to which is counterintuitive.

Moreover, GNOME by default, without the system tray extension, doesn’t have system tray implemented. Therefore, the only way to reopen the app is to manually kill the app then launch it again.

The issue is shown in the screen recoding.

How To Reproduce It

Open the app.
Close it. The app will be closed to system tray.
Reopen the app from the app’s icon. The app won’t reopen.

Image or Video

The Expected Behavior

After closing the app to system tray, the app can be reopened from the app’s icon.

Additional Context

The same issue was reported on macOS (already closed):

Device

Laptop

OS

openSUSE Tumbleweed

Anytype Version

0.40.9

Network Mode

AnySync

Technical Information

OS version: linux x64 6.9.1-1-default
App version: 0.40.9
Build number: build on 2024-05-22 13:45:39 +0000 UTC at #75374629f026904f01d57b422abf0c350488d584
Library version: v0.33.6
Anytype Identity: A7vbqLZXMneoS25NXW6SEcX45sSCU36AG4UDBUSZHz816gLW
Analytics ID: 9ee5e932-09e9-4059-a9cc-7c73b960d4ae
Device ID: 12D3KooWJgbmMWrHF9ryzAPayXxkApFAu4xSqqLE2fDQuD7bWFkU

parishka · June 2, 2024, 4:15pm

I have the same problem at the moment, ever since the most recent update. Not sure if the team is aware.

archerallstars · June 10, 2024, 4:59pm

This is fixed for me in v0.41, AppImage Linux.

HeLLoWeRLD · July 9, 2024, 8:39am

I’m having a similar issue. Can’t open the app, says it can’t sink. 0.41.1

requilence · July 9, 2024, 1:28pm

@HeLLoWeRLD This is a db corruption. Some of them are not automatically recovered. In the next months we are going to replace the DB with the more reliable. In the meantime you can use this instruction to fix the issue.

HeLLoWeRLD · July 12, 2024, 7:54am

Awesome, thanks. The steps are a little outdated (or it’s just because I’m on Windows 10). Just the first step, though. Wasn’t working for me when I did the app data thing, so just did it another way. The path to the account wasn’t there. Just found the local store file and renamed it.