We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In .NET 9 invoking Toast on Android works fine but doing it on Windows throws an exception with a multi line error of:
Element not found. Element not found.
A Toast notification rather than an exception on Windows.
Clone the repo then build and run the app on Windows, Once it is running click the button and you should see the fault.
https://github.com/david-maw/Community-Toast.git
- .NET MAUI CommunityToolkit:9.1.1 - OS:Windows 11 - .NET MAUI: 9.0.10
No response
The text was updated successfully, but these errors were encountered:
We do not yet support .NET 9.
We are blocked from merging any PRs until we are able to merge our .NET 9 PR which is currently blocked by a bug in .NET MAUI.
Once the MAUI engineering team resolves this bug, we will be unblocked and can resume merging PRs for the Community Toolkit: dotnet/maui#25871
This Issue is fixed by #2215
Sorry, something went wrong.
Thanks, and sorry, I hadn't realized that .NET 9 wasn't supported yet.
Successfully merging a pull request may close this issue.
Is there an existing issue for this?
Did you read the "Reporting a bug" section on Contributing file?
Current Behavior
In .NET 9 invoking Toast on Android works fine but doing it on Windows throws an exception with a multi line error of:
Expected Behavior
A Toast notification rather than an exception on Windows.
Steps To Reproduce
Clone the repo then build and run the app on Windows, Once it is running click the button and you should see the fault.
Link to public reproduction project repository
https://github.com/david-maw/Community-Toast.git
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: