Android Studio Error Code 403: Gradle Sync Failed - java

Im starting to use Android Studio and from then, I encountered this nuisance of an error: Error:Server returned HTTP response code: 403 for URL: https://services.gradle.org/distributions/gradle-3.3-all.zip
What I dont understand is that, why and what may be the cause of this error... Is there any work around on this? I have set this following lines in my gradle.properties file inside the Project (MyApplication3/gradle.properties)
systemProp.http.proxyHost=192.168.140.19
systemProp.http.proxyPort=3128
systemProp.http.proxyUser=userid
systemProp.http.proxyPassword=password
systemProp.http.nonProxyHosts=localhost
systemProp.https.proxyHost=192.168.140.19
systemProp.https.proxyPort=3128
systemProp.https.proxyUser=userid
systemProp.https.proxyPassword=password
systemProp.https.nonProxyHosts=localhost
My System Admin said that there is no proxy user and password set so i dont know what to put on the proxyuser and proxypassword fields...
I hope there is someone that could help me :( im getting frustrated at this

Related

'Application Error' when Im deploying one of my services on Heroku

There is a problem that I really need help to solve it.
I have no much experience with using Heroku, but I use to deploy a few apps successfully. Now after deploying is succeed I try to launch the app in my browser and get this Error:
Application error
An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details. You can do this from the Heroku CLI with the command
heroku logs --tail
I attached below the logs I checked in my Heroku CLI, but I still don't understand what exact the problem in my application java code. Is any ideas or own experience with it? Thanks
THE LOGS I GOT
This is the text of your error:
"no main manifest attribute, in target /ProPetsAccountingService-0.0.1-SNAPSHOT.jar"
Pay attention to the answers to this question:
Can't execute jar- file: "no main manifest attribute"
Or check what is listed in your "Procfile".

Error when I try to install my application on my device

Today I try do make this application : https://medium.com/#diprochowdhury/developing-a-movies-app-with-picasso-and-themoviedb-org-api-using-fragments-eb1bd19cf572
but at the end, I have this error when I try to install my application :
Installation did not succeed.
The application could not be installed: INSTALL_FAILED_NO_MATCHING_ABIS
Installation failed due to: 'null'
Retry
Someone understand it? I have made a lot of research on internet but I don't find anything about this.
Thanks

java.lang.IllegalStateException: Scanner engine is not started. Unable to execute task

i tried an update of the sonarqube Server.
Now i get an error when i'm trying to scan my project with the ant task.
The error is "java.lang.IllegalStateException: Scanner engine is not started. Unable to execute task."
The Ant Task was succesful on my old Server (6.1), on the new one (6.5) it failed. So i tried to downgrade to 6.4, but the error still remains.
So i downgraded to 6.3 and the error disappears.
My question is, does anyone know about this error? And how can i solve it?
This is a misleading error message. I faced this error when I added Authentication to my server i.e. force authentication for every user.
If you have added authentication recently too, then you need to make sure that you are passing the sonar.login property through your scanner.
You may create a "build" user, generate its token and pass it to the sonar job.
This is how a token can be generated.

AWS Java NoSuchMethodError using IVONA Text to Speech

I have started using IVONA TTS and AWS is a dependancy of it, so I have also imported that to the project. My problem is that when running even the sample Java application I get the following error:
Exception in thread "main" java.lang.NoSuchMethodError: com.amazonaws.auth.AWS4Signer.presignRequest(Lcom/amazonaws/Request;Lcom/amazonaws/auth/AWSCredentials;Ljava/util/Date;)V
at com.ivona.services.tts.IvonaSpeechCloudClient.prepareRequest(IvonaSpeechCloudClient.java:292)
at com.ivona.services.tts.IvonaSpeechCloudClient.prepareRequestForGetUrl(IvonaSpeechCloudClient.java:270)
at com.ivona.services.tts.IvonaSpeechCloudClient.getCreateSpeechUrl(IvonaSpeechCloudClient.java:159)
at filetest.TextToSpeech.main(TextToSpeech.java:49)
TextToSpeech.java:49 being:
System.out.println("Requested URL: " + speechCloud.getCreateSpeechUrl(createSpeechRequest));
I'm using AWS version 1.10.12 (latest), but I've also tried several other previous versions only to get the same error. I've checked the class file "AWS4Signer", and the method "presignRequest" does exist, so I'm confused as to why I'm getting this error. If needed, here is the sample I used.
I'll be happy to add any more information if required. Any help would be greatly appreciated.
Your error is NoSuchMethod - I suspect that there is a version mismatch. Check from Ivona which version of AWS you need to use. According to Ivona's pom.xml it is 1.9.19.

xively java client returns status code 401

Trying to learn the Java interface to Xively. The following simple test fails with a 401 status code:
Feed myFeed = XivelyService.instance().feed().get(2126903832);
The exception statement is
com.xively.client.http.exception.HttpException: Http response status
indicates unsuccessful operation[Status code: 401.; Reason:
{"title":"Unauthorized","errors":"You do not have permission to access
this resource"} ]
The following console line leads me to believe that I'm not setting up the API key correctly:
2013-10-21 18:58:17,925 506 DEBUG [DefaultClientConnection.java:
276] (main:) >> X-ApiKey:
The Developer docs says replace <your api key> in config.properties with my API key. I did that, but it doesn't seem to make any difference.
I installed the library with Maven to my default Maven repo and point to it in Referenced Libraries. I am trying to build the whole thing in Eclipse.
My specific question is where is the config.properties the ApiConfig is reading?
I had this problem too. The problem was that I had double quotes in the config.properties file. The line should read:
api.key=yWYxyi3HpdqFCBtKHueTvOGoGROSAKxGRFAyQWk5d3JNdz0g

Categories