I started playing around with deploying a multi-device hybrid app. today. I am not sure the exact steps I took whilst doing this, but now when I try to build for windows 8 I get the following:
Error 3 The certificate specified has expired. For more information
about renewing certificates, see
http://go.microsoft.com/fwlink/?LinkID=241478.
[D:\dev\client\source\myApp\bld\Debug\platforms\windows8\CordovaApp.jsproj]
C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets
1772
There doesn't seem to be any way to configure or renew test certificates for this type of project.
Any help would be much appreciated.
Another way to fix this issue in CPT3.0 is to replace CordovaApp_TemporaryKey.pfx under
%userprofile%\.cordova\lib\npm_cache\cordova-windows\3.6.4\package\template\CordovaApp_TemporaryKey.pfx with the latest one from here.
Once you've downloaded the file, just rename it to CordovaApp_TemporaryKey.pfx
This way you do not have to copy the certificate every time you create new project.
Due to a coding error, the Windows Cordova platform has a temporary key in it that expired on 11/11/2014. Microsoft is actively working with the community on a long term fix. To work around this issue, create a Windows Store project (WWA), take the “_TemporaryKey.pfx” from the Windows Store project, and put it in your Tools for Apache Cordova project in following location:
• CTP 1 or 2: res/cert/windows8/CordovaApp_TemporaryKey.pfx
• CTP 3: res/native/windows/CordovaApp_TemporaryKey.pfx
This post by MS Open Tech has details and a certificate that you can download.
Related
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.
As IOS release its new updates we have IOS-11 now and to support we have Xcode9.
Xcode-9 has changes its upload process of build to i-Tunes and its quite unfamiliar for us to Follow the process.
Recently i need to upload the build but the selection of certificate section is quite confusing.
I have choose my distribution certificates but i it will not allow me to proceed further
Sometimes its says : 'Profile is not manually managed.'
Sometimes its says : Profile is not Appstore certificates.
Please if anyone can guide me How to Upload build using Xcode-9
Thanks.
I think choosing Automatically manage signing, and trying to upload a build using Application Loader will solve you problem.
We are actually trying to upload our Xamarin mobile application to AppStore. Application is built using Xamarin.Forms and uses Pspdfkit for pdf viewing on Ipad. This is the only external library we are using. Project builds correctly but when we try to upload to AppStore, we are getting the following error:
Heading
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://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html Once these issues have been corrected, you can then redeliver the corrected binary
Can someone gives me the details steps to sign an external library on Xamarin Studio?
The problem you see is most certainly not caused by the PSPDFKit library but by your app itself. iOS apps must be signed using different certificates:
There's one for development
one for Enterprise distribution
one for App Store distribution
You will have to create a proper distribution certificate in order to upload to the store. This involves setting up an App ID, the certificate itself and a provisioning profile which holds everything together.
Your entry point to those certificates is Apple's developer site.
You can read more about the publishing process with regards to Xamarin specific things (it really isn't that different from using an app built with Xcode, other than the different IDE) in Xamarin's documentation.
To automate the process and make it easier to manage you might also want to have a look at a collection of tools called Fastlane.
I have upgraded to OSX Server 3.2.1 and I am trying to get my bots to work again. I have one of my projects working, but when I have a workspace that tries to build I get stuck at the following message:
Integrating (step 4 of 9)...
Building sources Please wait...
This hanged for about 10 minutes and then fails with the following error:
Bot Issue: error. Build Service Error. Issue: Terminated xcodebuild
since it produced no output for too long.
There aren't any other errors I see in the error logs. Does anyone have any ideas on how to troubleshoot this issue?
The cause of my issue was due to a bug in Xcode server 3.2.1. In the previous version, it read all of its signing certificates from the system keychain. As of 3.2.1, it has its own private hidden keychain. There are 2 workarounds for this:
Override the xcode keychain with your existing system keychain (assuming your system keychain has all of your apps signing certificates already in it)
Install Server 4.0 and Xcode 6.1. Apple has assured me that this is fixed in this version, though I have not tested this without also doing the above step. Additional information is available on the Apple forums here:
https://devforums.apple.com/message/1053902#1053902
I had the same problem, and to fix it, in the target scheme, I've changed the Build Configuration of "Run" and "Analyze" to "Release" and it worked!
My scheme has no target for test, but I have another target with test and it works fine with debug configuration.
In your OS X Server account's Keychain Access app, select your certificate's Private Key and allow access by all applications.
Get Info > Access Control > Allow all applications to access this item
Source:
http://faq.sealedabstract.com/xcodeCI/#signing-for-distribution
I have implemented cross platform application using Titanium 3.2.0 but when i try archiving the build for iOS AdHoc distribution, it does not get compiled. It keeps giving error with developer name as mentioned below - Invalid "--distribution-name" value ""
I tried building from XCode, Titanium UI and over Terminal as well but same error everywhere. I have referred https://jira.appcelerator.org/browse/TISTUD-5642 and it says that issue is fixed but i still face this issue over every machine updated to 3.2.0 or even when 3.2.0 is installed fresh.
Please help and provide information.
Regards.
Sounds like your Application IDs don't match from your project to your Provisioning Profile.
In your Tiapp.xml file, you may have and application id like com.mycompname.THISappname, but you told the Apple Provisioning Profile that your app id was called com.mycompname.OTHERappname. So they don't match. Change your Tiapp.xml file to match the what the Apple Provisioning Profile expects or creating another profile matching your application id in Titanium Studio.
this worked for me: create a new production certificate AND create a new provisioning profile with the same bundle ID. (Yes, this will work if you are updating an app that is already live). Download the cert and prov. profile and run both (double click). Now repeat step 6 and archive. This should work.