pcolby / bipolar

Free your data from Polar FlowSync
GNU General Public License v3.0
115 stars 16 forks source link

Failed to Install Bipolar Hook #63

Closed LillyLP closed 8 years ago

LillyLP commented 8 years ago

Hello, I have installed Biploar, but when I run it I get the error message 'The Bipolar hook does not appear to beinstalled. Would you like to install it now'

On pressing Yes, I get a 'Failed to install.....' message

I have manually renamed the old Qt5Network.dll file and repaced it with the one in Bipolar directory but get the same response when I run Bipolar again. .

If I cancel the failed installation message and go to the input actions (I have manually created the Folder) I get the following in teh Bipolar window.

19:24:18 "Bipolar" "0.4.0.562" "Beta" 19:24:18 failed to locate flowsync 19:24:18 Unabled to read version information for "E:\Program Files (x86)\Polar\Bipolar\Qt5Network.dll" 19:24:18 "E:\Program Files (x86)\Polar\Bipolar" hook version -1 19:24:18 "E:\Program Files (x86)\Polar\Bipolar\hook" hook version 2 19:24:18 Processing started. 19:24:18 Processing finished. 19:24:18 Skipped 0 training sessions processed previsouly. 19:24:18 Wrote 0 of 0 files for 0 of 0 new training sessions.

Can you help?

pcolby commented 8 years ago

Hi @LillyLP,

First up, well done on providing lots of good info already :smile: Hopefully we can get to the bottom of this one pretty quickly.

Now, the log output itself, is very odd! Specifically, the line:

19:24:18 "E:\Program Files (x86)\Polar\Bipolar" hook version -1

Here, it should be more like:

19:24:18 "E:\Program Files (x86)\Polar\Polar FlowSync" hook version ...

That is, the code explicitly hardcodes "Polar FlowSync" into that path!

Can I get you to confirm that you have cut-and-pasted correctly? (I suspect you have, given that the "Unable to read version" message is also showing that same incorrect path).

In the meantime, I'll take a look at how the code that constructs that path to see if there's any clue as to why it might have messed it up.

Cheers.

pcolby commented 8 years ago

Ah, I see. So when QDir FlowSyncHook::flowSyncDir() fails (as indicated by the 19:24:18 failed to locate flowsync) line, the function returns QDir();, which rather than being a NULL or invalid directory, actually returns the program's current working directory.

So, there's two issues here...

  1. the QDir FlowSyncHook::flowSyncDir() function is not returning a value that indicates that the path wasn't found, and
  2. the path wasn't found :wink:

The first one, of course, is very quick and easy to fix.

The second one, we'll need to dig into :)

pcolby commented 8 years ago

BTW, if you're in a hurry, you can install the hook manually (happy to walk you through it). Bipolar will still nag you until we fix the detection issue, but at least the export would still work. Let me know if you want to go that route for now. In the meantime, I'll prepare a small set of questions re your FlowSync installation.

pcolby commented 8 years ago

Ok, so can you please cut-and-paste the output of the following commands:

  1. echo %ProgramFiles%
  2. echo %ProgramFiles(x86)%
  3. echo %ProgramW6432%

Also, what path is Polar FlowSync installed in?

Thanks.

PS If you've installed FlowSync somewhere weird (and hey, why not? It's your right to install it wherever you want to), then I might add some logic to check for the FlowSync installer's registry entries too.

LillyLP commented 8 years ago

Will come back on questions, but yes to unusual location as installed on E drive as C was getting full so MDIR new folder on E for additional programmes.

Louis Sent from my BlackBerry® wireless device

-----Original Message----- From: Paul Colby notifications@github.com Date: Fri, 22 Jan 2016 22:37:30 To: pcolby/bipolarbipolar@noreply.github.com Reply-To: pcolby/bipolar reply@reply.github.com Cc: LillyLPlouis@lillywhi.demon.co.uk Subject: Re: [bipolar] Failed to Install Bipolar Hook (#63)

Ok, so can you please cut-and-paste the output of the following commands:

  1. echo %ProgramFiles%
  2. echo %ProgramFiles(x86)%
  3. echo %ProgramW6432%

Also, what path is Polar FlowSync installed in?

Thanks.

PS If you've installed FlowSync somewhere weird (and hey, why not? It's your right to install it wherever you want to), then I might add some logic to check for the FlowSync installer's registry entries too.


Reply to this email directly or view it on GitHub: https://github.com/pcolby/bipolar/issues/63#issuecomment-174154166

pcolby commented 8 years ago

So I've (theoretically) corrected both of the issues identified above. However, I don't have access to a valid Windows test machine currently, so an unable to test right now. Once the builds have completed in AppVeyor (https://ci.appveyor.com/project/pcolby/bipolar/build/master-245) feel free to download and test for yourself :smile:

Note, AppVeyor appears to be broken (on their end) currently... if it's not working again in the morning, I'll shoot their support guys a message.

Cheers.

pcolby commented 8 years ago

Note, AppVeyor appears to be broken (on their end) currently... if it's not working again in the morning, I'll shoot their support guys a message.

done.

pcolby commented 8 years ago

Once the builds have completed in AppVeyor feel free to download and test for yourself :smile:

The builds are now available at https://ci.appveyor.com/project/pcolby/bipolar/build/master-249

You'd probably want the msvc2013 64-bit release version - https://ci.appveyor.com/project/pcolby/bipolar/build/master-249/job/3qvio32nqy4320h3/artifacts but any of them should be fine for testing.

Cheers.

LillyLP commented 8 years ago

Thanks Paul. I uninstalled the two programmes and reinstalled them in their default folder and Bipolar works perfectly - an excellent programme without which I faced the prospect of adding summary data to my polarprecision where I have data dating back to 2001. In due course I shall retry reinstalling on my E drive as space on my C: (System) drive is very short. Thanks for your trouble. (It used to be a lot easier when you could just edit *.ini files!),

Thanks

pcolby commented 8 years ago

Released in 0.5.1.