Yuchen Shi

I'm not 100% sure how, but this PR seems to break Storage unit tests: https://github.com/firebase/firebase-tools-ui/runs/6278540877?check_suite_focus=true#step:5:2864 Also: linter

We've made a huge update to the codebase and this PR is outdated. I'm redoing the proposed changes in #858 -- stay tuned and you're welcome to test on that...

> I'm not 100% sure how, but this PR seems to break Storage unit tests: https://github.com/firebase/firebase-tools-ui/runs/6278540877?check_suite_focus=true#step:5:2864 Found it -- caused by the fetch mocking failing since the URLs no longer...

Released in CLI v11.14.0. It's not perfect, especially not all emulators work over HTTPS, but we think it's a step in the right direction. Let us know if you run...

Any chance you can upload the logs (`*.log`) created? As mentioned in the output, the logs contain more information to debug the issue.

@tonyjhuang The logs seem to indicate issues on the rules runtime. Would you mind taking a look?

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help...

When the reference changes to an empty string, is there any error in your browser developer tool? Also, would you mind uploading a screencast? These will help us pin down...

@tachibana-shin Thanks for the report! I'm actually surprised to see these errors given that the Auth Emulator does support CORS on all domains reflected. This may be related to how...

I think we have two separate issues here. @tachibana-shin According to the HAR file, the response reverse proxied by Gitpod was `401` with no CORS related headers. I've tried to...