A valid provisioning profile for this executable was not found IOS 12 but launches still in IOS 11, xcode 10 - xcode

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.

Related

React Native with Xcode 13 throws: Error Analyzing App Version

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.

Xcode 12 update breaks Pods and Products

I just updated Xcode to version 12. When I open up a previously working project I now get an error No such module 'GRDB'. I have tried deintegrating and reinstalling the Pods, cleaning the build folder, and restarting Xcode. Additionally, when I look under my Pods the Products and Frameworks are colored red (view picture).
One observation: This issue only appears when building for the Simulator, building for the device works fine.
I go to build settings and find the problem my Architectures is arm64:
and I change to Standard architectures for every target in my Pods project :
I came across a "solution". I am not sure why this fixed the problem but when I was running into build issues, I was building for an iOS simulator. If I change the build to "Any iOS Device (arm64)" or to my iPhone then the issue goes away.

Missing entitlement - 'UIBackgroundModes' value 'workout-processing' without the required entitlement 'com.apple.developer.healthkit'

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.

XCode 3 - core compile errors with clean installation and iPhone 4 SDK

This is a copy of another question from AskDifferent, since I'm being adviced to put this question here instead.
This has been asked once elsewhere but nobody could give the guy an answer... and I Google seem to only know that single occurrence of the problem!
So I'm the second guy in history to experience this and my problem is:
I'm running XCode 3.2.3 on Snow Leopard 10.6.4 (I think, it's the minimal required OS version for this XCode version) with iOS SDK 4.0.2
I create a new empty Cordoba (PhoneGap) project
I set up my Base SDK in Project Settings to iPhone Simulator 4.0 per instructions on PhoneGap's website
I don't change any other setting at all
when I hit "Build and Run" button, XCode starts compilation and finished with 3 errors and 10 warnings
Now, I don't mind those warning, but I cannot successfully compile because of those 3 errors now. No idea how to fix this, I'm totally new to PhoneGap or Mac OS for that matter.
The errors I get are:
/Users/[name]/Documents/CordovaLib/Classes/CDVLocation.m:123:32 /Users/[name]/Documents/CordovaLib/Classes/CDVLocation.m:123:32: error: use of undeclared identifier 'kCLAuthorizationStatusAuthorized'
/Users/[name]/Documents/CordovaLib/Classes/CDVCapture.m:783:70 /Users/[name]/Documents/CordovaLib/Classes/CDVCapture.m:783:70: error: use of undeclared identifier 'NSEC_PER_MSEC'
Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/clang failed with exit code 1
I would appreciate any advice from you guys, as I'm completely at a dead-end here.
CLAuthorizationStatus, and thus kCLAuthorizationStatusAuthorized are only available in 4.2 and later.
Check this for more info: https://developer.apple.com/library/ios/#documentation/CoreLocation/Reference/CLLocationManager_Class/CLLocationManager/CLLocationManager.html#//apple_ref/c/econst/kCLAuthorizationStatusAuthorized
As to your other error, google pulls up this: How to resolve Phonegap error while Building the app

Getting "Missing SDK in target picChoice: iphoneos4.0" error when building a test release of my app in Xcode 4, pvw 5

I have opened a functioning Xcode 3x project in Xcode 4.0 pvw 5 and am getting the following error whei I try to build a debug version of the app: "Missing SDK in target picChoice: iphoneos4.0"
I am trying to find where and how to remedy this, and I am coming up with bupkus.
I apologize if this is not very clear, but I am rather flummoxed by Xcode 4 so far....
Your problem was probably that Xcode 4 only came with SDK 4.2, and the project pointed to 4.0.
It's pretty common!
The solution is to go to the project info | Build settings | Base SDK and setting it to "Latest iOS" so that you don't have to touch it for future updates.
When you close the window, you'll have to switch config from debug to release or distribution and back so that it updates and Xcode removes the "Missing SDK" problem.
I just wanted to put the full answer up here to help others who have the same problem ;)
Ok...I resolved this, but I did not properly track HOW I resolved it....
I think my Target's Base SDK was not set, and I set it to: Latest iOS (iOS 4.2)....
I think that's how I did it....
But, now it builds with no errors and loads onto my iPhone as expected.
That is exactly what you needed to do. Xcode 4 introduced the Latest iOS. If you wish to test the app for older versions, select target > summary > deployment target and set that to an older iOS version and then in simulator you will see more version options available to you.

Resources