Mac OS install not creating a .app but just a folder called contents

[jerkwagon]

Okay, you've got a great title already! Here's a suggestion for the description box, based on what you've experienced. You can copy and paste this, adding your specific macOS version:

Subject: Mac OS install not creating a .app but just a folder called contents

Description:

System Details:

• Operating System: macOS [15.4]
• Processor: Apple M3
• Balamod GUI Version: 1.2 , 1.34

Problem Description:

When I run the official balamod.pkg installer for Balamod GUI, the installation completes successfully according to the installer prompts.

However, instead of creating a launchable Balamod GUI.app (or similar name) application bundle inside my /Applications folder, it creates a folder literally named Contents directly in /Applications.

This means there is no application icon to click and launch the GUI. The "Contents" folder contains the expected internal structure of an app bundle (MacOS, Resources, Info.plist etc.), but it's not wrapped in a functional .app package.

Steps Taken:

• Downloaded the latest .pkg installer from the official GitHub releases page.
• Ran the installer multiple times.
• Deleted the incorrectly created "Contents" folder and tried reinstalling.
• The result is consistently the same: only a "Contents" folder is created directly in /Applications.

(Optional - Add this part if you ran the diagnostic command)

• When I try to run the executable directly from the Terminal using /Applications/Contents/MacOS/Balamod,

[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PathNotFoundException: Cannot create file, path = '/Users/XXXXXX/Library/Application Support/Balatro/balamod/commands/' (OS Error: No such file or directory, errno = 2)
#0 _checkForErrorResponse (dart:io/common.dart:55)
#1 _File.create. (dart:io/file_impl.dart:286)

#2 Installer.install (package:balamod/services/installer.dart:101)

#3 BalamodDetailsCubit.install (package:balamod/blocs/balamod_details/cubit.dart:51)

This seems to be an issue with how the .pkg installer handles the creation of the application bundle on my system configuration.

---

Just replace the bracketed parts with your specific details, and this should give the developers a clear picture of the problem!