You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Error in firebase_functions/private/util.py processing event time attribute #136
After upgrading to the latest firebase tools npm install -g firebase-tools to v12.5.4, the CloudEvent event's time attribute has this iso format: 2023-09-16T13:32:06Z extracted by adding a print() call to the firebase_functions' site-package source.
So, that unprotected time.split('.') call isn't accounting for the ostensible change to the time attribute's format.
I'm using Python 3.11.4 on macOS 12.6 with firebase-functions v0.1.1 (latest).
I have the same issue, but running npm install -g firebase-tools@12.5.3 didn't fix it for me.
I followed the official tutorial to the letter and encountered this issue, so it seems to be quite a big oversight from the firebase team.
EDIT: I had installed firebase tools from the bash script, had to uninstall it, install this specific npm version, and the issue is now fixed. Official tutorial is still broken though.
@jackall3n@joaqo Sorry about this. I realise that the workaround was downgrading the firebase_tools version. Correct me if I am wrong. I'll reopen this issue and investigate further
+1 this issue still happens and if not for this thread it would have been very difficult for me to resolve. I spent ~1 hour fruitlessly playing around with versions of various components before finding this. npm install -g firebase-tools@12.5.3 works.
Could you please check with the latest version 0.2.0 and confirm if this issue is fixed on your side? There was a PR that was merged but not released earlier which may have fixed this issue
Thanks for reporting this issue. I've managed to reproduce (MRE) it using the following versions:
firebase_functions: v0.1.1
firebase-tools: v12.5.4 (and all later versions)
firebase-admin: v6.2.0
To fix this issue, you can either:
Update from firebase_functions v0.1.1 to v0.1.2.
Update to the latest version of firebase_functions (v0.4.3).
Since there are good solutions to this issue, I'm going to close this issue here. However, if you have any further comments or problems with the solutions, let me know.
Activity
ekalosak commentedon Sep 16, 2023
It's worth noting that downgrading
firebase-toolsfrom the latestv12.5.4to the previousv12.5.3fixes the issue.tl;dr fix this bug by running:
npm install -g firebase-tools@12.5.3Firebase staff - please consider adding an integration test that covers
@firestore_fn-triggered functions to the firebase-tools CI.mitch-36 commentedon Sep 24, 2023
Thanks for sharing.
npm install -g firebase-tools@12.5.3Fixed the issue for me too.
joaqo commentedon Sep 25, 2023
I have the same issue, but running
npm install -g firebase-tools@12.5.3didn't fix it for me.I followed the official tutorial to the letter and encountered this issue, so it seems to be quite a big oversight from the firebase team.
EDIT: I had installed firebase tools from the bash script, had to uninstall it, install this specific npm version, and the issue is now fixed. Official tutorial is still broken though.
brianellin commentedon Sep 29, 2023
Same issue for me using the latest firebase.tools. Using 12.5.3 via npm for now until the issue is resolved.
Also, I'd recommend some better docs on "installing" a specific version binary from the firebase.tools website.
exaby73 commentedon Oct 9, 2023
Snce this issue has been fixed, I'll close this issue. Please comment if you disagree with my decision
jackall3n commentedon Oct 10, 2023
This is still an issue in the latest version, this issue shouldn't be closed.
joaqo commentedon Oct 10, 2023
Yeah, this is the 2nd recent issue @exaby73 has closed that hasn't actually been fixed.
exaby73 commentedon Oct 11, 2023
@jackall3n @joaqo Sorry about this. I realise that the workaround was downgrading the firebase_tools version. Correct me if I am wrong. I'll reopen this issue and investigate further
antopolskiy commentedon Oct 12, 2023
+1 this issue still happens and if not for this thread it would have been very difficult for me to resolve. I spent ~1 hour fruitlessly playing around with versions of various components before finding this.
npm install -g firebase-tools@12.5.3works.zsais commentedon Oct 18, 2023
+1 this issue still exists
exaby73 commentedon Oct 19, 2023
@zsais @joaqo Could you check this issue against the main branch by change the dependency in your
requirements.txt?Change
firebase_functions=<version>togit+https://github.com/firebase/firebase-functions-python.git@main#egg=firebase-functionsexaby73 commentedon Jan 15, 2024
Could you please check with the latest version
0.2.0and confirm if this issue is fixed on your side? There was a PR that was merged but not released earlier which may have fixed this issueantopolskiy commentedon Feb 22, 2024
I just tried it with firebase-tools v13.3.0 and it still fails.
exaby73 commentedon Mar 8, 2024
Hey @antopolskiy if you can still reproduce it, could you provide me with your stack trace?
CorieW commentedon Jun 25, 2025
Hi @ekalosak.
Thanks for reporting this issue. I've managed to reproduce (MRE) it using the following versions:
To fix this issue, you can either:
Since there are good solutions to this issue, I'm going to close this issue here. However, if you have any further comments or problems with the solutions, let me know.