I used the Apple MigrationAssistant to migrate to a new machine, and now MonoTouch won't launch my app in the simulator because it says my license is not valid. Following instructions in other posts here, I removed my license file and re-ran the setup, but that just told me that everything was installed and launched the app with the same problem. So, I completely removed MonoDevelop, and re-ran the setup. It dutifully downloaded MonoDevelop and installed it, but never gave me a chance to activate, so I'm still stuck.
http://support.xamarin.com/
Look at the box that says "Product Download and Activation Self Service" - login there to re-download the full licensed version of MT. There are also some tools to deal with reactivating licenses.
If all else fails, contact support directly.
Related
When trying to test my app on my device iPhone, I get the following error, I think it's something about registering my device.
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets(3,3):
Error MSB6006: "codesign" exited with code 1. (MSB6006)
(multifacturacion.iOS)
The strange thing is that this same device in another mac with xamarin if it works and with the same project.
If someone can help me with this, I have several days looking for a solution.
This went away for me after I cleaned the solution in Visual Studio.
(yes this is a complete answer, there are no citations, this is just what I did to fix it).
Open the info.plist and check "Automatic Provisioning".
Thing is, I am having this error regularily. I am working with a local developer certificate created on my Mac using a free Apple Id, but without a paid Apple Developer Membership. I am using a Windows based devloper workstation and program in Visual Studio 2019 with Xamarin.Forms 4.0. To get local deployment working again, I need to visit the general settings on my iPhone and remove my trusted account from the list of developer apps under device management which basically not only removes the account but also the app from the device.
Then I need to remove all occurances of the corresponding certificate on my Mac within the Keychain Utility and even the mobileprovision file on my harddrive located somewhere beneath my user directory.
Now I have to Start XCode on my Mac, open the project, I am working on and have it automatically "repair" the signing certificate which basically creates a new one and registers it in the Keychain. The moment I run the app from XCode, I need to always allow keychain access and on my iPhone I can see the account appear in the general settings again which I have to manually trust... again.
THEN I can open the corresponding project in my Visual Studio on my Windows Developer Workstation, rebuild and deploy the app and get no errors.
Without being able to say why, it could happen even the next time I try to build and deploy the app, that this error happens again... this is very (!) inconvenient and I didn't find any real solution for it yet...
remove your certificates from keychains and add again, close Info.plist open and fill de information on bundle singing option, that works for me, remember link your device with you provisioning.
The answer of Mephisztoe worked for me, except that I am working on Windows and you find the scheme-property in the project-settings and not in the plist-file.
Furthermore be sure that you installed fastlane (just open Extras > Options > Xamarin > Apple-Accounts and click on "install fastlane") and added your Apple-ID there.
I also deleted the certificate with the keychain-utility. That's why I had to reenter my password on the mac as I clicked on build on my windows machine.
With these steps done I can finally work again...
If the certificate of Apple developer is expired, you can get the error like "codesign", so you need to create a new certificate in Apple Developer site (https://developer.apple.com/account/), then download & install to your computer.
I have been struggling with the same issue for several days, the error came only when I tried to publish the app from my Windows VS 2019. It had no further details of why it was behaving like this.
What I changed was:
Created New Publishing Profile & Certificates
Instead of selecting Release in Configuration as suggested in this Microsoft article, I selected AppStore from the configuration.
Tried to recreate the archive and it was completed successfully.
Now when I tried to publish it, I encountered few error messages, I fixed them and submitted the app again. It worked fine.
For me, the issue was that there was a popup asking for a password on the network-attached Mac. I had to VNC into it and enter the password.
For some reason the first time I did this (and chose "always allow"), it failed again with this error, but the second time I ran it succeeded.
You'll want to make sure to have an app-specific password ready if you haven't already generated one. I have no idea why, but it prompts you for one in VS.
I am working with the infrastructure team on deploying a Windows 10 Universal app and running into some roadblocks. They are currently requesting a release version application that does not require a developer license to install. They are using SCCM, a tool that I am not familiar with, and are only being presented with OS requirements of Windows 10 Mobile (not Windows 10 (x86), (x64)) and are on hold until I solve the developer license issue.
Here is what I have done:
Create appx bundle via Visual Studio 2015 Professional
I chose that it will NOT be uploaded to the store
Used x86 and x64 in release mode for the configuration
License used from a domain CA for code signing and appears to work
Enabled "Allow all trusted apps to install" in local GP editor (my dev device)
Enabled sideloading in settings/update & security/for developers
When running the Powershell script, I am greeted with "Before installing this app, you need to do the following: - Acquire a developer license" and then it does some administrator prompting and cannot acquire a developer license.
If I put the device in developer mode, the script runs flawlessly and the application runs as expected.
Am I missing something that is causing me to require a developer license? Does it have anything to do with the package folder ending in _Test? It is the only output that it creates.
If I can provide any additional information, let me know. Thank you!
OK... I finally figured it out. It was nothing to do with the configuration or the app packaging. It was the Visual Studio 2015 generated PowerShell script that was requiring the developer license (Developer Mode). If I simply ran my own Add-AppxPackage PathToAppxBundle in PowerShell, it installed without certificate or developer prompt in Sideload mode. Note that the certificate is already installed via group policy in my case.
Visual Studio 2012 Update 4 install fails with the below error message, this happens with both the online installer and the ISO, the environment is Windows 7 Enterprise x64 SP1
To solve this problem, do the following before running the update. But if it's already too late, then uninstall the update, then repair the VS2012 install from Add/Remove Programs and follow the below steps (you may need to reboot your computer a few times). More info can be found on this blog (yes blog is for Update 3, but also applies to Update 4)
Download the ISO then run extract the contents and navigate to
"...\packages\WinACK\", and run the below msp patches
Windows App Certification Kit x64-x86_en-us.msp
Windows App Certification Kit Native Components-x64_en-us.msp
Run the update exe "VS2012.4.exe"
Note that this is what worked for me. Would love to hear what others have done to get it to work and share the knowledge especially because I had to struggle because the info was out there in bits and pieces and mostly related to older updates.
I've had other errors relating to the Presentation Framework and the solution for me to was log out of my Domain admin account and log into Windows as a local admin account before installing the update. Not sure if this will work for you too or not, but thought I would mention it.
I recently purchased a license for Telerik JustMock. The Telerik Control Panel shows JustMock under my list of Purchased products. When I attempt to run my tests in Visual Studio's Test Explorer with the JustMock Visual Studio extension enabled I receive an exception saying:
Telerik.JustMockExpiredException : This version of JustMock has expired!
I have uninstalled all the Telerik Visual Studio extensions, uninstalled everything Telerik via Windows Programs/Features, then re-installed the control panel and then JustMock yet the problem persists. Of note, when I re-installed the control panel it remembered my username/password so I'm guessing there is a configuration file somewhere caching my information incorrectly.
A possible root cause of this problem is that I was trialing JustMock under my personal email address but it was purchased by my company and assigned to my work email address. I am currently logging into the control panel with my work address and see no other place to change that.
The same problem occurs when I run nunit.exe via JustMockRunner.exe.
Full disclosure: I work for Telerik.
Please follow meilke's comment.
Nevertheless there are two options you can try:
As the license is developer based, it's important what email you use for downloading the licensed version. You should use the email that is assigned as licensed developer when downloading JustMock. I guess you've received similar answer from the sales support team.
The second option can be if you have used the JustMock trial version and you have included a trial Telerik.JustMock.dll somewhere in your source-control system. Hence despite installing the licensed version, your tests run with the trial.
Hope this helps.
I am trying to install Remote Tools on a Surface RT running Windows 8.1 preview. I downloaded update 2 of remote tools from Microsoft's site and when I try to run it I get the error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
This is confusing because I downloaded the file directly from MS website and when I look at the .exe properties it says digital signatures by Microsoft Corporation.
Any insight would be greatly appreciated.
Thanks!
Update: It seems like my Microsoft Root Authority certificate is "not valid for the selected purposes" I've tried exporting a "good" certificate from another machine and importing it into the Surface machine but it still gives the same issue.
This is because your downloading the 2012 tools. You can download the 2013 preview tools here at the following link! (Be sure to choose ARM)
http://www.microsoft.com/en-us/download/details.aspx?id=40781
Would have been nice if Microsoft had given us a heads up.
Also, when I go to the 2013 download on my Surface RT running 8.1 preview, and I click on Download, no matter which option I pick (x86, x64, or ARM) it downloads the x86 version, which obviously won't work. I had to download it on a PC and copy it over using a USB drive.
This problem exists on the released version of 8.1 too.
If you previously had the vs2012 tools installed, they appear to be uninstalled during the upgrade.
Attempting to reinstall gives the above error.
That means, it's now impossible to connect to the 8.1 Surface RT from VS2012 Pro to debug an 8.0 app running on 8.1. Instead, you need to connect with the VS2013 tools and remote debugger.
For anyone who is just trying to test their App updates a surface device running Windows 8.1 RTM, I have at least found a workaround.
You can manually deploy your package to your device by coping the package content to a USB memory stick and running a already defined powershell deployment script.
Basically you need to run the normal package creation process you would do to deploy to the app store to create a package, then copy the contents of the package folder (Not the compress package itself) to your USB stick. There should be a file named Add-AppDevPackage.ps1 in this folder.
Open your USB device from your Surface RT system, right click the Add-AppDevPackage.ps1 file and select "Run with powershell". You will receive several confirmation prompts at the command line and a popup window prompting you to run with admin privileges.
This is by no means a convenient or speedy process but it worked for my purposes.
This link has more detailed information on manually deploying your app package.