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

App will be Crash with an InfoBar and Publishing as Single File Option #7063

Closed
2 tasks done
ghost1372 opened this issue May 6, 2022 · 4 comments
Closed
2 tasks done
Labels
bug Something isn't working team-Markup Issue for the Markup team

Comments

@ghost1372
Copy link
Contributor

ghost1372 commented May 6, 2022

Describe the bug

If we have an InfoBar in MainWindow and publish it as a Single File (PublishSingleFile = true) App will not run and will crash.

i tested with visual studio debugger and i get

Exception thrown at 0x76C0F152 in App22.exe: Microsoft C++ exception: EEMessageException at memory location 0x0377EC8C.
Exception thrown at 0x76C0F152 (KernelBase.dll) in App22.exe: 0xE0434352 (parameters: 0x80131524, 0x00000000, 0x00000000, 0x00000000, 0x00AA0000).
Unhandled exception at 0x76C0F152 (KernelBase.dll) in App22.exe: 0xE0434352 (parameters: 0x80131524, 0x00000000, 0x00000000, 0x00000000, 0x00AA0000).

Steps to reproduce the bug

1.Create a New WinUI 3 Project
2.Change To Unpackaged Project
None
3. Add InfoBar on MainWindow

<Window
    x:Class="App1.MainWindow">
    <StackPanel>
        <InfoBar
                        Title="Up To Date"
                        IsClosable="False"
                        IsOpen="True"
                        Severity="Success" />
    </StackPanel>
</Window>

4.Publish Project as Single File (PublishSingleFile = true)
5.Run Published App

Expected behavior

App should run without any problems

Screenshots

No response

NuGet package version

WinUI 3 - Windows App SDK 1.0.3

Windows app type

  • UWP
  • Win32

Device form factor

Desktop

Windows version

Windows 11 (21H2): Build 22000

Additional context

Tested with WASDK 1.1.0-preview1, preview2 and preview 3
i reported this issue in wasdk repo but no one tracking this issue.
#7143

@ghost1372 ghost1372 added the bug Something isn't working label May 6, 2022
@ghost ghost added the needs-triage Issue needs to be triaged by the area owners label May 6, 2022
@ojhad ojhad added the team-Markup Issue for the Markup team label May 10, 2022
@ojhad
Copy link
Contributor

ojhad commented May 10, 2022

@RealTommyKlein Any ideas on what could be going on here?

@ghost ghost removed the needs-triage Issue needs to be triaged by the area owners label Aug 15, 2022
@beeradmoore
Copy link

@ghost1372 , any idea why this is closed? This is still an issue. Should we be focusing on any one specific issue of the duplicate/related issues instead?

@ghost1372
Copy link
Contributor Author

@beeradmoore
i reopened this issue here
#7143

@beeradmoore
Copy link

Thanks. I have gone and subscribed to that one now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working team-Markup Issue for the Markup team
Projects
None yet
Development

No branches or pull requests

3 participants