Cannot upload MacOS Applications to Enterprise
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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:
- Open a project
- Import file, observe doesn't upload and error pops up
- 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"
- Lenguaje dominante
- C++
- Estrellas
- 1.3k
- Forks
- 298
- Merge medio
- 5 d 5 h
- PR fusionados (30 d)
- 19
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Vector35/binaryninja-api
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
Vector35/binaryninja-api#8540 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Vector35/binaryninja-api#8516 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
Vector35/binaryninja-api#8503 ·
-
normalize time logs from WARP Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Vector35/binaryninja-api#8446 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Vector35/binaryninja-api#8444 ·
Todos los issues de Vector35/binaryninja-api
Issues similares
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 92/100
autowarefoundation/autoware_universe#13413 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
automated-analysis bug memory-safety
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
gazebosim/gz-sensors#662 · 1 comentario ·