Cannot upload MacOS Applications to Enterprise

Open
#8,490 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, macos
Domain
desktop

Research direction

Reproduce the issue in an Enterprise project using the reported macOS version and Binary Ninja build. Start with the Import Files and Import Folder flows, then inspect the log entry about refusing to create a file with an empty name. Done means a macOS application can be selected and imported with a defined, tested treatment of executables and non-executable bundle contents.

Written by the indexing model from the issue text.

Description

Version and Platform (required):

  • Binary Ninja Version: 6.1.10552-dev
  • Edition: Ultimate
  • OS: MacOS
  • OS Version: 27
  • CPU Architecture: M3 Pro

Bug Description:
MacOS Applications are unable to be uploaded to an Enterprise project via either "Import Files" or "Import Folder". Import files allows me to select the application, and it pops up importing at 0% and then stops with no upload. The error message in the log says "[Projects] Refusing to create a file with an empty name". Import folder just grays out the selection so you can't upload it.

I don't actually know if this is a bug or intended functionality, but the error makes no sense and this should definitely be possible. So I would like to add this either way.

Steps To Reproduce:

  1. Open a project
  2. Import file, observe doesn't upload and error pops up
  3. Import folder, observe nothing's selectable

Expected Behavior:
It should import a folder containing the executables in the directory. I would leave out things like the .plist files and generally non executables, though I don't know to what extent we should not include things.

Screenshots/Video Recording:
"Import Folder" view, in the log you can see the error messages from "Import Files"
Image

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.