it's return:
1、Apple's web service operation was not successful
2、Unable to authenticate the package:730904073.itmsp
3、ERRPR ITMS-9000:"This bundle is invalid.Apps that include an armv7s architecture are required to include an armv7 architecture."at SoftwareAsset/SoftwareAsset(MZItmspSoftwareAssetPackage)
but my "Build Settings","Architectures"is"Standard architectures(including 64-bit)(armv7,armv7s,arm64)".
And when I turn the "Architectures"to the "Standard architectures(armv7,armc7s)" it's same return.
In the past three days,it aways return me this error.
I really don't know what to do.
Please help me .
OK,I got it !
I delete the “armv7s” in Valid Architectures both 'debug' and 'Release'.
And turn the 'Build Active Architecture Only' to 'No'
Then Apple receive it！
I too faced same issues during App submission, I have resolved above problem by following steps
1) Go to Applications->Xcode->contents->Applications->Application Loader.app->Contents->MacOs->itms->java->lib there u will find a file net.properties open it with text edit and then change the line # https.proxyPort=443 with # https.proxyPort=80
2) Quit Xcode and reopen after in build settings make it to Don't Code sign then clean the project
3) in the Build Active Architecture Only all values to NO
4) for Architectures select Standard architectures (including 64-bit)(armv7,armv7s,armv64)
if don't have any images errors you can go ahead and archive and try to submit. if you have it then follow next steps
5) Go -Info.plist file in Xcode in supporting files in that file select icon file remove all the images if you have any thing
6)then clean project and reassign all images in General tab of the project(if u select Project title u can see this tab)
7) select appropriate Code signing identity and Provisiong profile and archive and submit to store
Related
Ok so I have just about managed to get to this point on my own but am now having some issues code signing the app specifically with the AdMob framework. I am getting this error:
Command /usr/bin/codesign failed with exit code 1 the details it are giving are as follows: Applications/MyApp.app/Frameworks/GoogleMobileAds.framework: bundle format unrecognized, invalid, or unsuitable
I have read the other posts on the site and tried many different ways of fixing this. If I untick 'Code Sign On Copy' the archive builds successfully but then fails on validation with a match error. This is how I have my frameworks set up currently:
Any help would be much appreciated!
I saw this same issue with a different framework.
The solution for me was removing the framework from the 'Embedded Binaries' section and only adding it to the 'Linked Frameworks and Libraries' section in the target 'General' tab.
I have just seen the same issue but with a different framework that was the social framework and then I did below:
go to build phase -> embed frameworks -> press copy only when installing check box
then it worked with me with no error
I had a similar problem but with a different framework. The solution for me was to make sure that the framework was present in these three places:
General tab:
Embedded Binaries
Linked Frameworks and Libraries
Build Phases tab:
Embed Frameworks
I ran into this issue when using a different framework.
Clear the DerivedData solve this issue.
https://docs.sentiance.com/sdk/troubleshooting/ios/bundle-format-unrecognized-invalid-or-unsuitable
Go to Xcode menu bar and select File > Project Settings (or Workspace Settings).
Under Per-User Workspace Settings, find the shortcut to DerivedData folder and open it via Finder.
Remove the entire content of the folder and empty the Trash.
Restart Xcode.
In Xcode 11.*
Target -> General -> Linked Frameworks and Libraries
change related framework with option "Do Not Embed"
Else Check on the :
Target -> Build Phase -> Link Binary With Libraries
Check status with Required/Optional - try it with required first.
I downloaded Xcode 6 GM and submitted two Swift apps to the app store today. Both passed all pre-upload verification and all the other stuff they had to pass and were successfully submitted. But then I got two emails from Apple... one for each program and they both said this:
Dear developer,
We have discovered one or more issues with your recent delivery for "xxxxxxxx" (my app name removed). Your delivery was successful, but you may wish to correct the following issues in your next delivery:
Too many symbol files - These symbols have no corresponding slice in any binary [1431D977-72BC-308F-AB71-71529F25400B.symbols, 158C72A7-98AC-3F07-B2BE-88427591B413.symbols, 44973EAC-563E-340C-B549-55A5014A68BA.symbols, 678BF06F-0C3D-3A09-BFBF-699C7079FECD.symbols, 90907DDB-0400-38ED-BB5F-0C12333C0624.symbols, 93B79949-5757-374A-97B9-825AE1A61B7D.symbols, ABA05220-4FB0-397F-AFBB-08774A82F4CA.symbols, AD70F02A-4422-32B8-8C40-CF9B45A2CCC6.symbols, B0CC9F7D-C542-3E18-A518-B28B7ECABE80.symbols, BF6A4C3B-6FA5-3C51-8404-19C2F132458D.symbols, C9D6E078-8E2A-39D9-8DEE-476916A69CEE.symbols, CF5320DF-AB31-3845-BAD5-F6E51045D396.symbols, D4967AA3-8FB0-3712-B0DE-7F4144AF8F4B.symbols, D813B314-AD37-31D4-B675-442052994495.symbols, DF42A13F-08D8-3E71-B221-FC357E0B60F5.symbols, F5F636C2-F0E0-3CA7-8F7D-C49A36CD5C65.symbols]
After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.
Regards,
The App Store team
I'm going to guess that really has nothing to do with me or my apps... and it is just a quirk of day one Swift app submissions? Both apps are still sitting in "Waiting for approval" mode. I certainly can't think of anything I could change to make what they said go away! Anyone else submit a Swift app yet and get that response? Think I should just ignore it and wait to see what happens?
This happens if you are including debug information of your libraries with the project archive but are not including binaries.
Open the Organizer window in Xcode
Right-click on an archive that had this issue and select "Show in Finder".
Right-click on the archive file and select "Show Package Contents"
In the "dSYMs" folder you will see several files. If you run the dwarfdump console command on these files you will get a list of UUID strings:
dwarfdump -u MyFile.dSYM
I'm sure you will find some matching UUIDs from Apple's email.
To avoid this warning you need to include with your archive only the dSYM files of your application and not the libraries. For this you need to change the build configuration of the libraries to not generate a dSYM file. Just search for "debug information format" in configuration and change it from DWARF with dSYM File to DWARF only.
For example, in the screenshot below you will find the Stripe iOS framework.
If you encountered this problem while using CocoaPods, add this to your Podfile:
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['DEBUG_INFORMATION_FORMAT'] = 'dwarf'
end
end
end
It will set Debug Information Format to DWARF only for all your Pod targets only (not the main app target)
If you are using CocoaPods and your app is set to use arm64 only (i.e. there is only arm64 in your project's info.plist)
<key>UIRequiredDeviceCapabilities</key>
<array>
<string>arm64</string>
</array>
then you can try adding the following script in your Podfile to solve this issue.
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['ENABLE_BITCODE'] = 'NO'
config.build_settings['ARCHS'] = 'arm64'
end
end
end
AND
set all your projects' targets (not the targets in Pods) to arm64 only
CocoaPods Github issue reference
I have this issue due to the project has valid architecture arm64 where the CocoaPods targets have valid architecture arm64, armv7 and armv7s.
To check which target has which valid architecture follow following steps
In Xcode -> Window -> Organizer
Select the archive and Reveal in Finder
On .xcarchive file, Show package content
Open terminal and give path of dSYMs folder.
Enter command dwarfdump --uuid * and it will show list of UUIDs with valid architectures.
The UUID will match with Apple's warning email
The main project and cocoa pods target suppose to have same valid architecture. By doing this, it will solve the issue.
Worked for me by enabling bitcode - it was off before
Enable Bitcode - Yes
The above helped troubleshoot, but couldn't solve. We had project at iOS 12 but pods 10 - led to a bunch of armv7 files. Updating pod to iOS 12 solved instantly.
Had the same problem fixed it by having the same "General" => "Deployment info" => "Deployment target" for all my targets.
In Xcode, look in Build Settings for “Strip Debug Symbols During Copy”
(COPY_PHASE_STRIP). When enabled, debug symbols are omitted from your
.app and placed into a .dSYM file. Otherwise your .app contains these
symbols. (By default, debug symbols are stripped from release builds
for reasons of obfuscation. You probably shouldn’t change this setting
for the release configuration.)
Make sure you check this option in project Build Settings
https://possiblemobile.com/2015/03/symbolicating-your-ios-crash-reports/
The problem for me was a line in my build.xcconfig file.
I had to remove
IPHONEOS_DEPLOYMENT_TARGET = 11.0
which was setting the project to only build for arm64 (and not arm7).
Following the steps by #miOS I could see that the pods project was building for both.
For me everything was very simple. I had the same problem and didn't know what to do for a week.
After you submit an archived application, you will see certificate for distribution in small popup window. There is a checkbox after it, which you should uncheck. After that you will submit it and get an email about symbol files. BUT it isn't problem. It's just a warning; not an error! If you uncheck that checkbox, your app will be sent correctly. I hope it may help you.
Screenshot of the checkbox and the popup:
For 2 days now I'm trying to upload a App through xcode to apple. But on every validation it shows following error:
It just came from no where. Even my older Archives that are already in the App Store show the same error when I try to validate them.
Any help would be very nice. Atm I can't push updates..
have you already tried the answer in this post?
OSStatus error -67028 When Building Ad Hoc iOS App
ensure that the Main_iPhone.storyboard file is indeed in the compiled bundle. If not, check your "copy files" build phase to ensure it is there.
So I finally got it to work:
Click on your Project and switch between your Targets. There's a Project Target and a Target with the App Icon.
On Every Targets go to Build Settings and choose your Provisioning Profile and Code Signing Certificates.
Check under Build Phases -> Copy Bundle Resources if there is a Framework in there that belongs to the Library Phase.
Before all that I updated to the newest beta of Yosemite (not needed if you don't have it) and made a clean Project. Please check all these steps!
Hope it helps others!
I Archived my app, and usually the "archive type" section says, iOS app, and you can submit directly from organiser. However, the type of this app seems to be "Generic Archive" and asks me to export in 1 of 2 ways When i click on distribute - Save built products - export as Xcode archive.
How do i submit?
The short version is you can't. It probably means that your binary has multiple targets inside it. My guess -- as this is what's happened to me -- is that you included an open source project and have it configured incorrectly. Check the "Skip install" setting of any sub-projects.
This is a issue of wrong Schemes for multiple targets, check and create new schemes for every target and then go to Build Settings>target dependencies and remove if any!
Please check below link this apple document:
http://tinyurl.com/nnxjtzq
When you make archive, It will show at xCode Organizer ,
In
xCode Organizer find three tab Click on last tab Archives
Select you app and Click on Distribution
There you will find three check box like this image
For submit appstore check first and follow next steps ..
May be help full for you ...
Okay, the problem turns out to be that my cocos2d libraries were included in the build settings. This was solved by
cocos2dLibraries > Build Settings > Skip Install
and making the value "Yes".
When trying to archive an app for an Ad Hoc release, I am getting the following warning:
iPhone/iPod Touch: application executable contains unsupported architecture(s): armv7s (-19031)
I am really not sure why this is happening for two reasons:
The only non-foundation framework I am using is the Facebook SDK, which is the latest version
I successfully archived the app last week and the only things that have changed since then are purely coding changes.
Also, I have tried archiving with and without an iPhone 5 plugged in, and I receive the error both ways.
Does anybody know how to fix this?
Quick fix is
Remove armv7s from
Project -> Build Settings -> Architecures
Updated ::
Now change Build Active Architecture in Build Settings to No to Yes.
But even this is not a pure solution to this problem.
I could archive and validate my projects by changing status of 'Build Settings -> Build Active Architecture Only' from 'No' to 'Yes'.
Same problem here today when submit my app (update) to appstore.
I clearly remember that its last version was submitted with both armv7 and armv7s set and succeeded, but now Organizer told me :
"iPhone/iPod Touch : application executable contains unsupported architecture(s): armv7s"
to remove armv7s is simple, but my app is Universal, will the armv7s-removed app run on all iOS devices (iPhone 5 for example)? when should i build with aremv7s?
Same issues here, app passed validation before, but after a quick code change, no go. Could this possibly have something to do with ipods? Seems to be a recent issue, as of yesterday.
Getting the same result as 21k. I submitted a binary with both armv7 and armv7s to the App Store last week, and it passed validation as well as the review. Now I tried submitting an update to the same app with the exact same project settings (other than the usual version number bump), and it fails validation.
In fact, I try validating the archived app from last week and now get the same error. So something must have changed on the App Store's side.
Go to Project ---> Build Settings and scroll down to the Architecture setting.
You will probably see the value $(ARCHS_STANDARD_32_BIT) listed under Architecture.
If so, double-click $(ARCHS_STANDARD_32_BIT), select it, and click the minus button to get rid of it. Then click the plus button and write armv7 and press Enter.
You have now removed armv7s, which was unsupported. Try it again and things should be good.
Removes armv7s architecture from menu Build settings > Architectures. At that point must appear valid architectural amrv7s and amrv7. Removes only finished in s. If the menu doesn't appears, notice that it is set to "All" and "Combined" in the search bar.