Open
Conversation
Context: 06f4f80 Context: unoplatform/uno.extensions#3022 Context: microsoft/microsoft-ui-xaml#8723 Build and run `Chefs.csproj` for e.g. net10.0-desktop and Native AOT while using Uno 6.6.0-dev.3: sed -i '' 's/"Uno.Sdk": ".*"/"Uno.Sdk": "6.6.0-dev.3"/g' global.json git clean -xdf Chefs{,.Api} dotnet publish -c Release -r osx-x64 -f net10.0-desktop -p:TargetFrameworkOverride=net10.0-desktop \ -bl Chefs/Chefs.csproj -p:UseSkiaRendering=true -p:SkiaPublishAot=true \ -p:IlcGenerateMapFile=true -p:IlcGenerateMstatFile=true -p:IlcGenerateDgmlFile=true -p:IlcGenerateMetadataLog=true \ -p:EmitCompilerGeneratedFiles=true -p:CompilerGeneratedFilesOutputPath=`pwd`/_gen Chefs/bin/Release/net10.0-desktop/osx-x64/publish/Chefs From the launch screen: 1. Click **Skip** 2. Click ** Sign in with Apple** 3. Click **❤️Favorites** in the left-hand pane 4. Click the **My Cookbooks** tab 5. Click the **➕Add** floating-action-button (bottom-right) 6. Leave the *Cookbook name* field blank. 7. Click the **Create cookbook** button. The problem is that the dialog which is shown is *empty*: > (no content here) > **[Close]** ![Empty error dialog][0] The app log output contains: fail: Uno.UI.DataBinding.BindingPropertyHelper[0] The [Title] property getter does not exist on type [Chefs.Business.Models.DialogInfo] fail: Uno.UI.DataBinding.BindingPropertyHelper[0] The [Content] property getter does not exist on type [Chefs.Business.Models.DialogInfo] As with commit 06f4f80, the problem is due to missing reflection metadata, and as with 06f4f80, there are "two" fixes, but really only one fix: 1. Add `[Microsoft.UI.Xaml.Data.BindableAttribute]` to the type indicated in the `fail` message: `DialogInfo`. 2. Add `[System.Diagnostics.CodeAnalysis.DynamicDependency]` to the constructor for all properties present in the type. (1) is the easy solution, but as seen in 06f4f80, this causes build errors when the type contains `init` or `required` properties *and* the app targets WinRT, due to microsoft/microsoft-ui-xaml#8723. Thus (2) is the only viable solution, tedious as it is. With this fix in place the error dialog is now displayed as: > **Error** > Please write a cookbook name and select one recipe. > **[Close]** ![Error dialog with content][1] [0]: https://private-user-images.githubusercontent.com/155958/541582643-59b816c3-b01a-4c25-a6b1-2977fc0ab573.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzA2Njg5NTQsIm5iZiI6MTc3MDY2ODY1NCwicGF0aCI6Ii8xNTU5NTgvNTQxNTgyNjQzLTU5YjgxNmMzLWIwMWEtNGMyNS1hNmIxLTI5NzdmYzBhYjU3My5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMjA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDIwOVQyMDI0MTRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1lNTkyMDAxODBjN2VkZGE4ZjRhZjg2Y2Q0MWRhNzBiNzRiYzU1MGM4YWNkNmY5OGE4ODllMDNiOWZlZjA0MTQ0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.xkdLy2wy4pY3kEgX33v76v5AwUwWGw_fj4MSXO6WdqE [1]: https://private-user-images.githubusercontent.com/155958/541582597-0b152753-b204-4cb8-9cd8-d17df7a8e5de.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzA2Njg5NTQsIm5iZiI6MTc3MDY2ODY1NCwicGF0aCI6Ii8xNTU5NTgvNTQxNTgyNTk3LTBiMTUyNzUzLWIyMDQtNGNiOC05Y2Q4LWQxN2RmN2E4ZTVkZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMjA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDIwOVQyMDI0MTRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kZDZlODVjNGFiZDY2YzhiZDcwYzIxYTM1NzI5YzA0NjAwODY3YTk4M2VmZjQxMGNlY2Q3NDRhODVhZWFlMjY1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.6rYPKy5v42mIfqOEAETbOlAKfHuZI0WVtQKaU4ttDAw
4f10224 to
0e2c939
Compare
rajamatt
approved these changes
Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context: 06f4f80
Context: unoplatform/uno.extensions#3022
Context: microsoft/microsoft-ui-xaml#8723
Build and run
Chefs.csprojfor e.g. net10.0-desktop and Native AOT while using Uno 6.6.0-dev.3:From the launch screen:
The problem is that the dialog which is shown is empty:
The app log output contains:
As with commit 06f4f80, the problem is due to missing reflection metadata, and as with 06f4f80, there are "two" fixes, but really only one fix:
Add
[Microsoft.UI.Xaml.Data.BindableAttribute]to the type indicated in thefailmessage:DialogInfo.Add
[System.Diagnostics.CodeAnalysis.DynamicDependency]to the constructor for all properties present in the type.(1) is the easy solution, but as seen in 06f4f80, this causes build errors when targeting WinRT due to microsoft/microsoft-ui-xaml#8723.
Thus (2) is the only viable solution, tedious as it is.
With this fix in place the error dialog is now displayed as:
GitHub Issue (If applicable): #
PR Type
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Runresults.Other information
Internal Issue (If applicable):