I’m experiencing this bug for a while. Last night it popped up in my mind that maybe storing the file in Dropbox is causing the problem, so I moved the file to iCloud and the problem went away. Strange, indeed.
Below are the details of the bug,
Cheers,
H.
Bug: Cashculator crashes if the file is saved in Dropbox and changes made to recurring payment. Affected operating system(s): macOS Sequoia 15.5 Affected version(s): Cashculator 2.7 (and below)
Reproduction Steps
Create a recurring plan in expenses. Planned or Actual doesn’t matter.
Save your file and exit.
Open Cashculator.
Make changes to same recurring plan.
Change details window pops up…
Crash.
Expected Behavior
Create a recurring plan in expenses. Planned or Actual doesn’t matter.
Sorry for my late reply. It’s not possible for me to open the file in two Macs at the same time . I’ll try to reproduce problem with a video, and send you the logs afterwards.
Sorry @Jacob, I still didn’t have the time to recreate the crash with a fresh file, but I have noticed another anomaly.
See, I have moved my file to iCloud after Dropbox created some problems. Now, if the file is in iCloud, I get a dialog saying that the file is modified outside the application and how should Cashculator proceed.
I think the multi-file nature of .cashdb packages create consistency and integrity problems when they are stored on real-time syncing folders since both services try to do their magic on per-file basis. At the end of the day, a .cashdb package is a directory with a specific structure.
BTW, having this behavior OK in my case. I’ll just store the file locally on my Mac.
I’ll still do my promised screencast with a new file and post it here, but wanted to add new information I have gathered.
It only happens if the Cashculator window is maximized full screen (as on its own desktop). Otherwise it doesn’t crash. It’s not related to Dropbox, but being fullscreen.
Sorry for the confusing report. I discover this as I dig.
Oh, that’s a good lead with the full-screen. Can you send me the crash report? You can find it in the Console app, under Crash Reports in the sidebar. Select one, press Command-R to reveal the file and send it to me. Either attach here or email it to support@apparentsoft.com. Also, do you know what action triggers the crash in full-screen mode?
As I dug the problem, it got a bit weirder. Also, looks like some of my observations were wrong. Sorry about that. I’ll try to recap and collect everything under this post.
Reproducing the problem requires Cashculator being full-screen (as in having its own desktop).
The crash is not a full-blown crash. Cashculator “closes” the file, hence there’s no crash log.
The bug sometimes fails to reproduce if you open the same file w/o quitting Cashculator, but sometimes it just reproduces successfully.
Is there any in-software logs I can dig and provide you more insight? This is one of the more stranger bugs I have encountered and is plainly confusing.
Hi. No, there are no specific logs that Cashculator itself produces. You can open the macOS Console app and search for “Cashculator” (better if you filter so that it’s the process and not “any” Cashculator) and see if anything stands out, but these console logs are not very friendly and can have a lot of noise in them.
Thanks for the info. I’ll try to reliably reproduce the problem and write a better report. There’s no point in wasting your time with an unreliable and inaccurate bug reports.
The issue is interesting though. I can tell that with my developer hat.
Thanks for developing Cashculator and all the hard work.
. I’ll try to reproduce problem with a video, and send you the logs afterwards.