Stopped working, no support, no plan

[counterpoint]

Used to work fine. Now fails to start:
pCloud console client v.2.0.1
init failed
Support request received a suggestion that didn't work, then the reply "Unfortunately, the console client is to be improved, so we would not be able to assist you on this matter at present" So it seems the client is dead for some unspecified period with no clear future path. This is very disappointing, especially as the web site still insists that there is a console client. A lot of things can be done on a headless server that are impossible without the console client. What is to be done and when?

[ddssff]

What OS are you using?

[counterpoint]

Linux, Debian 9 Stretch. I have a script that checks for updates to the console client and builds a new version if it detects a change. There hasn't been any change SFAIK, but presumably the pCloud servers are behaving differently, since the console client is failing where it used to work. I noticed the failure on 4 April.

[blackjackshellac]

Agreed it is a gaping hole in functionality if they are no longer supporting a console client for a cloud service. I don't trust this code right now, given that there hasn't been a commit for over a year.

[counterpoint]

Support says "the improvement of our Console client is a part of our roadmap, so the same will be definitely improved in the future!" But that's pretty vague, has no timescale, and leaves us without important functionality for some indefinite period. So I thought it might help to raise an issue here.

[blackjackshellac]

No question. They're looking for 3 developers in Sofia Bulgaria, I suspect that is part of the issue.

[gdzevo]

Could you try to build #94
It seems they've added mandatory parameter deviceid

[counterpoint]

Could you clarify where to find build #94 please?

[bkline]

@counterpoint he's pointing you to this pull request:

#94

[bkline]

I can't even get the software to build, so it doesn't even get to the failing-at-runtime point.

/usr/include/boost/smart_ptr/detail/local_counted_base.hpp:67:9: error: ‘__builtin_assume’ was not declared in this scope
         __builtin_assume( local_use_count_ >= 1 );
         ^~~~~~~~~~~~~~~~

[blackjackshellac]

@bkline I fixed that issue with the diff in this zip file https://github.com/pcloudcom/console-client/files/3145967/pCloudCC_PSYNC_HAS_BUILTIN.zip

To apply to the branch, clone it, checkout the appropriate branch, unzip the archive and do git apply pCloudCC_PSYNC_HAS_BUILTIN.diff, it should fix the issue with __builtin_assume.

[counterpoint]

Thanks, I see he points me to the pull request, but I do not see how to get code from it.

[counterpoint]

Which is the appropriate branch? I can't see any information about anything other than the master branch, and the others appear to be behind the master.

[blackjackshellac]

On gdzevo's fork you'll find this branch, https://github.com/gdzevo/console-client/tree/add-tfa-support, clone it, and checkout the origin/add-tfa-support branch

[counterpoint]

Thanks, I was able to build the version direct from gdzevo. But I have a problem. I can run the console client and connect as root. But when running as a non-root user, the same username (email) and password fail with BAD_LOGIN_TOKEN. Prior to the change that broke the official client, there was no such problem.

[blackjackshellac]

Try renaming your ~/.pcloud directory and running again, perhaps there's a cached token in there that is no longer valid.