I'm having problems uploading my app version since I upgraded Xcode to 13.3.1
The compilation succeeds as always, but when I'm doing the process of uploading and distributing to the App Store I get this screen with no explanation:
I have cleared the cache, clean the build, and changed the node version from 14 to 16 and I haven't been able to make it work.
Thanks
After many attempts, I solved this by setting the Team to NONE and then back to the signing team.
This is under the Signing tab.
Related
I am currently unable to archive my app using Xcode 11 GM, seed 1 and 2.
I want to upload my new iOS 13 build to App Store Connect but am unable to because of this issue.
The archive always gets stuck on task number 911 when archiving, this is when it says it is building Realm or Charts. The same happens when building using fastlane gym except it gets stuck much earlier when compiling nanopb-vers.m
So far I have tried suggestions from people facing a similar issue with no luck:
Changing compilation mode
Changing optimisation level
Adding a custom building setting (LD_VERIFY_BITCODE = NO)
Using the legacy build system
Using fastlane
Removing armv7 from supported architectures
Setting debug information format to just DWARF
Does anybody know how to fix this issue?
I have released my app a couple of times and had the process under control until most recently when I updated from XCode 9 to XCode 10 due to a 3rd party lib requirement.
Everything seems fine when I compile and run on the emulator; but, when I come to the "Validate" (Archive) the app prior to uploading to the app store I am getting an error.
My Setup:
MacOS 10.14.2 (Mojave)
Using XCode 10.1 (10B61)
Error message:
Missing entitlement. watchOS extension
'XXX.app/Watch/aw-xxx.app/PlugIns/aw-xxx Extension.appex' uses
'UIBackgroundModes' value 'workout-processing' without the required
entitlement 'com.apple.developer.healthkit' signed into the bundle.
Watch Extension Capabilities:
The app is built using cordova-8.1.1 and cordova-ios-4.5.5
cordova build ios --buildFlag='-UseModernBuildSystem=0'
In addition to that, the project on XCode 10 has been set to 'Legacy Build System' on File -> Project Settings.
Lastly, the 'aw-xxx Extension.entitlements' has the 'HealthKit' key value set to 'YES' under the 'aw-xxx Extension' folder as one could expect.
Any help or pointers would be much appreciated.
I'm happy to provide more info, logs, etc as well, thanks!
After following the comment below I managed to get my app to validate once again on XCode 10:
Hi #guikeller Just wondering if it is related. I had similar issue while doing a ionic cordova app release. I figured the
com.apple.developer.healthkit
is missing in my platforms/ios/myApp/Entitlements-Release.plist. It does exist in Entitlements-Debug.plist. All I did is copied the key from the debug file to release and app store accepted it.
Source: https://github.com/apache/cordova-ios/issues/475#issuecomment-450174628
In addition to that, I was also able to submit my app into the app store.
this is driving me insane. I updated my device to IOS 12, and my xcode to v10. when I try to test it, it gives me the error stated in the heading.
then I inserted another device that uses ios 11 still, and in that device it launches with no problems.
Image of error
please help guys. I have already tried deleting the everything from provisional Profiles and downloading manual profiles from xcode, it still gives me this error on ios 12.
I was having a similar issue, and it started when I updated my Xcode 9 to Xcode 10.
The same error:
A valid provisioning profile for this executable was not found.
However, it fails to build on a device that runs on iOS 11. I can build on a simulator or even archive and deploy to AppStore, no matter the iOS version I set on the deployment target.
I was reading the update notes for the Xcode 10 and noticed the following:
Build Performance
New build system improves performance and is enabled by default for all projects
I was ready to downgrade my Xcode, but as a last resort I went to "File/Project Settings" and selected "Legacy Build System" from the dropdown.
Now it builds with no issues.
And yes, I'm using the Ionic3 framework too.
I have an issue that has come up before however in this situation I have two development machines and the code build and runs on one machine but not on the other.
I have a MBP and a Mac Pro, the code is in git and once I have built on one machine and committed and pushed to git when the code is fetched on the other machine I receive the error message WatchKit App won't compile: “error: WatchKit Extension doesn't contain any WatchKit apps”.
I have checked bundle identifiers and they all look correct which makes sense as it builds on one machine.
I also downloaded a sample app from Xamarin.com, the WatchTables demo. The bundle identifiers are correct but I am receiving the same build error with that solution.
Any thoughts, I have checked the version of Mono and other frameworks on both machines, Xcode and VSfM are the same version and up to date. Any ideas would be helpful.
After downloading additional updates on the machine that was failing when I went to install and restart an error occurred and VSfM would no longer start. So I reinstalled VSfM again, this allowed it to start and I was able to apply the updates.
Once I started the IDE again I was then able to build the solutions.
I would seem that something had become corrupt with VSfM and until the failure of the updates broke the IDE this wasn't getting sorted.
All is good now.
Today I got the memo from Apple as probably every other Apple developer about potentially infected Xcode installations. (https://developer.apple.com/news/?id=09222015a)
I followed the instructions and tried to validate my Xcode app using the command mentioned. (spctl --assess --verbose /Applications/Xcode.app) The program ran for a while and exited with a "/Applications/Xcode.app: a sealed resource is missing or invalid" message.
The article says "Any result other than ‘accepted’ or any source other than ‘Mac App Store’, ‘Apple System’ or ‘Apple’ indicates that the application signature is not valid for Xcode." However, I'm actually pretty sure my Xcode copy is legitimate (downloaded and updated via App Store with Gatekeeper enabled) so I thought maybe there could be another problem preventing it to validate as it should.
Do you have any ideas what this error message actually means? Do you think I need to reinstall Xcode just in case?
Thanks in advance for your help.
The false positive validation issue appears to be caused by containing previous iOS SDKs in order to be backwards compatible.
A clean install will completely wipe the SDK directories. When you run the validation test after a clean install it will pass. Once you copy previous iOS versions, which, for us, is iOS 8 for iPhone, the validation will fail.
This scenario was tested after updating to XCode 7.0.1 (7A1001) which was released earlier this afternoon.
In order to avoid a clean install, you can temporarily remove the previous SDK version from their respective location, and run the validation. Then, once the validation passes, copy the files back where they belong.
I was getting the same message "a sealed resource is missing or invalid". However i was able to rectify the issue by going into the App Store and downloading the latest version of Xcode - Version 7.0 (7A220), and this seems to have rectified the issue.
Although i did first try updating Xcode through the updates section on the App Store, but for some reason this didn't work. So i would recommend going into the App Store > Search for Xcode > Then install the latest version available to you.
Depending upon gatekeeper settings.please check gatekeeper settings to allow anywhere and revalidate Xcode.