-
Notifications
You must be signed in to change notification settings - Fork 742
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
[Android] NavigationBar
PrimaryCommands unresponsive
#18506
[Android] NavigationBar
PrimaryCommands unresponsive
#18506
Comments
@agneszitte this one sounds kinda bad, we should investigate where this started happening from Perhaps @vatsashah45 can take a look? |
Closing this issue as it seems to be a local emulator error for the author, and not an actual uno issue. |
@morning4coffe-dev so if you are creating a new emulator, you are not able to reproduce the issue on your side for example? |
It seems related to #18498 as well |
The problem began with Uno.Sdk 5.4.0-dev.236 (it is not reproducible with Uno.Sdk 5.4.0-dev.234 or earlier versions).
Based on the versions differences between these two Uno.Sdk versions, it does not seem related to an Uno Toolkit change. I also can confirm that this is the same issue for #18498 as well |
@agneszitte, @vatsashah45, I did a quick round of tests as well and can reproduce this on both an emulator and an actual device with similar versions to the ones Agnès shared. |
@MartinZikmund as we discussed together, here is the sample app I created for a simple reproduction of the issue (using the blank preset + Toolkit). I conducted a quick check on the other platforms (except macOS), and it seems that the issue is indeed only Android-specific, as mentioned in this issue. You can find the sample app here: NavigationBarSampleApp.zip Based on my investigation, it looks like the issue might have originated from the changes introduced in PR #17860. I'll leave it to you to confirm my findings. |
@MartinZikmund would you know if this has been fixed? |
I can repro as long as the Material styles are not used alongside Toolkit. Interesting |
Following up on @kazo0's finding I could also only make the NavBar's AppBarButton work with Material. Then I tried removing Material entirely, at this point the issue is reproducible However then I removed the Icon property from the AppBarButton and the command was being triggered again. So it seems to be related to the Icon in Fluent in a way or another. It is not working with a BitmapIcon defined either. Next step would be to debug in here https://github.com/unoplatform/uno.toolkit.ui/blob/91c5efcb40ef385f98225c258ff60664c2735815/src/Uno.Toolkit.UI/Controls/NavigationBar/AppBarButtonRenderer.Android.cs#L167 I'll post my findings once that's done |
When using Material, the When not using Material (Fluent), the |
Another update, turns out its being invalidated when clicking on the button since fluent is changing the opacity of the icon OnPressed: these lines show the Icon foreground is being observed. Will be removing these and adding a test for the scenario |
Current behavior
When I try to put AppBarButton in PrimaryCommands, it becomes unresponsive, the Command and Click doesn't work. When I put it outside of NavigationBar, everything works as expected.
This seems to be a regression in the latest dev versions. I tested with
5.5.0-dev.40
and5.5.0-dev.50
, on both the issue appears.How to reproduce it (as minimally and precisely as possible)
NavigationBarRepro.zip
Nuget Package:
Uno.Sdk
5.5.0-dev.50
Affected platform(s):
The text was updated successfully, but these errors were encountered: