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

Getting not implemented warning issue. #19576

Open
speed2048 opened this issue Feb 22, 2025 · 5 comments
Open

Getting not implemented warning issue. #19576

speed2048 opened this issue Feb 22, 2025 · 5 comments
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification

Comments

@speed2048
Copy link

Current behavior

When I compile a Uno Project I get the following error warning message in the error list.

Severity Code Description
Warning (active) Uno0001 This member or type is not implemented and will fail when invoked.

According to #10436, this was supposed to be fixed.

Expected behavior

No warning message should be displayed as it was fixed the #10436.

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

No response

Workaround

None, but calls work on linux/Windows desktop, however does not work the same on osx. Will be creating another ticket once I can provide some code.

Works on UWP/WinUI

None

Environment

No response

NuGet package version(s)

No response

Affected platforms

Windows (WinAppSDK)

IDE

Visual Studio 2022

IDE version

Version 17.13.0

Relevant plugins

No response

Anything else we need to know?

No response

@speed2048 speed2048 added difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification labels Feb 22, 2025
@jeromelaban
Copy link
Member

Thanks for the report. This particular method is implemented, but is still marked as not implemented if running on some platforms:

[NotImplemented("__IOS__", "IS_UNIT_TESTS", "__WASM__", "__NETSTD_REFERENCE__")]
public void Exit()
{
if (this.Log().IsEnabled(LogLevel.Warning))
{
this.Log().LogWarning("This platform does not support application exit.");
}
}

While this is technically correct, it may be of interest to change it to "not supported" in the future so that it can be displayed as such by intellisense. At this time though, because of the way uno changes runtimes, it's not clear how the implementation can be made, so we're relying on NotImplemented.

@speed2048
Copy link
Author

Thank you for the explanation, so this Exit call should work on maccatalyst? If it is I will be create a new issue.

@jeromelaban
Copy link
Member

@speed2048 no, __IOS__ is defined for is not implemented for Mac Catalyst. Historically, iOS apps should be exiting themselves, this was an antipattern, it's likely to be the same for Catalyst. At this time, the behavior is to close the app when the last window is closed.

I wonder though, do you need Catalyst specifically, or would net9.0-desktop running on macOS be sufficient?

@speed2048
Copy link
Author

Hi Jérôme

What I am trying to do is save windows screen positions like in #18338 when I do a File Exit or Close application. This works as advertised except all frameworks except mac Catalyst and I understand why now. Exit Will not execute the callback defined in app.xaml.cs.

I have tried to use net9.0-desktop on MacOS and at this time it just shows a blank screen. So at this time would prefer to use catalyst framework.

Question:

Is there an alternative to get screen coordinates from MainPage. As I cannot see away to do this outside of App.xaml.cs.

Regards,
Bob

@jeromelaban
Copy link
Member

I see. @MartinZikmund may know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification
Projects
None yet
Development

No branches or pull requests

2 participants