Amazing, thank you so much!
3 Likes
What a great releasenote in all assets! Congrats!
Thank you for your work! But unfortunately I experience a strange issue: after updating I don’t have any contact name anymore in Whisperfish. Enabling the “prefer device contact” option doesn’t help, manually linking the contact says “no contacts”. 
5 Likes
This is lovely, especially on this very unique day.
Huge thanks!
Thank you Ruben for cleaning up the final pieces and preparing the release! This is one of the bigger releases in terms of shearing technical debt off, I think, and provides a good base for future work!
PS. I’m already running the next set of experimental stuff, and it’s looking good! As always, stay tuned!
10 Likes
Thanks for reporting. That sounds like a permission problem, but we’ll have to check.
As a reminder, that feature was a hotfix/workaround for broken profile sync waaay back, so in theory it shouldn’t be needed anymore. But, it looks like it’s a wanted feature in its own right, so we should get it fixed!
2 Likes
Hi, after losing my registration due to new primary android device, i was waiting for the registration fix. Tried to do it now (after deleting cache/config/local data) but it fails after the qr code is scanned (Error. The configuration of the signal client failed). In Android it shows as device associated. What is the procedure to register whisperfish as secondary?
1 Like
We’ll have to exercice our patience a bit more 
Or perhaps we do something wrong.
XA2 Dual 5.1.0.11
Failed to register as secondary device here too.
QR Seems ok in signal but WP has the same problem.
(I removed these files/folders before every new attempt)
rm -rf /home/defaultuser/.local/share/harbour-whisperfish /home/defaultuser/.config/harbour-whisperfish /home/defaultuser/.local/share/be.rubdos/harbour-whisperfish /home/defaultuser/.config/be.rubdos/harbour-whisperfish /home/defaultuser/.cache/be.rubdos /home/defaultuser/.config/be.rubdos /home/defaultuser/.local/share/be.rubdos
defaultuser@SfEr ~ [2]> harbour-whisperfish
Creating new config path…
Creating empty config file…
Creating empty QSettings file…
Creating new storage path…
Creating storage and db folders…
Production mode configured!
thread ‘main’ panicked at /home/rsmet/rpmbuild/BUILD/rustc-1.89.0-src/library/std/src/thread/local.rs:281:25:
cannot access a Thread Local Storage value during or after destruction: AccessError
note: run withRUST_BACKTRACE=1environment variable to display a backtrace
defaultuser@SfEr ~>
[defaultuser@SfEr ~]$ RUST_BACKTRACE=1
[defaultuser@SfEr ~]$ harbour-whisperfish RUST_BACKTRACE=1
error: unexpected argument found
[defaultuser@SfEr ~]$ harbour-whisperfish
Production mode configured!
thread ‘main’ panicked at whisperfish/src/worker/client.rs:3612:70:
calledOption::unwrap()on aNonevalue
note: run withRUST_BACKTRACE=1environment variable to display a backtrace
Well, manual linking is not needed as a wanted feature (for me) - I just tried it. But showing names in Whisperfish is one 
Thanks for taking care!
Yeah, at least the previous, experimental build still is able to register just fine, so it looks like we did something funny with merging it… We’ll look into it in a day or two, so I’m afraid it’s going to take a little longer to get Whisperfish on your new (or current) phones.
1 Like
Yep, I get that too… And I am soo glad you posted so I didn’t have to work out what and how to describe it! 
Would an output with the debug package help or did you already spot the bugs?
If an experimental build would get the user over the registration hurdle and then be able to use beta42 i would call it a workaround Are the experimental builds available for download?
— edited
I mean the linking failed … The android device is primary.
I believe that:
- Registration was probably not broken, but we failed to repeat that you need to disable your registration lock if you already have a Signal account on an official Signal app: Frequently Asked Questions · Wiki · Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab.
- Linking was indeed broken because a bunch of other stuff got merged that got some code path confused. Experimental build which should fix this, but it’s not tested. New logs would be appreciated, if e.g. @ric9k could test
Don’t forget to reset your Whisperfish before trying again!
8 Likes
We have everything we need to reproduce the issue, thank you for asking! As Ruben just wrote, I may have assumed one bug, but skipped the registration lock since I haven’t tested with it yet - and it’s indeed a known issue that it breaks Whisperfish registration attempts.
5 Likes
[defaultuser@Fairphone4 ~]$ rm -rf ~/.local/share/be.rubdos/harbour-whisperfish ~/.config/be.rubdos/harbour-whisperfish
[defaultuser@Fairphone4 ~]$ harbour-whisperfish
Creating new config path…
Creating empty config file…
Creating empty QSettings file…
Creating new storage path…
Creating storage and db folders…
Production mode configured!
thread ‘main’ panicked at whisperfish/src/worker/client.rs:3612:70:
called Option::unwrap() on a None value
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
^CCalling app.quit() on DBus.
[defaultuser@Fairphone4 ~]$ harbour-whisperfish
Production mode configured!
^CCalling app.quit() on DBus.
The original Signal app is available on the C2 phone
I already announced in Helsinki that I’ll be showing up here, soon enough
That experimental build did resolve the linking issue (for a secondary device) for me after deleting the config files listed in the FAQ and subsequently installing that experimental rpm.
1 Like
Thank you @rubdos and @direc85 !
The Experimental build seems to work here on XA2 Dual 5.1.0.11.
Linking a secondary device is back.
No need to start and stop AAS anymore.
Friends and family are back in Sailfish through WP. Beautiful!
Would logs (command line + journalctl, I suppose) still be of use or, as @direc85 said, not anymore atm?
2 Likes
Update: after some while (realized it now) all Signal contact names are back again! 
3 Likes
I had the same issue…