@dalen_ward@Firebase D'oh! I just flagged this to the team. I can guess how this is broken.
If you change your <script> tags to use the "compat" SDK this should all work:
https://t.co/R8AxpQd0mi
Or you could remove the __init.js script and convert your app to the modular style.
🎉 The NEW Firebase JS SDK is out of beta and now generally available!
Version 9 adopts a module-first format to eliminate unused code, resulting in a potential reduction of JavaScript bundle size of 80%.
Learn how to get started 👇 https://t.co/zSsQOSCB8y
⬇️📱 Optimize your app bundle and reduce download sizes with the new Firebase Android SDK!
The latest version lets you modularize your app so users receive only the code they need, when they need it.
Learn more → https://t.co/P45I0uQhIL
@rbolte@brocoli_@seldo@Firebase@googlecloud The vast majority of Firebase Hosting infrastructure is running on Google tech. Using Fastly for our CDN is the major exception.
@fastly GitHub, StackOverflow, and Twitter are all showing similar 503 errors from a varnish cache server. A quick look at headers shows Fastly headers in all of them. Outage?
@markgoho@ToddKerpelman Either one! rules-unit-testing has a nice utility function which helps you disable function triggers while seeding, which can be really helpful.
@maxmonteil@heybereket@fauna We just launched our v9 Beta SDK which should be *much* smaller than the old Firebase SDK. Check out the docs!
https://t.co/iWuSDdcvLP
@__AliBey Oh no, glad you caught it within an hour! If you haven't already please contact Firebase support:
https://t.co/4c2makBFyE
If you explain your mistake they will work with you and (probably) refund the charge.
📐 Measure Realtime Database performance.
With Firebase Performance Monitoring, you can collect and analyze RUM data for your app or website to see how fast your database really is.
Learn how → https://t.co/p5r0DaDL3N
@bcnzer Is there a chance you have a project ID mismatch? Maybe the emulator is running one project ID and your code is pointing at another?
If you want to dig into this more feel free to email me: samstern [at] google [dot] com
@nikhildp@Firebase We're working on it, those emails were likely a mistake. For now the best thing to do is ignore them while we investigate. We're also working on updating the status page.
@KamilRykowski@Firebase We're working on it, those emails were likely a mistake. For now the best thing to do is ignore them while we investigate. We're also working on updating the status page.
@alex7egli@Firebase We're working on it, those emails were likely a mistake. For now the best thing to do is ignore them while we investigate. We're also working on updating the status page.