Torsten2217 / google-plus-platform

Automatically exported from code.google.com/p/google-plus-platform
0 stars 0 forks source link

Updated application does not reload .js file, only .xml #609

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
How does the product behavior differ from your expectations?
Sometime after 7/3, when I publish Hangout extension, it takes a very long time 
for the whole application to become "visible". Changes to app.xml file are 
visible immediately, however correlated app.js file is not loaded by hangout 
application for up to 24 hours. I can confirm manually that new version of the 
file loaded to appspot, but it's not loaded by hangout application

Describe, step-by-step, how to reproduce this issue.
Create app with .xml file referencing .js file
Upload to appspot using publisher for Python (tested on Windows and Mac)
Load Hangout app - development version 
Make change to .js file 
Upload updated app. 
Reload Hangout application - changes in .js file are not there

Describe the impact of this bug
-> How does this affect your application? eg. causing production outage,
breaking user facing features, preventing launch of new feature
-> How many users does this bug impact? What is the size of your user base
and what percentage of your user base is impacted?

When did this bug start happening?
Impossible to continue development for Hangout.

-> If the bug affects existing code (is a regression), when did you first
notice it?
Discovered 7/3 after new code was uploaded and tested was attempted 

When does the bug occur?
Occurs every time right now 

Describe any workarounds you have found
No workaround has been found. Waiting for 24 hours helps, but it does not seem 
to be very productive 

Original issue reported on code.google.com by gvm...@gmail.com on 10 Jul 2013 at 9:43

GoogleCodeExporter commented 9 years ago
This is an issue with caching - and there are multiple layers of caching going 
on in this case. The best solution I have is that my .xml file will reference 
resources (js and css files) with a query suffix after them. So it will be   
foo.css?version=12  and my deployment script automatically updates the version 
numbers.

Original comment by Prison4...@gmail.com on 4 Sep 2013 at 8:04