Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug Report: CRITICAL: macOS: Cannot install due to corrupt DMG #661

Open
Swivelgames opened this issue Aug 23, 2024 · 7 comments
Open

Bug Report: CRITICAL: macOS: Cannot install due to corrupt DMG #661

Swivelgames opened this issue Aug 23, 2024 · 7 comments
Assignees
Labels
bug Something isn't working high priority Something causing a significant issue or would cause a large improvement

Comments

@Swivelgames
Copy link

Describe the bug
When attempting to open the install DMG, the following error occurs:
image

When trying to mount the DMG via CLI, I get the following:

hdiutil attach Pomatez-v1.7.0-mac-arm64.dmg
Checksumming Protective Master Boot Record (MBR : 0)…
Protective Master Boot Record (MBR :: verified   CRC32 $4D954D6C
Checksumming GPT Header (Primary GPT Header : 1)…
 GPT Header (Primary GPT Header : 1): verified   CRC32 $3A8A4ACE
Checksumming GPT Partition Data (Primary GPT Table : 2)…
GPT Partition Data (Primary GPT Tabl: verified   CRC32 $5F5F7B02
Checksumming  (Apple_Free : 3)…
                    (Apple_Free : 3): verified   CRC32 $00000000
Checksumming disk image (Apple_APFS : 4)…
..........................................................................................................................................................................................................................................
         disk image (Apple_APFS : 4): verified   CRC32 $FAF6A9A9
Checksumming GPT Partition Data (Backup GPT Table : 5)…
GPT Partition Data (Backup GPT Table: verified   CRC32 $5F5F7B02
Checksumming GPT Header (Backup GPT Header : 6)…
  GPT Header (Backup GPT Header : 6): verified   CRC32 $125B8055
verified   CRC32 $F2C6A99B
hdiutil: attach failed - no mountable file systems

To Reproduce
Steps to reproduce the behavior. Example:

  1. Download the latest version of Pomatez for macOS via the website
  2. Attempt to mount the DMG for installation

Expected behavior
DMG is mountable

Desktop (please complete the following information):

  • OS: macOS Sonoma 14.5
  • App Version v1.7.0
  • Installer Used macOS Apple Silicon

Additional context

It's worth noting that the DMG is not empty:

image

@Swivelgames
Copy link
Author

Just tested it with the Tauri Beta, and the same issue occurs.

@sekwah41
Copy link
Member

That's peculiar. I'll check on my MacBook later or this weekend. I know I had to do some stuff because Apple updated some terms for the apps to sign again.

@sekwah41 sekwah41 self-assigned this Aug 23, 2024
@sekwah41 sekwah41 added bug Something isn't working high priority Something causing a significant issue or would cause a large improvement labels Aug 23, 2024
@sekwah41 sekwah41 moved this to Bugs in Pomatez Roadmap Aug 23, 2024
@sekwah41
Copy link
Member

sekwah41 commented Aug 23, 2024

Just checked and I can open both the Tauri version and the Electron version's dmg's on my Macbook Pro M3. I will try to find another user to test to ensure its nothing to do with development keys

@sekwah41
Copy link
Member

for reference this is what i get when I run hdiutil verify -verbose
Screenshot 2024-08-23 at 11 49 03 PM

@sekwah41
Copy link
Member

Could you send checksums of the files you downloaded?
e.g. shasum -a 256 Pomatez_1.7.0_universal-mac-tauri-beta.dmg and show me the numbers?

Screenshot 2024-08-24 at 12 00 10 AM

they should match with these if your download isnt corrupted

@sekwah41
Copy link
Member

Can I check if this is a personal machine or a work laptop? I am not familiar with mac in enterprise but there is a chance it could be the mobile device management software you have blocking the opening of unapproved dmg's.

The logs you have don't seem to say they are corrupted vs its not found any it can mount as they all say verified.

@sekwah41
Copy link
Member

The fact that both fail further makes me believe it's a device management issue. If you are on a work or education machine you'll have to ask whoever is managing it to authorise my app id or dev certificate. (Not sure which it would be)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working high priority Something causing a significant issue or would cause a large improvement
Projects
Status: Bugs
Development

No branches or pull requests

2 participants