I wish I knew why it works, but here’s a fix that worked for me: Found the fix ! Click on your project > Targets > Select your target > Build Settings > Code Signing Resource Rules Path and add : $(SDKROOT)/ResourceRules.plist
Just came across this issue myself, the problem was that I had a Entitlements.plist file in the project as part of an ad hoc distribution, and its get-task-allow (ie. ‘can be debugged’) property was set to NO – setting this to YES fixed the issue and allowed the app to run from Xcode4 on the … Read more
Some things to check: Can you change to unrestricted? Set-ExecutionPolicy Unrestricted Is the group policy set? Computer Configuration\Administrative Templates\Windows Components\Windows PowerShell User Configuration\Administrative Templates\Windows Components\Windows PowerShell Also, how are you calling Script.ps1? Does this allow it to run? powershell.exe -executionpolicy bypass -file .\Script.ps1
The solution lies in the new option in Xcode 5 which says provisioning profile. Just set the project target’s provisioning profile to the right one and it’ll work.
A Quote from : iPhone Developer Program (~8MB PDF) A provisioning profile is a collection of digital entities that uniquely ties developers and devices to an authorized iPhone Development Team and enables a device to be used for testing. A Development Provisioning Profile must be installed on each device on which you wish to run … Read more
I too have been fighting this. Nothing helped until I tried the suggestion on http://devnet.jetbrains.com/thread/311971. Thanks ashish agrawal! Login your build user via the GUI and open Keychain Access. Select your signing private key, right-click, choose Get Info, change to the Access Control tab and select the “Allow all applications to access this item”.
The nice thing about Groovy is that you can freely mix Java code, and it’s pretty easy to read in a key/value file using java.util.Properties. Perhaps there’s an even easier way using idiomatic Groovy, but Java is still pretty simple. Create a keystore.properties file (in this example, in the root directory of your project next … Read more
This issue is related to Bug 1534145. SSL.com: P-384 curve / ecdsa-with-SHA256 certificates. A representative from Apple estimated 558,000 certificates to become invalidated: Bug 1533655. DigiCert: Apple: Non-compliant Serial Numbers GoDaddy, Google, Apple and Facebook (that would explain why Facebook was glitchy today) are affected. They are working on resolving the issue right now. That … Read more
I’ve finally found the solution. Edit the .csproj file for the project in question. Delete the following lines of code: <PropertyGroup> <ManifestCertificateThumbprint>………..</ManifestCertificateThumbprint> </PropertyGroup> <PropertyGroup> <ManifestKeyFile>xxxxxxxx.pfx</ManifestKeyFile> </PropertyGroup> <PropertyGroup> <GenerateManifests>true</GenerateManifests> </PropertyGroup> <PropertyGroup> <SignManifests>false</SignManifests> </PropertyGroup>
Updated Answer If you are using the following Windows versions or later: Windows Server 2012, Windows Server 2012 R2, or Windows 8.1 then MakeCert is now deprecated, and Microsoft recommends using the PowerShell Cmdlet New-SelfSignedCertificate. If you’re using an older version such as Windows 7, you’ll need to stick with MakeCert or another solution. Some … Read more