Update hosted files

[Chris Faiette]

I can't seem to update my static html files using firebase deploy. The command works great when initially uploading the site, but doesn't seem to work after that. I have also tried 'firebase deploy:hosting' command with no luck either.

[Jacob Wenger]

Hey Chris,

We will need some more info to help you out here:

1. Are you getting any error output from the CLI?
2. Have you tried hard-refreshing your browser to make sure you aren't getting a cached file? 
   
3. Does the deploy actually show up in the Hosting panel of your Firebase app dashboard?
4. How are you verifying that the page is not updating? Is it as simple as changing a string and seeing if that updates?
5. Are you sure you are viewing the correct URL? You may be deploying to one Firebase app when you mean to deploy to another Firebase app.
6. What version of the CLI are you using? You can use firebase -v or firebase -V to figure out the version info.

We aren't aware of any issues with Firebase Hosting at present and have not hear any other reports of issues like this. But we can work together to figure out what is going wrong for you.

Cheers,

Jacob

On Sat, Dec 5, 2015 at 8:39 AM, Chris Faiette <cfai...@gmail.com> wrote:

I can't seem to update my static html files using firebase deploy. The command works great when initially uploading the site, but doesn't seem to work after that. I have also tried 'firebase deploy:hosting' command with no luck either.

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/4dc410e6-2ece-48ab-803d-3fa69550e24b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris Faiette]

Thanks for the quick response Jacob, looks like it was a caching issue on my end, had a mischievous manifest.appcache file. Your reply had some great tips on troubleshooting though.