Hoping for some assistance. I have a Xamarin iOS project (Windows) which I'm trying to submit to TestFlight and getting the following error:
ERROR ITMS-90700: "Incorrect Platform. You included arm64 executable “iQ.Mobile.Safety.iOS.app/iQ.Mobile.Safety.iOS” in your iOS bundle. Only iOS executables can be included."
I have gone through the dependencies in Visual Studio and marked them all as x64 but I still get the same error.
Help appreciated.
I wasn't able to share the picture through the comments. But when you open your binary in Xcode, does changing the Architecture to Arm64 fix the problem?
Related
In Xcode12 beta4 or beta5, I encounter a failure in my project.
I can run the Project on my device, but it is not running in the simulator.
I get the failure message:
ld: in /libwebrtc.a(dequantizemmx.o), building for iOS Simulator, but linking in object file built for free standing, file 'libwebrtc.a' for architecture x8664.
So does anyone know what settings should be adjusted in Xcode 12.4?
Response from Apple on similar issue.
You’ll need a few changes to support the new Xcode.
Package your framework using XCFrameworks.
Don’t install your SDK into the iOS SDK. Your users should drag drop the XCFramework into their project.
I've just added a new RichNotification Extension to my project.
Now I've got "myApp" target and two targets for: "RichNotification" and "RichNotificationContent"
When I archive the main target for the App Store works fine but I get this error while trying to upload to the App Store:
ERROR ITMS-90700: "Incorrect Platform. You included the iOS arm64
executable
“myAPP.app/PlugIns/myAPPRichNotifications.appex/myAPPRichNotifications”
in your iOS bundle. Only iOS executables can be included."
Is there any special procedure to archive an app with multiple extensions / targets? Special build config?
Couldn't really find any information, I'm probably searching with the wrong terms.
I had the same problem. I just use pod update, rebuild project on another mac, and reupload build to AppStore and issue gone
We had this error when using Transporter to upload the application from a non-developer computer. The solution was installing Xcode on that Mac. After that the upload process went through without issues.
Thanks to #Mikhailo Karpenko
I solved the issue by re-installing pods
And I had to remove the setting 'ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES' from the project settings as this is set by pod iteself
I had a similar issue where uploading an app produced the same ITMS-90700 error but it was related to a watch app executable. In the end it turned out that I had an old watchOS target in the build settings which was causing the error.
Not completely related to this question, but this is the only question I found on SO that referenced error ITMS-90700. Hopefully it helps someone.
I solved this issue by making sure all of the build targets in my project were built for the same iOS Deployment Target.
We added an extension in our app and it defaulted this value to iOS 12 whereas the rest of our app was configured for iOS 10. Regardless of the valid architectures field in the build settings, the extension was only being built with 64-bit support, but the rest was being built with both 32-bit and 64-bit.
After making this change, I ran lipo -archs on the extension to validate that it was built for both arm64 and armv7.
I have been developing a mobile app using Delphi XE8 and testing under the platform:
IOS Device - 32 Bit - iPhoneOS 8.4.
Now that I am happy with the app I am trying to deploy it to the app store. From what I understand, in order to do this, I have to submit a 64 bit Build. Therefore, I am trying to build my app using:
IOS Device - 64 bit - iPhoneOS 9.0
When I compile or Build the project in 64 bit I get the error message:
[DCC Error] E2597 ld: warning: directory not found for option '-FC:\Users\leonard\Documents\Embarcadero\Studio\SDKs\iPhoneOS9.0.sdk\System\Library\PrivateFrameworks'
ld: file not found: /usr/lib/libiconv.dylib
I have tried deleting and re-adding the SDK and selecting the 'Update Local File Cache' for iPhoneOS 9.0.
The closest thing I could find on google was this link:
XE4 Deployment error
But that did not help. There were other suggestions that dealt with xcode but they do not look like they apply to my situation either.
It would be appreciated if someone can offer a suggestion as to why I am getting this error and how I can fix it?
Well I didn't discover why my PrivateFrameworks directory was missing. But I decided to move my app to Delphi 10 Seattle. After installing Seattle and configuring my application platforms, I then had the required directories. I was able to build my application in 64 bit and got an .ipa file in preperation for submission to the App store.
The problem appears because of changes in the iOS SDK 9. There is workaround for building iOS 32-bit applications for iOS 9 with XE7 and XE8 suggested in blog of Embarcadero Community. But I am not sure if this workaround suitable for 64 bit..
My MAC OS version is 10.8.5 and xcode version is Version 5.1.1 (5B1008)
I have an IOS app which i was trying to update to app store. In the usual process which i used to do everytime, now i have cleaned build, created an Archive(Product>Archeive) and tried to validate it by clicking on Validate button after archieve build has been created, but i was facing the below error
My build settings are
So whats the problem here ? and how to avoid this error ?
I read somewhere on google to update the valid Architecture with arm64, and when i added arm64 to valid architecture setting and when tried to create a build(tried to create an archieve) then i was getting a lot of errors and build/code was not working
So can anyone please take me through steps to fix the above issue ?
After updating Valid Architecture setting to below
and when tried to create an archive the build failed and the errors are
Edit
Also the framework in which my app was built on Cordova framework
You have no option but to add arm64 to Valid architectures. So removing it to avoid errors is not a solution.
Instead, add arm64 back to your valid architectures and try to solve errors.
If you cant solve yourself, search for solutions on this site, or ask new question, people will help you out..
In short, SOLUTION :
Add arm64 to your valid architectures and solve arising errors.
Type "arm64" in the Valid Architectures
As of Feb 1, 2015 apple allows the app to be submitted with arm64 support.
You have no option to submit your app without adding arm64 support.
By adding support for arm64 support, it will cause errors if you have used frameworks which do not support arm64 support.
You will have to update your frameworks which do not support arm64.
Also, update your architectures from Build Settings to Standard architectures(armv7,arm64) - $(ARCHS_STANDARD).
Once done, then and the only you will be able to archive successfully and submit the app to app Store.
Hope it helps you.
In order to support arm64 with Cordova follow this post xcode 5.1: libCordova.a architecture problems
Otherwise #Mayur Deshmukh and others are right! You have no choice but supporting arm64 now.
Looking at the errors you have received, it would appear that the cordova framework you have used does not yet support arm64.
I experienced the same problem with a different framework and was able to solve it by contacting the creator of the framework, i would suggest doing this to see if there is an updated framework available.
Has anyone else received that warning while uploading the application to App Store?
Everything was going well before today, but when I started to upload the application I began getting the below warning, telling me to update the architecture to support 64-bit.
When I performed the function asked of me, I began getting a lot of errors. If I upload it with a warning will it affect my other code?
We build the app in unity pro 4.5.5 and exported the project to Xcode with iOS 7.0 as build target. Now when we are changing it to standard architecture which consist of arm64 we get lot of errors stating that the unity libraries are not supporting arm64 architecture.
Please let me know if anybody is facing a similar warning while uploading the ipa and any preferable solutions or suggestions are welcomed. Thanks in advance for help.
Unity 4.6 latest version is fixing the armv64. So from now if you create a project in unity for iOS please update it to 4.6 and then create. Cheers.