App Binary

RSS for tag

An app binary is a file that contains machine code for a computer to execute.

App Binary Documentation

Posts under App Binary tag

15 Posts
Sort by:
Post not yet marked as solved
1 Replies
50 Views
We have a huge project. Until today we didn't use an .app but now we must in order to use Endpoint security and other stuff. Until today our binary sat in /opt/XYZ/binary.bin Now because of the .app, looks like it will have to be /opt/XYZ/Cool.app/Content/MacOs/binary.bin This change really breaks our code and will cause a massive code change. If I extract the binary from the app and place it in /opt/XYZ/binary.bin and run it, the process is killed. Is there a way to extract it from the app and run it from /opt/XYZ ? any tool, command, resource, etc' will be great.
Posted
by yoavre.
Last updated
.
Post not yet marked as solved
2 Replies
129 Views
I have a general question that confusing me. I am on M1 and I can build my app on Xcode (or create an archive) for device. Looking in to derived data I can see Debug-iphones (and simulators) folders, I can get the .app and drag/drop it to the simulator. When trying to run the app the app will crash with error: EXEC 14 Binary with wrong platform I understand that it wasn't build for simulators but rather it was build for devices and there fore the crash, but when thinking about it I dont understand why? (at least theoretically it shouldn't crash as it was build for arm64 ). Inspected the binary with lipo it was build for arm64. Comparing the binaries for simulator and device (with otool) I dont see a lot of difference except the rpath. So how does IOS knows it was build for device and not simulator (wrong platform)? is there a way to add some sort of relaxation (in the end both binaries were build for arm64).
Posted Last updated
.
Post not yet marked as solved
2 Replies
460 Views
Hi, our app - that has been successfully being updated every few weeks on Testflight for years now - suddently (although still compiling and running fine on a device connected to Xcode) fails validation & upload to Testflight. The error message does not give any info, other than "Asset validation failed - The app contains one or more corrupted binaries. Rebuild the app and resubmit (ID: 718a52a4-fed6-49ac-a025-8d62f6285cd2)". The follow up email, says : We identified one or more issues with a recent delivery for your app, "Name of app" 1.23 (1.23). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. There are no method names "listed above" whatsoever in our case. Have tried restarting, deintegrating pods and reinstalling, restarting xcode and computer, cleaning derived data etc - nothing works. In other SO or web similar cases, it seemed to be an Xcode issue that got resolved by Apple on their back end. Is that the case, if so what's ETA for fix? Otherwise any idea on where to search for the solution or what could be the issue? Thanks
Posted
by Apneist.
Last updated
.
Post not yet marked as solved
6 Replies
686 Views
After updating from MacOS 14.0 to 14.1 we got permission errors within an app we developed. We got an "operation not permitted" error if the app tries to access files on a samba network share which is mounted by another tool. Additionally, we got a "Permission denied" if the app tries to run programs outside the app, for example /usr/local/bin/ip. The app works fine on Catalina, Big Sur, Monterey, Ventura and Sonoma 14.0. The app and its components are codesigned and the app is notarized, no entitlements. In the Info.plist the NSNetworkVolumesUsageDescription key is set. Any ideas? Could it be that the app is sandboxed by default on MacOS 14.1? And we have to disable sandboxing via entitlement? Thanks for any input!
Posted
by Opsi2Mac.
Last updated
.
Post not yet marked as solved
1 Replies
857 Views
Hello all, I have an app that has been rejected due to Guideline 3.1.4 and I don't know how to get around it. The app is essentially a QR scanner for the construction industry that scans QR codes created by a plugin for design software. The app user can use the service completely free with no log in required. Once the QR code is scanned the app returns a result there are no features locked to the app user. The response form the review board is; Your app enables additional features or functionality when used with augmented reality markers or QR codes. However, those features are not available in the app to users without the necessary markers. Next Steps To resolve this issue, please provide a means to access these features from within the app, such as through achievements or in-app purchase. If they can be freely obtained, such as through a link to a website, please revise your app to include clear instructions for obtaining the necessary markers or codes. Which to me seems illogical because if the app user doesn't have a drawing with a QR code on it they don't need to use the app or know of its existence to find the result another way. The app user and the plugin user are two completely different entities and the app user would never be able to create or obtain the QR codes from the app without a drawing. The typical scenario would be the Architect would produce the drawings and add the QR code and give the drawings to the builder who would scan the QR code with the app to get a result. I am struggling to see how this differs to a generic QR scanner that is scanning a code on the side of a can of coke. Any assistance or advise would be appreciated.
Posted
by ReviCheck.
Last updated
.
Post marked as solved
4 Replies
43k Views
I've tried the various methods listed in the forums, but it doesn't work so I ask a question Here's how I tried:Build Settings Change "Product Name" TARGETS Select app Change "Display Name" Project Navigator Select project name Double-click Change "project name" Rename Mange Scheme Change "Scheme name" info.plist Change "Bundle Display Name" After doing the above 4 methods, Clean Build and install the app on the device. Is there any other way? The app is released on the App store.
Posted
by Swagger21.
Last updated
.
Post not yet marked as solved
1 Replies
597 Views
Getting the following incorrect error when uploading to App Store Connect. I've tried with Xcode and Transporter. The APIs are not being referenced anywhere in my project. There was a similar issue to this on the forum a couple weeks ago and it sounded like Apple resolved it but I am just now seeing this happen. Message: ITMS-90338: Non-public API usage - The app references non-public symbols in APP_NAME: _CMTimebaseCopyMasterTimebase, _CMTimebaseCreateWithMasterClock, _CMTimebaseCreateWithMasterTimebase. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions.
Posted
by chansencc.
Last updated
.
Post not yet marked as solved
1 Replies
1k Views
Hello all, I apologize if it's not in the right section. I'm working on a little app, mostly a CRUD and three HTTP requests. We will use MDM software to deploy the application (not the App Store). There is no pods, package, or specific framework, it's only basic Swift code. Unfortunately, I must do a pentest to push my app into production. The security engineer said he would use the mobile security framework tools. So I tried myself before to be sure that we would succeed. After using the static analyzer, I discovered several issues. The first issue is : The binary may use _malloc function instead of calloc. And I don't know how to prevent that since it is low level, and I don't have access to that. My second issue is a warning : This binary is not encrypted. Honestly, I don't know how to fix that since it seems impossible to encrypt the codebase. Or maybe I'm wrong? Thanks to everyone who will take the time to read and try to help. Regards
Posted
by SlimanD.
Last updated
.
Post not yet marked as solved
2 Replies
1.2k Views
Hi All; I recently found a git repo that cracks our license verification library. What are the recommended methods to detect hooking? Is there a way to force integrity verification both on loading and at random times when running?
Posted
by pjford.
Last updated
.
Post not yet marked as solved
3 Replies
1.6k Views
After static analysis of IPA binary, We found below warnings • @rpath: It is recommended to reconfigure the application binary to ensure it has disabled the Runpath Search Path(@rpath) How can i fix this?
Posted
by jk_r.
Last updated
.
Post not yet marked as solved
26 Replies
15k Views
I have this warning when publishing the App, it does not prevent it from being uploaded to review, however, it had never come out, and on the other hand I do not understand what the error could be...
Posted
by RobertoMG.
Last updated
.
Post not yet marked as solved
1 Replies
1.1k Views
We've created and distributed a Universal app for Intel/Apple Silicon devices, which then gets launched by an Intel-only launcher. I'm finding that if I launch the app from the launcher, Activity Manager is reporting that it is an Intel application, whereas if I launch it directly, it reports as an Apple (Silicon) application. (Worth noting: this app is completely codesigned/notarized.) This is definitely odd, because we have other Universal projects that get distributed on different Intel-only launchers (e.g. Steam) and they are properly launched as a native Apple Silicon app. I apologize that I'm low on information here; happy to do more work to provide additional info.
Posted
by mcarriere.
Last updated
.