AnyType closed to perform an update while I was typing

What’s The Bug?

Right at the outset I want to start by saying I am really enjoying AnyType and really appreciate the efforts of the team working on this! This product clearly has a lot of UX thought put into it and I think the community can see that. This is a minor UX gripe, but I wanted to mention it anyway because it was fairly disruptive.

Bug: AnyType closed to perform an update while I was typing.

I did not receive any indication or warning that an update was available, and I lost a bit of what I was working on because the editor simply closed on me.

How To Reproduce It

I am not sure how to reproduce it, I did not take any action (to my knowledge) to update the application.

The Expected Behavior

I would have expected some kind of prompt indicating an update was available

Additional Context

The application closed, almost like it crashed (abruptly), but probably just closed. There was a small native-windows progress bar that popped up saying something about updating and then that closed. I had to re-open Anytype myself, it did not come back up.

Device

Windows Desktop PC, custom

OS

Windows 10

Anytype Version

0.43.6

Network Mode

AnySync

Technical Information

OS version: win32 x64 10.0.19045
App version: 0.43.6
Build number: build on 2024-11-07 16:33:48 +0000 UTC at #7ef8bff406cf2125f54c71f92cb2815f7e6c70bd (dirty)
Library version: v0.36.10
Anytype Identity: A8bR72Yn7kSKeieJrMSoCqwtBTWnbRv2H8kAyyh7VtTJT4cv
Analytics ID: 11d85683-d1ea-4860-b923-f2966ada3b24
Device ID: 12D3KooWNmiwF3bWFMbU98ZoGLRqtu8CFEhckcCwALkyQZWFWY7k

I think the issue is that

  • while one is typing
  • the notification appears
  • the user doesn’t notice it
  • and continues to type while hitting enter at some point
  • and the update proceeds

It is a common UX issue people complain about. I hope it will get addressed at some point.

Thanks for the feedback krst, that seems entirely possible. I did not notice a notification, so I can’t say for sure.

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.