REST Client hangs trying to update itself

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try to launch Rest client from app menu or Chrome icon in system tray

What is the expected output? 
Rest client launches

What do you see instead?
"Installing application..." with a green Pacman
It never clears...no errors on Dev Tools console

On what operating system?
Win 7 x64 and Win Vista x86

Please provide any additional information below.
Client version 3.0.26
Chrome Version 23.0.1271.64 m

Original issue reported on code.google.com by margaret...@gmail.com on 9 Nov 2012 at 3:29

[GoogleCodeExporter]

Strange. There should not be any error this kind. Can you try to set a variable 
 DEBUG_ENABLED with value: true in Local Storage? Maybe with this it will print 
some debug information. Probably it hangs on database update but I'm not sure 
if it is it.

Original comment by jarro...@gmail.com on 9 Nov 2012 at 8:11

[GoogleCodeExporter]

Well, I tried, but the app seems to be resetting it to "false" every time the 
tab loads. I'm not really familiar with how local storage works.

Original comment by margaret...@gmail.com on 9 Nov 2012 at 8:56

[GoogleCodeExporter]

I did find where my URLs are in the database though. I really did want to 
rescue them, so now I have copied them out. I'll try simply removing and 
reinstalling the app now. 

Original comment by margaret...@gmail.com on 9 Nov 2012 at 9:00

[GoogleCodeExporter]

So can you tell mi is it fresh install or it is update from previous version?

Original comment by jarro...@gmail.com on 9 Nov 2012 at 9:01

[GoogleCodeExporter]

A reinstall after removing it seems to have worked OK. I suspect there was 
something in my saved requests that it was choking on. 

Original comment by margaret...@gmail.com on 9 Nov 2012 at 9:02

[GoogleCodeExporter]

Oh, it was a well-used previous version. A fresh install seems to have worked 
fine. I just didn't want to lose my saved requests; I pasted them into a file 
and can refer to them and rebuild them. 

Original comment by margaret...@gmail.com on 9 Nov 2012 at 9:03

[GoogleCodeExporter]

But it does not a way to solve the problem :(
I'll try to check what can be wrong in DB update.

Original comment by jarro...@gmail.com on 9 Nov 2012 at 9:04

• Changed state: Done

[GoogleCodeExporter]

If this helps you, there is a import from file option. File should have 
structure as follows:
{"projects":[], "requests":[{"id":DB ID, 
"encoding":"application/x-www-form-urlencoded", "headers":"X-Requested-With: 
XMLHttpRequest\nUser-Agent: MyUserAgent", "method":"POST", "name":"Request 
name", "payload":"Request payload", "project":0, "skipHeaders":false, 
"skipHistory":false, "skipMethod":false, "skipParams":false, "skipPath":false, 
"skipPayload":false, "skipProtocol":false, "skipServer":false, 
"time":1346785456759 <- time value, "url":"http://REQUEST URL"}]}

Original comment by jarro...@gmail.com on 9 Nov 2012 at 9:10

[GoogleCodeExporter]

Well, I still have a broken copy on my home machine....willing to provide
information from that.

Original comment by margaret...@gmail.com on 9 Nov 2012 at 9:16

[GoogleCodeExporter]

OK. I believe I found who's guilty. 
When application upgrading itself from previous version to the new one it 
change the requests database table to new one. When inserting new data in query 
it should replace all quotas with \' to work properly. Unfortunately I've made 
a mistake and I changed all " to \", not ' to \" which gives nothing because it 
destroys the query anyway it any of saved value contains ' character.
I'll send an update to the web store today. If it not update itself try update 
it manually in extensions menu (in developer mode).   

Original comment by jarro...@gmail.com on 10 Nov 2012 at 1:16

• Changed state: Fixed

[GoogleCodeExporter]

The copy on my home machine updated with no problem.

Original comment by margaret...@gmail.com on 10 Nov 2012 at 1:31

[GoogleCodeExporter]

Issue 110 has been merged into this issue.

Original comment by jarro...@gmail.com on 10 Nov 2012 at 1:36

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The same happened to me. I hadn't used the extension since some days ago, and 
today it was not loading (got stuck in the "Installing application..." step 
with the green Pacman).

I tried to update the extension as you described but I already had the latest 
version (3.0.30). Finally I had to remove and do a fresh install and now it is 
working.

I'm at Mac OS X 10.8.2 with Chrome version 23.0.1271.64.

Original comment by pablit...@gmail.com on 19 Nov 2012 at 2:07

[GoogleCodeExporter]

Seeing same problem - green pacman stuck halfway along progress bar under the 
"Installing application..." message. Windows 7 with Chrome Version 23.0.1271.91 
m. Guess I'll have to go the uninstall/reinstall route...

Original comment by mgpee...@gmail.com on 26 Nov 2012 at 6:58

[GoogleCodeExporter]

Strange. I've fixed it a time ago. Re-open this issue and will check again.

Original comment by jarro...@gmail.com on 28 Nov 2012 at 10:15

• Changed state: Started

[GoogleCodeExporter]

Can't upgrade either: Windows 7 x64 and Chrome Version 28.0.1500.72 m

Last dev console entry:
(-:-) 2013-07-24 22:28:35,420 [DEBUG] 12 tasks left to do of: 21
 restclient.nocache.js:37

Do you need any additional information?

Original comment by frederik...@gmail.com on 24 Jul 2013 at 8:31

[GoogleCodeExporter]

I believe it is an upgrade error caused by SQL query. There may be an error 
when creating a query. 
Fastest way is to remove "databaseSet" entry from local storage. If it is 
present the app will still try to update itself. If not it will try to create a 
new database structure.
There is a catch. If you do this the app will not update itself (it doesn't do 
this anyway) and all data will not be moved to new structure. The data will be 
present in the DB but the app will not use it. You can export saved requests on 
the server / Google Drive and then import it. But history will be lost. At 
least until you move the data to new tables manually. But it is not easy 
(totally different schema).
I'm working on new version of the application which will use IndexedDB instead 
of WebSQL. It will have new upgrade mechanism. However it take some time before 
it will be ready. I estimate that I will have working version in September. 
Since then I do not plan making any changes to the current version.

Original comment by jarro...@gmail.com on 26 Jul 2013 at 11:53