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

27 Posts
Sort by:
Post marked as solved
20 Replies
7.3k Views
Hi, We are using Firebase Crashlytics to collect crashes from our app. Firebase Crashlytics says that the dSYM is missing to process crashes for the recent two versions of our app. We have recently not changed anything in our app distribution process (it is based on CI/CD). For the non-product change, we moved one of our internal frameworks to be managed by SPM (previously Carthage). In build settings, we have set : Debug information format: DWARF with dSYM Files Enable bitcode: Yes Because of the latter, we manually download all dSYMs from the AppStoreConnect page and upload them to the Firebase Crashlytics for each new version. I've double-checked the UUID's and the one mentioned by Firebase is missing in the downloaded (from the AppStoreConnect) zip file. The zip file contains dSYM for our app but with a different UUID. Is there anything I can do to verify that generated dSYMs have the correct UUID? Not sure if this is related, but when I try to download crashes via Xcode Organiser, I got an error: Unable to download crash information. An error occurred preventing Xcode from downloading updated crash information. The value “2021-07-27T00:00:00Z” is invalid. Please try again later.
Posted
by
Post not yet marked as solved
2 Replies
1.1k Views
Hello, I am trying to submit my new application to code review in Appstore. I validate binary in XCode. OK. I uploaded it from XCode to Appstore. OK. Completed processing. I run it through TestFlight and tested on several devices. OK. I submitted it to review. I got message. Waiting to Review. One minute later, I got Invalid bimary. I tried one more time, and I created new build and and uploaded it. The same result. I got mail from Apple - that application is in Invalid binary state. No explanation, no clarification... OK, may be y Xcode installation is broken? I asked my team mate to build new release and upload it to Appstore. The same result, one minute after submitting to Appstore, I got message - Invalid binary. No clarification, no explanation. I asked tech support. I got response - you should get message with explanation, make fixes and resubmit. I resend them message from Apple server. And didn't get any response from tech support at all. I created another request. And put there reference to my previous request. And I got another common words as answer - something is wrong with your application... I suspect, tech support doesn't read my mail at all... So my question is: how can I get info, what actually is wrong with my application? Why Apple server considers it as Invalid, while all tests, I can make, returns me "Passed" state Thanks in advance. Regards, Vladimir
Posted
by
Post marked as solved
3 Replies
11k 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
Post marked as solved
16 Replies
6.4k Views
Hello, My team is currently having an issue uploading our app to the AppStore because of the following issues: ITMS-90562: Invalid Bundle - Bitcode failed to compile for your watchOS binary because it includes assembly source code or inline assembly. To resolve this issue, rewrite the corresponding code in a higher-level language such as Objective-C or Swift and redeliver your app.  ITMS-90562: Invalid Bundle - There's an issue with the app's bitcode compilation. Rebuild the app using the current public (GM) version of Xcode and upload it again. Firstly, we do not have a watchOS app at all. Our last release was successful when built on Xcode 11.6 and we're currently using Xcode 11.7. According to Apple, Xcode 12 isn't required until April of 2021, so I'm not sure what it's complaining about. Here's what we've tried. We created an AppStore build and ran it through the validator and that succeeded. It even uploads fine, but doesn't successfully process once uploaded. We created an Enterprise version of our app and exported it, making sure to enable the "Rebuild from Bitcode" option to hopefully mimic what the AppStore is doing and failing at and it still succeeds. We downloaded and used the Transporter app from Apple to try uploading our AppStore ipa, but the logs didn't indicate anything suspicious (perhaps because the bitcode compilation for AppStore variants happen on Apple's servers?) We searched for anything that could have indicated "watch" or "watchOS" in our codebase and build settings and dependencies (built from Carthage), but we didn't find anything there either. We went through the Export phase again for the AppStore build and disabled Bitcode. The only one to succeed was #5, but we don't want to do this as a long term solution, but don't understand how to get more information as to what the problem is exactly. Does anyone have any information on this?
Posted
by
Post not yet marked as solved
12 Replies
4.4k Views
When Submitting new App version for Review, the status changed to Invalid Binary and I got an email saying the following: We identified one or more issues with a recent submission for App Store review for your app, ****************. Please correct the following issues, then upload again. ITMS-90118: Invalid routing app setting: To upload a routing app coverage file on App Store Connect, you must define the app binary as a routing app.
Posted
by