There may be something going on with attachments on the server side. If you do capture the logs, please make a ticket. Attachments were broken for me too for a while.
Emoji support in Sailfish is limited, and black-and-white only. The box with cross means that the emoji in question isn’t included in the set Jolla provides (or that it’s a skin tone modifier). There are ways to install colored emojis in Whisperfish, please check the Whisperfish wiki for more info.
Sending and receiving attachments not working looks to be a IPv6+DNS issue, not a Whisperfish/Signal issue. That also explains the intermittent nature of the bug occurring or not. Please see this bug report for details - there’s a workaround for the issue, too, if you’re familiar with using the terminal.
I tried sending another picture recently, and I again experienced the same thing. Not working initially, then working when starting from ssh. I am experiencing a similar situation with Fernschreiber. Fernschreiber however gives an error “can’t get stat about the file” when it doesn’t work.
I now suspect that this is maybe something with my specific setup, something to do with permissions somehow?
I’ve symlinked my pictures folder (and other folders) from my home dir to my sdcard, so that I have a continuous backup. So far this has worked great. However when I go to share a picture in whisperfish and I choose “File system” I can only see my homedir, not the sdcard (I can see it if I start whisperfish from ssh). In the homedir, all folders (like pictures) are 0 byte files (but not when started from ssh).
Could the problem be that whisperfish doesn’t have access to the sdcard, so sharing a file from there would never work? Even though e.g. the image picker does see it?
Sounds familiar indeed. Could you test what happens if you devel-su ping cdn.signal.org from the command line? And if it does not work, does the same command with ping -4 cdn...?
I verified that sending an image was not working after starting whisperfish from the app drawer. Then I went to the terminal and tried to ping. This worked fine, and it pinged an ipv6 address. Then I tried to ping -4. This time it didn’t work, with the following error:
PING cdn.signal.org (52.222.139.33): 56 data bytes
ping: sendto: Network is unreachable
The same error occurs when I try to ping -4 google.com. I don’t know what this means.
But I think it’s more likely a permission problem than a network issue.
@d.geelen, sounds a lot like what direc85 talk about here Whisperfish - The unofficial SailfishOS Signal client - #587 by direc85
I’ve figured it out, so far as the attachments go. I added the RemovableMedia permission to the .desktop file and now I can see the sdcard when I go to browse ‘File System’ and sharing a picture from the picker also works and is shared properly.
For the network stuff I don’t quite know yet, but it looks like maybe ipv4 doesn’t work properly when roaming (not on wifi). But unlike the bug report by @direc85 I have never tried VoLTE yet.
FYI, I’ve added RemovableMedia to the privileges for the next release.
Thanks for sharing this, no wonder I couldn’t send pictures taken with Camera 
Since yesterday, @direc85 and I are working very hard on some very necessary features and fixes in Whisperfish.
You can follow our progress on the Brussels 2022 code sprint milestone and follow live on Matrix.
Good luck and all the best. Looking forward to Wisperfish 1.0.
Hi, very cool idea to have a hackathon! I see something on the issue list referencing a ‘share plugin’. What is it, I can’t find much info on it? Is it a way to integrate Whisperfish into the ‘share’ dialog in e.g. camera? Because that would be awesome 
Hi. Thank you for WP 0.6. I used it since several months. It works often very well and as expected. I only miss sometimes some pictures. Especially when they come in via a picture serie.
I’m looking forward to more versions and hope to see the first official version 1.0 soon.
Keep up the good work, rubdos and direc85 
This is so cool dudes!
Glad you enjoy it already. The pictures do already get downloaded and stored in the database, and almost half a year ago I started working on actually displaying them in the app. It’s a bit more difficult than I’d like it too, if it’s to be decent code. I might give it a go again if I can finish the message queue implementation that I now started.
Thank you all for your support!
Actually the share plugin (currently works only on SFOS 4.4) has already been released. It’s a separate RPM file, and you can download it from Openrepos. Making it work on SFOS 4.3 all the way down to 3.4 should be done during the hackathon, too!
And about the camera, there’s an in-app support for camera coming up for the next release, so stay tuned for that!
Ruben is also splitting Whisperfish and the share plugin into separate repositories, so it will be a lot easier to download the correct versions - determined by the Sailfish OS version installed.
Regarding the sqlite symbol conflict, have you tried building againt system sqlite instead of bundled, when building libsqlite-sys?
I’m sorry if this has already been covered, but I’m on mobile and couldn’t find any mentions of this (and unable to use the workaround).
When linking against a SQLite (or SQLCipher) library already on the system (so not using any of the bundled features), you can set the SQLITE3_LIB_DIR (or SQLCIPHER_LIB_DIR) environment variable to point to a directory containing the library. You can also set the SQLITE3_INCLUDE_DIR (or SQLCIPHER_INCLUDE_DIR) variable to point to the directory containing sqlite3.h.
Yes, we’ve tried against the system SQLcipher before. In fact, the reason that we started shipping our own, was is because of the conflict.
Meanwhile, you haven’t heard from us since the hackathon picture. We accomplished a lot of things, except for one: actually releasing it. Currently, time is a bit short, and I haven’t gotten around the few things I’d like to polish first. Soon™!
This is a huge release, thanks to the hackathon we did a month ago with @direc85 (see picture at Whisperfish - The unofficial SailfishOS Signal client - #595 by rubdos).
There’s a ton of useful changes for the users, and there’s also a lot of technical debt fixed that will make the next releases even more awesome. Diffstat since beta.9: 127 files changed, 11795 insertions(+), 5464 deletions(-) (and that’s huge)
Changes
This is quite a milestone. The next big milestone will be porting Rust 1.61 to SailfishOS, because that will allow us to further push the dependencies and implement all the new GroupV2 and sealed sending features more easily.
Beta 10 should become available the next few hours on OpenRepos automatically.
@flypig or any other moderator in here, is it an idea to allow me to edit the first post to update the change log? Wiki-style or just to remove the time limit?
Congratulations on the release. What a properly impressive set of improvements, I’m really looking forward to using it 
Would you be able to ping me a private message with some info to include in the newsletter (e.g. a short explanation of why Whisperfish is important; a description of the update and how your hackathon went; what your future plans are)? I can extract the info from your post here otherwise, but it’d be nice to have a little more context direct from you for users who aren’t so familiar with Whisperfish or Signal.
Unfortunately I don’t have the power to reset the timer. I can convert it to a wiki, but then anyone would be able to edit it. Would that still work?
