Skip to content
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

CommandBar on Android raises exceptions which crash the app in debug #8751

Open
dr1rrb opened this issue May 11, 2022 · 0 comments
Open

CommandBar on Android raises exceptions which crash the app in debug #8751

dr1rrb opened this issue May 11, 2022 · 0 comments
Labels
area/commandbar Categorizes an issue or PR as relevant to CommandBar area/porting 🖨️ Categorizes an issue or PR as relevant for porting of WinUI code difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI kind/bug Something isn't working platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform

Comments

@dr1rrb
Copy link
Member

dr1rrb commented May 11, 2022

Current behavior

When we use the CommandBar in debug on Android we can get this exception:

System.InvalidOperationException: 'The Dependency Property [Color] is owned by [Microsoft.UI.Xaml.Media.SolidColorBrush] and cannot be used on [Uno.Toolkit.UI.NavigationBar]'

And if we use a PathIcon we also get:

System.InvalidOperationException: 'The Dependency Property [UriSource] is owned by [Microsoft.UI.Xaml.Controls.BitmapIcon] and cannot be used on [Microsoft.UI.Xaml.Controls.PathIcon]'

**** Both issues crash the app! **** (In debug only)

cf. details here unoplatform/uno.todo#231 (comment)

Expected behavior

  • App must not crash when we get an exception in InitializeComponent(), especially for a check like this.
  • We don't get those exceptions!

How to reproduce it (as minimally and precisely as possible)

No response

Workaround

Detach debugger ...

Works on UWP/WinUI

No response

Environment

No response

NuGet package version(s)

No response

Affected platforms

No response

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

@dr1rrb dr1rrb added kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels May 11, 2022
@jeromelaban jeromelaban removed the triage/untriaged Indicates an issue requires triaging or verification label Dec 2, 2022
@MartinZikmund MartinZikmund changed the title CommandBar on Android raise exceptions which crash the app in debug CommandBar on Android raises exceptions which crash the app in debug Jul 25, 2023
@MartinZikmund MartinZikmund added platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI area/commandbar Categorizes an issue or PR as relevant to CommandBar area/porting 🖨️ Categorizes an issue or PR as relevant for porting of WinUI code and removed difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels Jul 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/commandbar Categorizes an issue or PR as relevant to CommandBar area/porting 🖨️ Categorizes an issue or PR as relevant for porting of WinUI code difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI kind/bug Something isn't working platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform
Projects
None yet
Development

No branches or pull requests

3 participants