Super, super annoying.
Using Blocs is a total random process due to this. I’ve lost approx 10 hours work during a 48 hours hackathon - not pretty.
And that’s after first shelling out and buying the tool.
I’ve had this issue since the beginning. It seems like it doesn’t like me to leave Blocs open. When the computer goes to sleep, after it wakes up it will never save again. It acts like it is saving, but it isn’t. Very very frustrating. Lost many hours of work.
I’ve just experienced same issue with ‘saving’.
Sorted out after restart of computer but all saved work is lost.
I have the same problem here. This is a serious problem and I hope there will be a solution soon, makes the app nearly unusable. Maybe I do something wrong or it is Catalina. Grateful for any tip
I’m aware of the situation the cause is still unknown but it’s not a consistent issue for all Blocs users.
It appears to be limited to Catalina so far, which was recently updated.
So far, restarting either the Mac or Blocs corrects the issue.
Give this a try and see if the problem continues.
5.2 is currently in beta so I’m hoping I’ll get this snagged before the release of this version.
I’ve had this problem, but only rarely - it’s not consistent at all. The way I’ve corrected the issue - without closing Blocs was to select force quit from the apple menu, select Finder and then click the relaunch button. When finder reopened, I was able to save again. This would suggest an issue with the OS itself, so I think it’s worth trying to see what happens on your system. It worked for me, but I accept, I don’t really know if its a solution that will work for everyone.
That’s interesting I’ll log that down with notes For this issue.
I have my concerns it’s an issue at the OS level too, some kind of permissions issue.
My solution came to light by accident. When my Blocs project locked, I noticed that clicking on desktop folders wasn’t opening the folders. To correct that problem, I relaunched Finder. It was then that I noticed that Blocs was able to save again - strange behaviour!!
I am having issues too… I’ve only been using Blocs for a short time, but in the last few days it is randomly not saving. The saving progress bar completes, and all seems well, but when I reopen the project file it becomes apparent that my previous session hasn’t saved. Sometimes it does, sometimes it doesn’t… highly frustrating, as I’m currently having to save every five minutes, close Blocs and reopen it to make sure it has saved correctly!!
Did you try the finder relaunch trick to see if that brings the save option back. If you relaunch finder, you don’t have to close your Blocs project, but after the relaunch, it may enable you to save your project file.
Thanks, I will have a play around and see if that works for me. Hopefully the issue is resolved soon, so I don’t have to be on my guard all the time! Like someone mentioned above, closing my macbook whilst having an unsaved project open seems to kill the ability to save… I’ll just need to be careful until a fix is found.
So if you close your laptop it breaks save every time? Are you using Catalina?
I’m wondering if this issue relates mainly to people using laptops. Blocs appears to be an app that doesn’t prevent sleep which means that if a laptop goes into sleep mode, the app will not continue running in the background. Maybe when the laptop comes out of sleep mode while blocs is fired up, it loses its ability to save upon being woken up. Certainly, if a project is using hosted assets on a cloud server, the connection to the server would be lost when the app goes into sleep mode, which may cause an issue or two. I understand that disabling sleep mode consumes more power, but it may be something that is contributing to the issue. Therefore, it may be an idea to have a user selectable App Nap option enabled in the app info window. As the screen shot below shows, blocs doesn’t currently have the option to turn this function off and on. Presumably, app nap is enabled by default.
Certain apps, such as Apple music DO continue running in sleep mode which means it continues playing music when the lid is closed on a laptop. See the activity monitor screenshot below.
It certainly appears to be the case, I’ll have to play around and see if I can replicate the issue consistently by closing the lid. Yes, I’m on Catalina.
I’ve just tried editing a project and then both closing the laptop, and putting it to sleep manually before saving, and it saved the project fine… sorry, that was what seemed to be causing it for me, but obviously not.
It could be, it may just take extended periods. I’m guna started testing this theory on Monday when I’m back in office.
Hi Norm, I’ve experienced the same exact problem on Catalina (10.15.6) and wondered what the root cause was.
I noticed someone else posted that they experienced the issue when a user was controlling the screen remotely, and then realized my setup isn’t all that different. More precisely, I sometimes use an app called Barrier that allows me to control my PC using my Mac’s keyboard and mouse. In my case, the Mac is the master while I control another machine remotely, but I figured maybe there’s something in this type of setup that’s causing the problem.
Since carefully quitting Barrier and all its processes on my Mac before running Blocs, I have not experienced the same problem and the app saves everything normally. This doesn’t definitively prove anything, of course, but it may be worth looking into.
Blocs is wonderful and incredibly valuable software. Thank you for all you do!
Unfortunately, it is still happening and frustrating. Sometimes it saves the project, sometimes there is no content when I open it again. The assets are visible, but all the pages are gone.
The files with the purple icon are the bad ones
Which version of Blocs?
With Blocs 3.5.3 if save fails, it should keep the save dialog open, if this happens generate an app system report before you restart Blocs. The report should include the crash report if the OS issues one.
Apologies, the issue is pretty inconsistent so it’s making it very tricky to track down.