-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check if OS notifications work correctly on Windows #1411
Comments
I can look into this. |
Depends on #1383 |
@mrblue313 Any update on that task? |
I am working on it. Will give an update in the following days. |
Giving an update on the current status of this. Testing the current solutionI have been testing using Clear-net and Windows 11. The following matrix was considered:
These were my findings:
For instance, in the case of the offerbook, this is what it displays (not very indicative):
Same when you click on the three dots icon: And in the system settings:
... and even the notification bell lights up! Other things I have noticed (outside the notification framework layer, but still find worth mentioning):
To compare, this is an example of how notifications show in Element. They have the user image, longer text, etc. Investigation
Suggested next stepsI suggest I test again when the binary is ready to be generated and revaluate the situation. But if we are able to set the app name correctly + image, and with some enhancements on the title/message that we pass adhering to the constraints seen, I would continue using AWT. Another thing I am concerned about is that Windows Toast Notifications is only available from Windows 10, so if we want to ensure compatibility with any Windows version, that would still not be a good solution. |
Yes agree.
It should work now to build a binary for windows.
Yes we should increase maxLenght
Not by design. Probably better to not send a notification in that case, but low prio to fix IMO.
We could show a popup (with dont show again) with more info. When un-ignore all msg are shown again. Its just a local filtering.
That would be nice but I think thats a challenging task to get on all OS working. You could add an issue as a future feature request. Thanks for all the testing. Can you try if you can get a windows binary running to see if icon / name works as expected? |
Sure, I'll get back with this. |
I have tested with the binary. Presenting the findings. After generating the binary, I am taking the installer from: It looks like the content in the folders inside images is swapped? in the I have tried both of them. The bisq2/build-logic/packaging/src/main/kotlin/bisq/gradle/packaging/jpackage/PackageFactory.kt Line 44 in 0d05a7e
This only happens in the notification panel, the rest of places get "Bisq2". I have also noticed that we are using a different (old) version of the logo in the task bar. This looks inconsistent with the one appearing in the process window, which is the newer one. I can update those icons in a PR soon. Not sure if related to our One more thing to consider, and that I have noticed, (independent from the build itself) is the flushing of messages when the user connects/starts up the app. At the moment, the user needs to wait/dismiss for every single notification. If the messages are more than 3 o 4, that might not feel like a good experience. I have created an issue for this #1546. |
@mrblue313 Can you try to fix the issues with the image and title? If no solution found @alvasw might have an idea. |
Yes, that's what I used.
Sure, I will continue looking into it. |
Do you know when did it worked last (with the installed binary)? That would help to identify the commit that broke the notifications. |
I have never seen it working before. The first time I tested it was around the 16th of Dec. |
Oh my bad, I thought it worked before we updated the packaging module. @HenrikJannsen Have the notifications ever worked on Windows? I haven't read or worked on notification code before. |
I never managed to build a binary for Windows. So I could not test it with a binary to see if the icon and app name is correct. |
On Windows we use AwtNotifications. We should figure out if there is a native solution which works well on all commonly used Windows versions. If not feasible we need to check if AwtNotifications works sufficiently well.
The text was updated successfully, but these errors were encountered: