Skip to content

Conversation

@DevTKSS
Copy link
Contributor

@DevTKSS DevTKSS commented Jul 24, 2025

GitHub Issue (If applicable): closes #

PR Type

What kind of change does this PR introduce?

  • Refactoring (no functional changes, no api changes)

What is the current behavior?

if the user includes the Mobile target, he will get this comment added in his template, advising to uncomment/comment out the Packaged WinAppSdk target, but this seems (following this link) to be fixed 🎉 lets remove this? 🙃

What is the new behavior?

lets remove this? 🙃

PR Checklist

Please check if your PR fulfills the following requirements:

  • Associated with an issue (GitHub or internal)

Other information

While this particular issue is fixed, could the team quick check if there are other issues open (Backlog I think you call it?) that would still require us users to do anything on this profile and we might should have a comment to this there, but with some link update?

Internal Issue (If applicable):

Copilot AI review requested due to automatic review settings July 24, 2025 13:03
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR removes a temporary workaround comment from the launch settings template that referenced a resolved issue. The change removes guidance that instructed users to comment out the Packaged profile when using Mobile targets, as the underlying WinAppSDK debugging issue has been fixed.

  • Removes outdated comment block referencing a resolved GitHub issue
  • Cleans up conditional compilation directives for Mobile target scenarios

//#if (useWinAppSdk)
//#if (!useMsalAuthentication)
//#if (useMobile)
// Note: In order to select this profile, you'll need to comment the `Packaged` profile below until this is fixed: https://aka.platform.uno/wasdk-maui-debug-profile-issue
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just want to double check and confirm with @jeromelaban that this comment is indeed no longer needed

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe it is, but it has a tendency to come back after a few versions :) This is not the first time it got fixed on VS's side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants