I'm currently having problems building a release-version for Android.
The keystore file/password/alias are correct and I've set "Generate Builds" to release, but I'm still getting the following notification:
Warning: Building for Android without a valid certificate will produce a temporary certificate that cannot be used for redistribution of applications. Its very easy and free to create an Android certificate, see: http://www.codenameone.com/signing.html
I have successfully used this certificate before, about two years ago...
I'm using NetBeans 8.1 with the CN1-plugin 3.3.2.
Is there a way to fix this?
That means Codename One didn't find the file or the password/alias are incorrect.
You can use the keytool to verify this:
keytool -list -v -keystore full_path_to_keystore -alias myalias
Make sure the alias/path are identical to what you see in NetBeans.
Related
I have set up a code-server on a remote machine and when browsing the extensions, the C/C++-Extension from Microsoft is not available.
It is also not possible to install it via the CLI:
pi#raspberrypi:~ $ code-server --install-extension ms-vscode.cpptools
Installing extensions...
Extension 'ms-vscode.cpptools' not found.
Make sure you use the full extension ID, including the publisher, e.g.: ms-dotnettools.csharp
Failed Installing Extensions: ms-vscode.cpptools
Is this extension just not available, or is it, because the server is not accessible via HTTPS (I couldn't get the certification to work)
First you have to fullfill prerequisites: https://code.visualstudio.com/docs/cpp/config-linux
Then download the extension:
https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools
-> Click on version history and choose for your linux architecture.
Install extension with: code-server --install-extension ms-vscode.cpptools-1.10.3#linux-x64.vsix
I cannot connect to my nuget feed by visual studio 2017 enterprise. I'm owner of nuget feed. When I use browser in VS i can connect but when i use nuget source i get 401 unauthorized exception.
enter image description here
Does your organization connect to AAD? Do you use a Work account or Microsoft account?
If your organization doesn’t connect to AAD, and you use a work account, you’ll meet this error. If you use a MSA account, you’ll find you can restore the packages without issue.
It’s a known issue, and has been fixed in VS 2019 Preview2 (I have verified it’s working in VS2019 Preview2). Currently, the workaround for previous versions of VS is generating a PAT and register the Nuget feed on your system with following command. I’ve tested in VS2017, after running the command below, I can restore the package with a work account:
nuget.exe sources Add -Name "FeedName" -Source "https://feedurl" -username unused -password PAT
I am learning VSTS. I have a one-line HelloWorld.cpp file in my repository and a makefile to build this cpp file.
Firstly, I created my build definition, which is like below:
secondly, I assigned the build definition to the only available Linux hosted-agent, called "Hosted Linux (Preview)":
After these I kicked off a build but it returns error:
I then checked the capabilities of the agent. It doesn't have CMake, nor does it have compiler like gcc or clang.
I checked VSTS documentation pages about build agents, but have no clue what I should do.
The Hosted agent and Hosted VS2017 agent have CMake installed, you can use Hosted agent or Hosted VS2017 agent. You need to add the capability manually (cmake and yes), check Build:CMake Q&A.
On the other hand, regarding CMake in Hosted Linux agent, I submit a feedback here: CMake in Hosted Linux agent.
Unable to deploy my app as I started getting below error since today morning.
I have tried gcloud info --run-diagnostics and gcloud components reinstall without much help.
I tried to deploy it using the old Google App Engine Launcher for Windows but faced the same error.
Earlier it worked till yesterday night (IST) using gcloud. Please help!
I am on latest gcloud sdk and have updated all its components. I use Win10. I tried rebooting my laptop as well.
C:\gaurav\coding\python\myapp\myapp\dist>gcloud app deploy --project=myproject --version 1 --verbosity=info ./app.yaml
INFO: Refreshing access_token
ERROR: gcloud crashed (SSLHandshakeError): [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)
If you would like to report this issue, please run the following command:
gcloud feedback
To check gcloud for common problems, please run the following command:
gcloud info --run-diagnostics
C:\gaurav\coding\python\myapp\myapp\dist>
Diagnostics Output.
C:\gaurav\coding\python\myapp\myapp\dist> gcloud info --run-diagnostics
Network diagnostic detects and fixes local network connection issues.
Checking network connection...done.
ERROR: Reachability Check failed.
Cannot reach https://accounts.google.com (SSLHandshakeError)
Cannot reach https://cloudresourcemanager.googleapis.com/v1beta1/projects (SSLHandshakeError)
Cannot reach https://www.googleapis.com/auth/cloud-platform (SSLHandshakeError)
Network connection problems may be due to proxy or firewall settings.
Do you have a network proxy you would like to set in gcloud (Y/n)? n
ERROR: Network diagnostic (0/1 checks) failed.
C:\gaurav\coding\python\myapp\myapp\dist>
Although gcloud info --run-diagnostics complains that the three URLs are not reachable. I am able to open them from web browser.
I found that when using Fiddler (for viewing network traffic) and have decrypting https traffic enabled, then I received the SSLHandshakeError.
Stopping the tool (or choosing not to decrypt https traffic) and then running the gcloud resulted in success.
According to the comments, also a problem with other web debugging proxies such as Charles.
A problem in recent GAE and GCloud SDK versions is the presence of invalid SSH certificates, see, for example, Google App Engine SSL Certificate Error and issue 38338974.
You could try to use my suggested solution in the above-mentioned post and replace your SDK's certificate file with a valid one (will have to locate a good one for the gcloud SDK, my answer was for the GAE SDK).
You might also be able to use the gcloud config command to set the core custom_ca_certs_file configurable property to point to a file with up to date certificates, if you have one. I didn't try it, YMMV.
Upgrading to Python 2.7.9 on MacOS High Sierra solved the issue for me.
I had this issue upon install of the google cloud SDK on MacOS Mojave. I am not behind a corporate proxy, and all the answers on the web seemed to indicate that this was the issue. I noticed in the install.sh script that it takes an environment variable CLOUDSDK_PYTHON for the python executable. So, I fixed this by exporting the path to my python 3 executable.
In my case:
export CLOUDSDK_PYTHON=/Library/Frameworks/Python.framework/Versions/3.6/bin/python3.6
The install worked as expected after this.
On MacOS Catalina, the solution was to completely uninstall gcloud and reinstall it.
I had the same issue, downloaded the root/intermediate cert from one of the google url you get when you run the command: gcloud info --run-diagnostics and append to the cacerts.txt file that is being used. In my case it was the following one: google-cloud-sdk/lib/third_party/httplib2/python2/httplib2/cacerts.txt
For me it was a conflict in the python versions. gcloud was calling a different version. The solution was to set CLOUDSDK_PYTHON to point to the correct python (python2 in this case).
I tried to deploy gcloud and I was getting this error. Here is how I fixed it:
Access to Google cloud using Firefox
Download certificate. pem file and chain file
Append them on cert.pem located at:
C:\Program Files\google-cloud-sdk\lib\third_party\certifi\cert.pem
(using this you are creating custom CA cert file based on your proxy)
Update cert file as mentioned here: https://cloud.google.com/sdk/gcloud/reference/config/set
(Absolute path to a custom CA cert file.)
Make sure you have cert.pem at the end of path.
I fixed the problem by installing gcloud from apt-get. The guide is at this link
I used Windows Explorer to "Install Certificate" for my certificate on my Windows 7 build machine. But I could not sign a file:
> signtool sign /a exefile
SignTool Error: No certificates were found that met all the given criteria.
Thinking that signtool needed the p12 file but wasn't saying anything, I then used Windows Explorer in an attempt to "Install PFX" but got an error from the Certificate Import Wizard saying "The Specified file is empty.".
Do I really have to do this whole "obtain a signing certificate" process all over again for each build machine platform type (macOS, Windows, Linux)?
Yes, you can use the certificate so long as you correctly export the cer and p12 files from the macos host and install them correctly on the windows host. I used the macos keychain app to export the certificate two times, once to export the cer file and again to export the p12 file. The reason my first attempt failed is because the p12 I assumed was correct was not at all correct. After I exported correctly, I was able to use windows explorer to double click on the two files and install them.