SailHub - abandoned?

SailHub - native app for Github, I reported issue with the app to the dev on his Github in summer 2025, no response yet. Since summer 2025 is not working (at least for me) to add token for login to github account. When I run it from terminal, there is only this:

[W] NemoConfigurationValuePlugin::registerTypes:52 - org.nemomobile.con
figuration import is deprecated. Suggest migrating to Nemo.Configuration

Sure you have seen this thread before posting:

Your help is welcome

Ok. It’s added to the list. Seems to be this issue: problem with app - token · Issue #116 · black-sheep-dev/harbour-sailhub · GitHub

maybe the developer @BlacksheepGER can share some insights. I do see he was last time active in January 2023 in this forum. He has also created the great Audiothek app - thank you for that as well!

Yes, thanks indeed for all the nice apps :slight_smile: It seem that not much has happened in the last few years, so I assume that maybe time/interest constraints are an issue?

According to ChatGPT there was change in Github API and it needs to modify Authorization header. It is here line 38, it should be "Authorization", "Bearer " + token instead of old "Authorization", "token " + token.

Added to the ticket you made on github.

But author of the app seems inactive and don’t care about the app as I posted the issue on github in summer and he made some contributions on his github in autumn.

That reminds me that I still wanted to create a PR because I added MPRIS support to Audiothek a while ago locally…

1 Like

Hmmm. Could be time issue? I was really busy in the last year and a half and didn’t get much done, either.

or maybe he doesn’t use SFOS anymore.

I tried to compile it in Sailfish SDK but it complains:
Cannot read /home/kuba/dev/sf/harbour-sailhub/extern/sailfishos-utils/compressor/compressor.pri: No such file or directory

Project ERROR: nemonotifications-qt5 development package not found

and when I want to install package libnemonotifications-qt5-devel in SDK:

root@SailfishSDK ~]# zypper install libnemonotifications-qt5-devel
Error building the cache:
[adaptation0|plugin:ssu?repo=adaptation0] Valid metadata not found at specified URL
History:

  • [|] Error trying to read from ‘plugin:ssu?repo=adaptation0’
  • Store credentials not received. Not connected to D-Bus server

Warning: Skipping repository ‘adaptation0’ because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data…
Reading installed packages…
‘libnemonotifications-qt5-devel’ not found in package names. Trying capabilities.
No provider of ‘libnemonotifications-qt5-devel’ found.

did you remember to get the submodules:

git submodule init

git submodle update

?

EDIT: I just compiled in SDK and it compiles just fine if you have the compressor submodule installed. I’ll look at fixing.

EDIT: I think the flow has changed a LOT since sailhub was built. You now have to build a github app and perform a LOT more steps to create access for it. It has nothing, I believe, to do with the token per se. In any case, I could not find the old method for creating tokens.

1 Like

I have at ine point started to work on GitHub integration for SFOS.

It contains account creation (so it’s available through Sailfish.Accounts), and some experimental integration of Github Notifications in Sfos socialcache and Event screen.

Interested developers are invited to have a look and maybe contribute so we can at least get the Accounts stuff into SFOS proper.

It needs rework/rebasing, possibly aligning with the open-sourced Nextcloud account stuff.

Also, due to GitHub requiring an ‘Application’ tied to an account, in the end Jolla would hopefully create and provide that like they do with other services.

I have not touched this stuff for a while but I think the Accounts part should be usable still:

6 Likes

Did you actually set up a github app? I took one look and ran away screaming while holding my head in both hands.

It’s been a while, but yes:


1 Like

Ah, I finally found it. There is a classic tokens pain you only find if you start creating another thing like an app or oath flow.

I’ve tested a build with ‘Bearer’ swapped in for ‘token’. this works. I didn’t go further since the app requires FAR too many permissions for my taste. Made a PR: Fix: move from token to Bearer in Authentication header by poetaster · Pull Request #117 · black-sheep-dev/harbour-sailhub · GitHub