I am currently trying to write a code for text-to-speech module on Android Studio following these steps: https://cloud.google.com/text-to-speech/docs/libraries#using_the_client_library
I created my service account on my Google Cloud Platform, set the environment variable for GOOGLE_APPLICATION_CREDENTIALS and it echoes the path to my JSON file properly on my Mac OS.
However, when I run a test on the Android Studio, it returns error:
java.io.IOException: The Application Default Credentials are not available. They are available if running in Google Compute Engine. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
I googled how to solve this for a while but no luck on this issue.
I would like to know how to solve this credential checking issue.
Your advices are much appreciated!
Related
I am trying to run azure function in local in intellij.
While I run in local, I get this error in intellij :
when I click on configure, I see that the path is set correctly.
Now, I have tried uninstalling the current azure tools, and installing through npm or through installer. But nothing worked.
I have also tried the version 3 instead of 4 for azure tools, that also didnt help.
Any idea how to resolve this? Nothing seems to be working.
I have tested in my system - IntelliJ IDE - Java Azure Functions Project, it is running successfully.
As I observed in your IDE Azure Sign In Tool
the functions core tools path is different compared to my IntelliJ IDE Configuration.
Replace the Functions core tools path with the path as I have shown below, in your IDE and run the function once.
C:\Users\<YourUserFolder>\AppData\Roaming\npm\node_modules\azure-functions-core-tools\bin\func.exe
And even in the run configuration also, it should be same:
I am debugging my Service App, published in Azure, on my local machine with Visual Studio. I attached a debugger on the published .Net Core app.
It works fine and I can inspect all values and debugg all code I want.
But, I want to save some runtime values to a .TXT file on my local machine, so I can process it later. But it gives me the following error:
It makes sense, since I am debugging a remote aplication, thats running on an Azure Server. But how can I overcome this? Is there a way?
I know I could save this values to a blob on Azure then download it, but if I could put directly on my local machine it would be easier (and free) for me!
Thx for help!
So getting right to the point, I am behind a corporate firewall. I had to manually download the zip file for Android Studio which I extracted to program files (windows 10) on my machine. When I launch studio I'm dialogue'd studio needs to retrieve sdk's which I try to do but it fails on these 3 zips.
build-tools_r29.0.1-windows.zip
platform-29_r01.zip
sdk-tools-windows-4333796.zip
Mostly I see
java.net.SocketTimeoutException: Read timed out Warning: An error
occurred while preparing SDK package Android SDK Build-Tools 29.0.1:
Read timed out.
I'm assuming my firewall proxy is preventing this type of setup install since the links to these zips point outside our network but I am able to download the zips individually through a browser session one by one and save them here
c:\Users\myPin\AppData\Android\Sdk
I extracted each zip file and then reran Android Studio but it doesn't seem to have made any difference. It still goes out trying to download the same packages which I already extracted to the SDK folder. Shouldnt studio see the zips I've extracted in the SDK folder location? How can I get this working?
So we have work around I think others might find useful. If your having problems with the Gui SDK manager, then definitely use the cmd based sdk manager. This did not time out for us.
So for example where in the Gui I would get something like
java.net.SocketTimeoutException: Read timed out
When tryin got get platform-29_r01.zip
But if I try to perform the same operation using C:\Users\PIN\AppData\Local\Android\Sdk\Tools\bin\sdkmanager.bat using whatever cmd tool you like (I like cmder).
.\sdkmanager.bat --proxy=http --proxy_host=access.lb.ssa.gov --proxy_port=80 "platforms;android-28" --verbose
The above cmd will dl's and configure the sdk correctly.
You may have to do this for any of the sdk's you require. I think in our Firewall proxy scenario there's a user-agent setting or something that is not set for the Gui which is causing the timeouts but not with the cmd tools so this is a legitimate work around I think.
First things first. You have to check your Computer time, it must be accurate. If still error appeared, try this.
On you PC search Powershell and type code below. See image below for reference.
Path reference
Powershell Image
Failed version code
Click Retry
.\sdkmanager.bat --proxy=http --proxy_host=access.lb.ssa.gov --proxy_port=80 "platforms;android-29" --verbose
Run powershell > type cd> path of files
Check what SDK number version is getting error
From the android studio ERROR, click Retry while powershell is running.
If the said SDK version number is fixed, go to the next version number, by pressing control+C to powershell to stop the command.
Then type the same code with different number..
Note: If you do not have bin folder. You can create a folder named bin and create sdkmanager.bat file, inside sdkmanager.bat file, type this code >> sdkmanager.bat and save.
Anyone know the solution for this? Using the latest version of Azure tools and every time I do a build I see these messages in the output window:
Windows Azure Tools: Warning: Unable to delete directory APPROOT.
Windows Azure Tools: Warning: Unable to delete directory WEBUX.
Windows Azure Tools: Warning: Unable to delete directory APPROOT.
Angela, it is very much possible that an application has open handle to these folders and build process could not delete the folder/files so it can update with new binaries. This problem is specific to your machine, not Windows Azure.
If you could not figure out which application is using, what you could do is restart your machine so you know none of any application is using and then start Visual Studio and clean/rebuild your application and see if you still see this error. If you still see the error, I can provide some other troubleshooting info to help you further.
I ran into this error too. Azure SDK 1.7 added a new way to deliver 'extra' file resources upto the roles. To fix my this error, I manually deleted the folders under the Azure project, Profile roles after exiting VS.
As Avkash mentioned, some app is using your files... a few suggestions that worked for me:
1) Prevent antiviruses from inspecting the build folders
2) Disable Windows search service
3) Disable any auto-backup or auto-sync services that look at build folders
HTH
I'm developing a Windows Mobile application for internal company use, using the Windows Mobile 6 Professional SDK. Same old story: I've developed and tested on the emulator and all is well, but as soon as I deploy to advice I get an UnauthorizedAccessException when writing files or creating directories.
I'm aware that an application installed to a device needs to be signed but I'm running into roadblocks at every turn:
Using the project properties 'Devices' window I select 'Sign the project output with this certificate, and choose one of the sample certificates from the SDK. This results in a build error: "The signer's certificate is not valid for signing" when running SignTool.
If I try to run SignTool.exe from the commandline, I get an error telling me to run SignTool.exe from a location in the system's PATH.
I can't use the 'Signing' tab in the Project Properties to create a test certificate - this is greyed out (presumably for WinMobile projects?).
If at all possible, I would like to avoid having to go through Versign or the like to get a Mobile2Market certificate. If I have to go this route for a final version that's fine, but I need to at least be able to test the app on real devices.
Any advice would be most welcome!
First, make sure you really do need to sign it (you might be able to adjust the device security model).
If you do, then run signtool.exe, but from a Visual Studio command prompt. The easiest way to get there is fromt he Start menu, select Microsoft Visual Studio 2008->Visual Studio Tools->Visual Studio 2008 Command Prompt. This will set up all the proper pathing for you.