Chrome version not updating

[GoogleCodeExporter]

Using the link on the main page as usual ( 
http://game-golem.googlecode.com/svn/trunk/chrome/GameGolem.crx ) , I'm still 
on version r792.

Original issue reported on code.google.com by bparoi...@gmail.com on 27 Sep 2010 at 4:56

[GoogleCodeExporter]

I have the same prob. Is there any trick for chrome?

Original comment by pbotsi...@gmail.com on 27 Sep 2010 at 6:19

[GoogleCodeExporter]

Not all people working on Golem can build the Chrome version - in addition, a 
bug in Chrome itself means that in order to build the Chrome version, you have 
to quit it first (otherwise it pops up a new Chrome window, and doesn't build 
the release).

I've just updated the Update worker, so the in-Golem update buttons are now 
enabled, and *should* let you update identically to the Firefox version.

Until Chrome itself gets that bug fixed however, there will still be occasions 
when it doesn't get a release at the same time as the Firefox build.

Original comment by RycochetTM on 1 Oct 2010 at 4:39

• Changed state: Verify
• Added labels: Usability

[GoogleCodeExporter]

Changed the update worker a little more, so it's more future proof and less 
reliant on current data.

If anybody can update to r806 and then hit the Beta button to test it would be 
useful...

Original comment by RycochetTM on 2 Oct 2010 at 4:36

• Added labels: Worker-Update, Milestone-NextRelease

[GoogleCodeExporter]

Worked for me.

Original comment by bparoi...@gmail.com on 2 Oct 2010 at 10:14

[GoogleCodeExporter]

My IDE has been troubleshot and now I am properly building the Chrome version.

Seems I didn't set the path to Golem trunk so the "./" in the build.bat worked 
for everything but chrome extension paths. Little bit of playing with it and 
got mine going. (FYI, turning off --no-message-box helps until you are sure you 
are packing the extension!)

Original comment by HaploAW@gmail.com on 4 Oct 2010 at 2:13

[GoogleCodeExporter]

Verified that version R812 isn't updating.  The buttons are enabled indicating 
that there are two updates available for it, r813 and r817, I click the button 
and it asks if you want to install it.  after clicking that button it indicates 
that it was installed but then when I go and look at the extensions installed 
it says that it is r812.  I tried uninstalling and restarting chrome and then 
installing from the site and I get r812 and it indicates that there is an 
update available.

Original comment by p_ha...@hotmail.com on 10 Oct 2010 at 12:28

[GoogleCodeExporter]

I had the same issue HaploAW did, but I think I sorted that out now. I got 
fooled by the same silent fail of --no-message-box also. r818 should include 
r813 and r817, so updating should work for Chrome users again. Sorry about 
that, I'm not a Chrome user myself.

Original comment by lur...@hotmail.com on 10 Oct 2010 at 2:44

[GoogleCodeExporter]

I've got (waiting to be rolled out with other changes) an update for 
worker_+update, the build script, and some other related bits.

Now using browser detection - and the _version.js file checked depends on the 
browser detected (so it'll copy it to /chrome/ when you build the chrome 
version) - can't help for failed builds, but does mean that if there isn't a 
build for a specific platform then it won't matter (Firefox will be getting a 
dedicated extension at some point, but that's currently on hold).

Internally "isGreasemonkey" is no longer used, instead there's a "browser" 
string, lower case, with the name of the browser in it ("greasemonkey" is 
classed as a browser) - already changed it everywhere that's currently needing 
it.

Original comment by RycochetTM on 10 Oct 2010 at 2:54

[GoogleCodeExporter]

Original comment by RycochetTM on 10 Dec 2010 at 2:43

• Changed state: Fixed