Hi, I was notified about quarantine files but I don't know why? ITMS-91109: Invalid package contents - The package contains one or more files with the com.apple.quarantine extended file attribute The mentioned file is to project logo as PNG image. The PNG file is located here: MyApp.app/Contents/Resources
Search results for
ITMS-90158
1,681 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
ERROR ITMS-90725: SDK version issue. This app was built with the iOS 15.2 SDK. All iOS and iPadOS apps submitted to the App Store must be built with the iOS 16.1 SDK or later, included in Xcode 14.1 or later. Submits my app to testFlight but I am facing this error. I updated but it didn't fix macOS: Big Sur 11.7.7 Xcode: 13.2.1
Hi, I am receiving the above error after trying to upload it to the App Store. I would know what to do IF Xcode would provide WHICH file is corrupt. The error reads: ITMS-90013: Corrupt Image File - The image file $[IconName] appears to be corrupt. Again, I would know what to do if I had more information about which file(s) to fix. Could anyone FROM APPLE help me or give me a hint? Thanks, Dan Uff
A new error is occurring while uploading our app which includes an extension with a bundle identifier in the format xxx.yyy.zzz. The xxx is our application bundle identifier. We're receiving the following error message when submitting to the App Store:ERROR ITMS-90347: Bad bundle identifier. The bundle identifier xxx.yyy.zzz of the application extension xxx.app/Plugins/xxxExtension.appex should start with the application's bundle identifier xxx and not contain more than one period . after the application bundle ID.We've been using this bundle ID for a few months now with no issues. Has anyone else gotten this error or could someone from Apple please comment?Thanks,Bobby
I'm stuck with this error message a day ago. I wanted to upload new version of ios app, but I always get this error message: ERROR ITMS-90085: No architectures in the binary. Lipo failed to detect any architectures in the bundle executable. I tried to create a new app under new bundle id, and the same error occured. I tried to upload from Cordova and by Application loader 3.1 as well, with the same result.My app is generated by cordova and archived by Xcode but it runs on simulator, physical devices, last week version was uploaded, I don't kown what to do now.
When I uploaded build on TestFlight its processing and then rejected because of following response 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/
Hello, I have submitted my app build from xCode on June 10, 2015 through XCode. It passed all validations and submission was successful. But it's not appearing in iTunes Connect even now. As it is not shown, I have been trying to submit another build for the same application using the same configurations and same xCode method for submission, am getting this error description: Invalid Signature - Code object is not signed at all. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose Clean All in Xcode, delete the build directory in the Finder, and rebuild your release target. For more information, please consult https://deve
I'm getting an error when submitting an archive to iTunes connect. The error says Unsupported Architectures. The executable for myApp.app/someThirdPartyFramework contains unsupported architectures '[x86_64, i386]. This error is new since the addition of the third party framework. But I don't understand why. The error seems to indicate that I'm trying to submit a an iOS app with an embedde framework binary that is built to run on a Mac. Any ideas why my embedded binary is building this way?
Yesterday with xcode7 package online, has been the problem, can I put this part set full set again, but still can't, why
Hi,We seemed to have reached an impasse with Apple support and after sending all relevent information at their request have not recieved a reply, so checking here to see if anyone can help. Thank you in advance.We are getting the following error, eventhough we have incremented the build number as required:xcode settings are:Additional notes:The team is not set in the identity settings, but we we build the project using the following commands:> xcodebuild archive -project /path/to/project/output/Take7_IOS_Release/Take7/Unity-iPhone.xcodeproj -archivePath /path/to/project/output/Take7_IOS_Release/Take7.xcarchive -scheme Unity-iPhone > xcodebuild -exportArchive -archivePath /path/to/project/output/Take7_IOS_Release/Take7.xcarchive -exportPath /path/to/project/output/Take7.ipa -exportFormat ipa -exportProvisioningProfile T7-Dist_Store This all works without giving us any code-signing identity errors
The value for the key 'NSExtensionActivationRule' in bundle InsightOneBeta.app/PlugIns/ViewController.appex is invalid. Please refer to the App Extension Programming Guide. NSExtensionAttributes NSExtensionActivationRule TRUEPREDICATE NSExtensionServiceAllowsFinderPreviewItem Trying to upload to App Store connect but it gives me the following error every time and I am not sure what to try.
itunesconnect starts giving following error from 5-oct-2016:The Info.plist file at MyApp.app/Theme/QM-Classic/info.plist is currently named info.plist. Info.plist filename is case-sensitive and must be exactly named as 'Info.plist'Interestingly, I successfully uploaded my another app with the same usage a few hours earlier.My app correctly contains one 'Info.plist' at the root. This other 'info.plist' file is not at the root of app and is for internal app use. Correcting this will need a lot of changes in my 6 years old app.
This warning appear all times I want to upload a new version to AppStore. How can I fix it?
I've received this email when attempting to upload my app to test flight, but I have a long description like This app collects motion data to track user activity and provide accurate workout insights. Motion tracking helps improve fitness and health-related features. specified in the project.pbxproj file, which is where all of these parameters are (and where I've specified them in the past).
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
I am trying to submit an old app, but keep getting this errorERROR ITMS-90035: Invalid Signature. A sealed resource is missing or invalid. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose Clean All in Xcode, delete the build directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.htmlERROR ITMS-90035: Invalid Signature. A sealed resource is missing or invalid. Make sure you have signed your application with a distribution certificate, not an ad hoc
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Signing Certificates
Provisioning Profiles