UnhandledPromiseRejectionWarning: FirebaseError: Task
See original GitHub issueEnvironment info
firebase-tools: Version: 7.3.2
Platform: macOS: 10.14.6
Test case
I tried to upload files to firebase hosting with firebase deploy --only hosting
which throws error.
Steps to reproduce
I tried to upload files to firebase hosting with firebase deploy --only hosting
. In my files I have symlinks, one of the symlink points to a file that doesn’t exist. This causes error.
Expected behavior
Upload files without any issues.
Actual behavior
Throws UnhandledPromiseRejectionWarning: FirebaseError: Task
=== Deploying to 'project'...
i deploying hosting
i hosting[project]: beginning deploy...
i hosting[project]: found 141 files in client/build
Error: Task scripts/symlink-file.js.map failed: retries exhausted after 1 attempts
(node:56592) UnhandledPromiseRejectionWarning: FirebaseError: Task scripts/symlink-file.js.map failed: retries exhausted after 1 attempts
at Queue.<anonymous> (/Users/user/.nvm/versions/node/v12.9.1/lib/node_modules/firebase-tools/lib/throttler/throttler.js:189:27)
at Generator.next (<anonymous>)
at /Users/user/.nvm/versions/node/v12.9.1/lib/node_modules/firebase-tools/lib/throttler/throttler.js:7:71
at new Promise (<anonymous>)
at __awaiter (/Users/user/.nvm/versions/node/v12.9.1/lib/node_modules/firebase-tools/lib/throttler/throttler.js:3:12)
at Queue.executeTask (/Users/user/.nvm/versions/node/v12.9.1/lib/node_modules/firebase-tools/lib/throttler/throttler.js:180:16)
at Queue.<anonymous> (/Users/user/.nvm/versions/node/v12.9.1/lib/node_modules/firebase-tools/lib/throttler/throttler.js:93:36)
at Generator.next (<anonymous>)
at /Users/user/.nvm/versions/node/v12.9.1/lib/node_modules/firebase-tools/lib/throttler/throttler.js:7:71
at new Promise (<anonymous>)
(node:56592) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
(node:56592) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Firebase hosting deployment failing - Stack Overflow
I've tried regular deployment with firebase deploy as well as with --except functions flag but with no luck. Also tried updating npm and ......
Read more >How to fix Firestore Error: PERMISSION_DENIED - Medium
First of all, let's understand what this error actually represents. Generally, when we interact with Firebase products, and something goes wrong ...
Read more >Error removing document: FirebaseError: Missing ot insufficient ...
//Let's say that a user is not logged in but needs to read landmarks data,. 5. //we should then create a rule to...
Read more >Ionic 4 Cordova - Run Android Firebase error all of a sudden
Task :CordovaLib:processDebugManifest UP-TO-DATE ... (node:13453) UnhandledPromiseRejectionWarning: Unhandled promise rejection.
Read more >failed to generate manifest from function source ... - You.com
Failed to load function definition from source: FirebaseError: Failed to load ... UnhandledPromiseRejectionWarning: Error: The default Firebase app already ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@tuananhlhpnd99 Yeah, that’s pretty a head ache for developer, also wastes hours and hours of time to find out the right issue.
@Firebase @Memeriaj team, If you guys can show a proper warning or error message will help to save the time instead of unhandled promise reject warning
I suffer from this issue too and it turned out that I left an unused symlink in the public folder. After removing that symlink, things worked just fine. I think that is time to close the issue.