Hoping someone here knows why Size has two wildly different values. In the Finder > Size column it shows 158.9MB, which matches the "bytes." So where is the 85.6MB coming from and why?
MacBook Pro 13″, macOS 10.13
I don't have the App, but I suspect the Package Contents include 1,000s of tiny files.
Assuming your particular Allocation Block size is 4,096 Bytes, (that is the smallest size of Disk that can be used, ie. a 1 byte file will take up 4,096 bytes of Disk, a 4,097 byte file will use up 8,192 Bytes), so if you had 1,000 10 Byte files it would only be 10,000 Bytes for the Package, but would use up 1,000*4,096 Bytes of Disk space - 4,096,000.
I don't have the App, but I suspect the Package Contents include 1,000s of tiny files.
Assuming your particular Allocation Block size is 4,096 Bytes, (that is the smallest size of Disk that can be used, ie. a 1 byte file will take up 4,096 bytes of Disk, a 4,097 byte file will use up 8,192 Bytes), so if you had 1,000 10 Byte files it would only be 10,000 Bytes for the Package, but would use up 1,000*4,096 Bytes of Disk space - 4,096,000.
Good enough for me. Thanks, @BDAqua.
It doesn't seem to have a lot of small files when I go rummaging about in the package, but that seems reasonable. It's peculiar that "on disk" wouldn't match "Size" in the Finder > List mode, but *shrug*.
OK, take care my friend.
Get Info shows two sizes for some apps ("bytes" bigger than "MB on disk")
