I'm trying to initialize a firebase project using the command firebase init, but I get the message Error: Command requires authentication, please run firebase login.
When I run firebase login, the process hangs and does not return the prompt :
Previously I have installed the latest stable version of node.js and firebase-tools (with npm install -g firebase-tools). I'm using a Windows 8.1 x64 machine.
The content of firebase-debug.log file noes not report any error or warning:
[debug] ----------------------------------------------------------------------
[debug] Command: C:\Program Files (x86)\nodejs\node.exe C:\Users\ \AppData\Roaming\npm\node_modules\firebase-tools\bin\firebase login
[debug] Platform: win32
[debug] Node Version: v5.1.0
[debug] Time: Mon Nov 23 2015 13:49:06 GMT-0500 (Eastern Standard Time)
[debug] ----------------------------------------------------------------------
[debug]
How can I debug the login command? Nomaly it should open a browser window for authentication, but this does't happen in my case.
Did you get your answer yet?
You need to type 'firebase login --interactive' then it'll take you through the browser to a gmail account to sign into then you can execute your 'firebase init' command.
Related
I am trying to restore NuGet packages from the Azure Artifacts feed with the task "Nuget restore" which is giving an error -
2020-03-17T06:16:01.923910Z Resolved from tool cache: 4.1.0
2020-03-17T06:16:01.939365Z Using version: 4.1.0
2020-03-17T06:16:01.924520Z Found tool in cache: NuGet 4.1.0 x64
2020-03-17T06:16:02.080668Z [command]C:\Windows\system32\chcp.com 65001
2020-03-17T06:16:02.007116Z Active code page: 65001
2020-03-17T06:16:02.012223Z Detected NuGet version 4.1.0.2450 / 4.1.0
2020-03-17T06:16:02.081611Z SYSTEMVSSCONNECTION exists true
2020-03-17T06:16:04.157611Z ##[error]Error: Error: read ECONNRESET
2020-03-17T06:16:04.190260Z ##[error]Packages failed to restore
Details -
Server - Azure DevOps server 2019
Azure DevOps build pipeline
Azure Artifacts Feed - offline
Agent Version 2.144.2
What I noticed
my "Nuget Restore" task is working well when my build machine is in the same LAN with azure DevOps server and giving an error with the different LAN's build machine.
I googled but did not find anything. some pages showing this error is because of the proxy, some page is showing version issue of NuGet.
Not getting what exactly the issue is. Can someone help with this?
I'm developing a Mac app that will be released outside the Mac App Store.
So, basically I just automated the build process: it builds the app and signs the .app file with a Mac Dev ID.
If I sign this app with my credentials it works as expected. Either in my machine or my peers machine.
But, if my peer signs it with his credentials (using the same scripts), the app crashes either in his machine or mine. This is the error from the Console:
6/27/14 3:04:39.647 PM taskgated[1807]: none of the 1 applicable provisioning profile(s) apply
6/27/14 3:04:39.647 PM taskgated[1807]: killed com.myCompany.myApp[pid 2255] because its use of the com.apple.developer.team-identifier entitlement is not allowed
6/27/14 3:04:39.648 PM com.apple.launchd.peruser.501[286]: ([0x0-0x117117].com.myCompany.myApp[2255]) Exited: Killed: 9
6/27/14 3:04:39.719 PM CoreServicesUIAgent[2258]: Error: qtn_file_apply_to_path error: Read-only file system
6/27/14 3:04:42.021 PM CoreServicesUIAgent[2258]: Unable to continue stopped application -- error -600
What are we doing wrong? and how can we solve it?
I'm using Jenkins on Win7 and i've installed tomcat for ssh-agent plugin. And I could clone my GitLab project via git bash via ssh.
But if I build the project by Jenkins, it always says :
[ssh-agent] Using credentials IliptonChen(APRTest)
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent] FATAL: Could not find a suitable ssh-agent provider
FATAL:[ssh-agent] Unable to start agent
The full output text is here
Did I do anything wrong?
Check the version of your ssh-agent used by Jenkins.
This bug (for linux, but could apply to Windows too) reports (10 days ago, January 2014) this very same error message:
"JENKINS-20276: Native Library Error after upgrading ssh-agent from 1.3 to 1.4".
Downgrading to 1.3 resolves the issue.
Update 2019, five years later: as commented, this should be fixed now.
ssh-agent.exe is part of a Git for Windows distribution
D:\git\git>where ssh-agent.exe
D:\prgs\gits\current\usr\bin\ssh-agent.exe
(provided path/to/git/usr/bin is first in the %PATH% used by Jenkins)
Assuming you've installed Windows Git on Windows slave, it comes with ssh-agent binary (e.g. C:\Program Files\Git\usr\bin). Try adding its path to system variable PATH.
Otherwise untick SSH Agent and choose the credentials by selecting Credentials from dropdown in Source Code Management section.
Another way is to generate personal API token (OAuth) for that GitHub user and include that along with your repository address, e.g.
git clone https://4UTHT0KEN#github.com/foo/bar
For windows, the plugin still requires Tomcat to be installed in both master and slave.
I got this error because I was using an Ubuntu image for the agent, which doesn't have SSH installed.
agent {
docker { image 'ubuntu:focal' }
}
... so the solution was as simple as installing SSH as part of the pipeline:
steps {
sh "apt-get update && apt-get install ssh -y"
// rest of your steps here...
}
In my case, the error was accompanied by an error about disk space depletion:
[ssh-agent] FATAL: Could not find a suitable ssh-agent provider
[ssh-agent] Diagnostic report
[ssh-agent] * Exec ssh-agent (binary ssh-agent on a remote machine)
[ssh-agent] hudson.AbortException: Failed to run ssh-agent: mkdtemp: private socket dir: No space left on device
So I ran docker system prune -a, which fixed it.
Step by step: 0) Install Appcelerator Titanium Studio.
1) Install Oracle VirtualBox.
2) Download and Install Android x86 VM. Instructions (Russian) here http://habrahabr.ru/post/119931/
3) Run and configure Android x86 (configure means that you should have 2 ethernet adapters and your Android x86 Virtual Machine(VM) must have an IP (for example 192.168.56.101))
3.5) try to ping your VM. Everithing should works just fine.
4) Run you Titanium studio and create an new project.
5) Run command line and from %Android SDK%/platform-tools/ directory perform operation
"adb connect 192.168.56.101".
it has to connect to VM successfully on port 5555.
Note: IF you not did this your Titanium Studio will log something like this
[DEBUG] ...\AndroidSDK\platform-tools\adb.exe start-server
[INFO] Titanium SDK version: 2.1.4 (11/09/12 12:46 51f2c64)
[DEBUG] Waiting for device to be ready ...
[TRACE] adb devices returned 0 devices/emulators
[TRACE] adb devices returned 0 devices/emulators
[TRACE] adb devices returned 0 devices/emulators
6) Try to install your Titanium Application on the DEVICE. As a platform i select Android 4.0.3 [x86]
6.5) Titanium studio would do a lot of work and it ends with:
[DEBUG] Waiting for device to be ready ...
[TRACE] adb devices returned 1 devices/emulators
[DEBUG] Device connected... (waited 0 seconds)
[DEBUG] waited 0.015000 seconds on emulator to get ready
[INFO] Installing application on device
7) Titanium successfully found the and have connected to the device? compiled all of the resources and trying to install your application to the device with this:
"C:\!Development\AndroidSDK\platform-tools\adb.exe -d install -r C:\!Development\Titanium\china\build\android\bin\app.apk"
But there is not matter how much time you will wait it won't install.
What is the problem? What i did wrong?
You have to make corrections to the file:
%HOME%\AppData\Roaming\Titanium\mobilesdk\win32\3.0.2.GA\android\builder.py
according to the screenshots in this article (Russian).
Can't this help?
It seems that you need to use adbhost
http://code.google.com/p/android-on-freerunner/wiki/AndroidDebugBridge
Here is the manual from xda to make it through wifi
How can I connect to Android with ADB over TCP?
Since the Link in ReinRaus 's post is down, i wanted to share the solution with you guys:
Get to %APPDATA%/Titanium/mobilesdk/win32/3.1.3.GA/android and open up builder.py
(Note: Replace 3.1.3.GA with your Version)
At around line #2601 you find:
device_args = ['-d']
# We have to be careful here because Windows can't handle an empty argument
# on the command line, so if a device serial number is not passed in, but
# a debugger_host (the argument after device serial number) _is_ passed in,
# to Windows it just looks like a serial number is passed in (the debugger_host
# argument shifts left to take over the empty argument.)
This is the line which causes the Install Script to force USBDebug mode, as seen in the Log while deploying:
[DEBUG] XX/sdk/platform-tools/adb.exe -d shell ls /data/app/xx.yyy.zzz*.apk
Change the args to ['-a']. This will stop forcing USB Devices only and you should be fine
My TeamCity agent is contniually trying to download upgrades from the TeamCity server. It always downloads the files, then fails to start the installation, with the error:
WARN - jetbrains.buildServer.AGENT - Unable to start upgrade: Connection reset
My server is running at http://localhost:9912
How do I stop this endless cycle?
Latest version of TeamCity downloaded from JetBrains
I'm guessing you're running the agent as an AD account rather than under the machine account.
Run the agent service under an account with administrative permissions for the upgrade. I don't remember the specifics of what it's trying to write but it won't if it's a standard user.