hdiutil detach does two things: 1. it will unmount the volume from /Volumes and 2. it will detach the disk image. Currently, appdmg will retry calling hdiutil detach when it fails. However, if it fails due to 2, then /Volumes/NAME as specified in temporaryImagePath will be gone. Then subsequent retries will fail as well. We are observing this happening on a slow filesystem where the writes are being flushed but the volume was able to be unmounted.
Suggestion: Use diskutil info /Volumes/NAME to get the Device Node and use the node name for hdiutil detach.
hdiutil detachdoes two things: 1. it will unmount the volume from/Volumesand 2. it will detach the disk image. Currently,appdmgwill retry callinghdiutil detachwhen it fails. However, if it fails due to 2, then/Volumes/NAMEas specified intemporaryImagePathwill be gone. Then subsequent retries will fail as well. We are observing this happening on a slow filesystem where the writes are being flushed but the volume was able to be unmounted.Suggestion: Use
diskutil info /Volumes/NAMEto get theDevice Nodeand use the node name forhdiutil detach.