Fonts Being Deactivated On Their Own (Dropbox watched folders)

Bugs
1

Ive noticed Fonts will completely deactivate on their own, it’s very random and sometimes it will just straight up deactivate all my fonts and I will have no fonts active. I notice this usually when my computer starts because font base runs on startup. I’m honestly tired of this and thinking of canceling my subscription. The organization is nice but the fonts not staying active is a hassle and im probably going to move to a different app. It’s so basic of a function to get wrong.

  • Sequoia 15.0.1
  • FontBase version 2.20.7
  • What actions caused the issue: I have no idea
  • If possible, attach a screenshot: Would not show anything relevant
2

Hello @mark21, thank you for your post and welcome to the forum :pray:
Very sorry for the major inconvenience you’re experiencing :pensive:
Are your fonts located on a local hard drive, or a network one (NAS/Dropbox/GDrive etc)?

Thank you again,
Yuriy
FontBase Dev Team

3

Thanks @yuriy, I should have noted my fonts are located on dropbox

4

Thank you for the quick reply @mark21 :pray:
It’s not the first time we’re encountering this app behaviour and as of now we’re still looking for the solution :pensive:
I’ll quote a part of our FAQ below for more background on the subject:

" Why do I experience issues with network drives?

We have received reports of inconsistent behavior when FontBase Root folder is located on a network drive, or when some of the watched folders you have added into FontBase are located on a network drive. By network drive here we mean a drive connected via LAN, a NAS drive, services such as Google Drive, Dropbox etc.

Sometimes it takes a while for your computer to get full access to the network drive, hence the inconsistent behaviour you might see in FontBase. For example, you launch FontBase with a folder on a network drive added as a watched folder and you have FontBase open on computer startup. It’s possiblle that FontBase loads faster that the access to network drive is established, so FontBase tries to check on the watched folder, cannot access it and removes it thinking it was physically deleted from the hard drive.

At this moment we are still looking for a possible solution to overcome the limitations of such network setups. During this time we recommend adding network drive folders as regular, not watched, folders, to make for a more stable experience."

Sorry for not providing a better way to mitigate this right away :pensive:

Thank you again,
Yuriy