Same here on 13.5.2, but not only APFS, also MacOS Extended and ExFat (6 disks corrupted in the past year). All these disks where formatted with the MacOS disk utility. I suspect the bug is somewhere in the software dealing with the USB(-C) connections as only 1 of the instances involved me accidentally removing the disk before ejecting. Suggested solutions in previous posts for repairing the disks with Disk Utility or via command line in Terminal or via re-boot, all did not work. Now only using APFS for Time Machine. Gradually moving all other disks (many) to ExFat. While MacOS is not able to repair the disk, I can fix the ExFat disk in a few minutes on Windows. The MacOS Extended disk I could mount read-only and copy its data to a new disk, albeit very slow (5 days for 4.5 Tb). With ExFat was I able to mount the disk read-only on MacOS with WD software in two instances. In another instance I could not even mount it read only, but I can still access the disk on Windows ... The only disadvantage of ExFat is that is uses 20% more space (I found out when copying 4.5Tb from a %Tb OS Extended disk to a new 5Tb ExFAT disk, it was full at 4Tb from the original disk). Ever since my first APFS Time Machine disk became unusable a year ago (not broken, reformatted and still using it), I have two Time Machine back-up disks. And fortunately I started years ago to make 2 back-ups of all my data that does not reside on the computer or in the cloud. Apart from this being a lot of extra work, I even don't feel safe with double back-ups anymore when external drives are being destroyed on my MacBook (2020) so often. Had not used my simple Windows computer, that came for 10% of the price of my MacBook, for many years and now it's my data saving machine for broken ExFat drives ...