Good question; Neither, and both hahah ... It is actually an error by the runtime tools.
Unfortunately, it doesn't say much either. This could be any thing, from trying to accessing a non-existing array index, or a function return value that doesn't exist or has a different structure, or a system call that fails, etc.

I've seen a few users mention this as though, and as I understand (since I have not seen it on my Macs) is that reboot seems to fix this. Odd as it may sound.

p.s. are you running on Intel or Apple Silicon hardware?

A reboot really fixed the dialog thing. I am unable to make a backup though. After selecting the destination file a red abort-icon shortly appears and then nothing's happening. No error in log.

Are you running ApplePi-Baker on an M1/M2 Mac maybe?

Yes, it's an M1 Max.

Did you add ApplePi-Baker in System Settings -> Privacy & Security -> Full Disk Access ?

I had a friend of mine test this and he reported back that ApplePi-Baker did not run initially on his M1 Max either, until he added ApplePi-Baker to the Full Disk Access apps. He mentioned that, oddly enough, reading a disk raw goes by undetected under Ventura, so you do not get the warning message that "Full Disk Access" is not allowed.

Worth a try. 😊 

Success with full disk access manually added. Thanks so much for your support. Will make extra donation. Such a useful app when working with Raspberry Pi. Allready saw myself working command line with dd ...

Cool - that is good to hear! ... And you're most welcome!
Thank you for being patient and even more so for the very generous amount of coffee ☕️ 😊 
Just got the notification I think (egoshooting?) ...

Hi, just had the same problem. I had "Full disc access" enabled and disabled. Always the same problem. Then I figured out in diskutil, that I had a new disk, which was the time machine backup disk. Just before it was not active. So I stopped the backup and hence the violation error disappeared. So the reboot recommendation workes, because after the reboot the backup is not active immediately. So running time machine backup and then starting Pi Baker brings up the error. Hope it helps.

@mhl5k Very nice catch! I'll have to try that on my own Macs! 👍

hello !

I just start using apple-baker 1st time on my Mac m4 max . trying to backing up a 1T nvme to another nvme storage ....

initially, I was trying to backing it up to my networked Mac mini server thru a 2.5G lan ....and it's works perfectly created a .7z for me on Mac mini. it's fully utlitise my network speed and finish in few hours....

but then I realised why dont i plug in my 1t  nvme and backing up locally, would speed up the process. (then copy that .7z to my server with full TB speed.)

the speed in deed much faster (1xxx mbs) finish in 30 ish min ,,,,,

but thing start get weird ....

I  keep getting the "Access Violation" right after it finish . also I noticed the app doesn't Shrinking the result file anymore ...it ended up with a 1T size xxx.tmp ....

now I tried both on my Mac mini m2 pro ....and my mbp m4 max .....

yes ...I tried reboot . set TM to manual ?....but the result are same. Warning and a 1T backup.tmp on my target drive.  

can anymore pls kindly help ?

English is not my 1st language , pls pardon me if it hard to understand ;) 

thx in advance !! ;)

Hey there 😊 

Sorry to hear you're running into an issue ...
Considering the size you're working with: do you have enough diskspace on the target disk?

1. A 1 Tb backup would need at least 2 - 3 Tb free diskspace if you wnat to us e the resize function.
2. The resize function is only useful for a backup of a disk that has one FAT partition and one EXT partition.

How is the backup going without the resize option enabled?