Fix painful differences between the emulators and production #14380
Replies: 1 comment
-
|
Hey @LeeMatthewHiggins, sorry to hear you’re encountering these issues with the emulator. I understand how these make it difficult to work with and test your app with the emulators. As an open source project, we appreciate your feedback as this helps us refine our tools. We try to make the emulators match the behavior in production - If you spot any inconsistencies, reporting those to the Firebase Tools repository is the best way to get those checked and fixed. Regarding the issues you mentioned:
These are issues that our engineering team is aware of and are currently being tracked in firebase/firebase-tools#2034, and firebase/firebase-tools#2027. Could you please leave a comment or a thumbs up on the issues? This helps us prioritize future development efforts.
I couldn’t find any similar issues to this one. I think we’re going to need additional information to investigate this. To help us, could you open up a report in the Firebase Tools repository so that we can take a look and route it to the correct folks? |
Beta Was this translation helpful? Give feedback.
-
I use the emulators extensively to create full stack DART/flutter apps.
My main pain points.
Scheduled functions - I would love for the emulators to just do it based on system time.
Indexes - I would like the emulators to give me the index needed like production does via a link.
Paths - In firebase storage I was shocked to find my fully tested system did not work when I deployed to production. This was because I used the path (name / source) of the storage object in my business logic. This path is one format (absolute) in the emulators but relative in production.
Too many times a fully tested system using the emulators does not work in production and takes some effort to debug.
Beta Was this translation helpful? Give feedback.
All reactions