-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Deployment error 0700 when building as Windows app #3542
Comments
@marwalsch does this work with the non-Blazor MAUI template? |
I have the same problem with the non-Blazor MAUI template. |
@Eilon I can't seem to be able to reproduce with the Blazor template any more. Might this have been silently fixed in the latest patch release of the VS2022 preview? |
If it's just the splash screen, I happened to see what I think was the exact same error in another app, and this was the workaround:
And so maybe this was a bug in some version of the templates, that has since been fixed? Can anyone reproduce this in the latest templates? I've done a lot of publishing tests with the latest templates and haven't seen this issue at all. |
Can't reproduce anymore on neither the Blazor nor XAML template; tested on Android Simulator on windows. I'll leave the issue open in case @dos-ise has additional feedback. |
You are correct. Fixing the file name in the Package.appxmanifest solved the problem for me. Thanks alot |
OK, closing this. This might have been a bug in the template at some point but it looks like it's fixed for everyone! |
This error still occurs for me. As far as I know, I'm using the latest preview (or at least it says it's up to date when I try to update it). |
@ColonelDuddits does the error go away if you do the workaround mentioned above in the appxmanifest file? |
@Eilon I've just got this error in a new MAUI project. I created it using the Visual Studio 2022 (17.1.0 Preview 6.0) add project dialog, adding to an existing solution, as @ColonelDuddits mentioned. The workaround didn't work for me, so I did a bit more digging. I noticed that if I opened the csproj file straight after creation, the <ItemGroup>
<!-- App Icon -->
<MauiIcon Include="Resources\appicon.svg" ForegroundFile="Resources\appiconfg.svg" Color="#512BD4" />
<!-- Splash Screen -->
<MauiSplashScreen Include="Resources\appiconfg.svg" Color="#512BD4" />
<!-- Images -->
<MauiImage Include="Resources\Images\*" />
<!-- Custom Fonts -->
<MauiFont Include="Resources\Fonts\*" />
</ItemGroup> rewritten to: <ItemGroup>
<!-- App Icon -->
<AndroidResource Include="Resources\appicon.svg" ForegroundFile="Resources\appiconfg.svg" Color="#512BD4" />
<!-- Splash Screen -->
<AndroidResource Include="Resources\appiconfg.svg" Color="#512BD4" />
<!-- Images -->
<MauiImage Include="Resources\Images\*" />
<!-- Custom Fonts -->
<MauiFont Include="Resources\Fonts\*" />
</ItemGroup> My gut feeling was that some extension was misbehaving, so I disabled the obvious ones I could see in the list: Xamarin.Android SDK, Xamarin.Apple SDK and Uno Platform Solution Templates. After disabling these, the csproj no longer got rewritten and everything published fine after creating a new project. Unfortunately (for testing purposes), everything still worked fine after I re-enabled the extensions, so I can't troubleshoot further, but perhaps this might help someone else. |
@mikegoatly - that definitely doesn't look right and shouldn't happen. Can you file that in a new issue so that we can track it? |
Same problem here. My .csproj contains these lines:
While my Package.appxmanifest file contains this: When I try to deploy the app on my Windows Machine, I get this: "DEP0700: Fehler beim Registrieren der App. [0x80073CF6] AppxManifest.xml(33,27): Fehler 0x80070003: Das Paket "8496B0C3-46D4-4C37-8FEF-A012F717C268_9zz4h110yvjzm" kann nicht installiert oder aktualisiert werden, da das Begrüßungsbildschirmbild [appiconfgSplashScreen.png] nicht geladen werden kann. Überprüfen Sie, ob das Paket ein Bild enthält, das als Begrüßungsbildschirm für die Anwendung verwendet werden kann, und ob das Paketmanifest auf den richtigen Speicherort des Begrüßungsbildschirmbilds im Paket verweist." (sorry for german translation) I did a search for *splash*.png within the bin/Debug folder and found a couple of appiconfgSplashScreen images right within the root folder that also contains all compiled DLLs. They follow this naming-scheme: appiconfgSplashScreen.scale-[nnn].png There are 5 of them:
For testing purposes, I edited the Package.appxmanifest file and removed the folder from the file reference:
Now the app gets deployed and executed. However, no splash screen rendered. Also I noted, that every other appearance of any image such as the Logo or the Tile also reference respective generated PNGs within the Assets folder that does not seem to exist. Thus, when executed, the apps' icon in the taskbar is also empty. When I remove the "Assets" folder reference in the properties, the taskbar shows the correct image. Also, I didn't find out, what setting is responsible for the windows' titlebar icon on the top left. [UPDATE] I just updated my maui workloads to preview 12 and now the AppIcon as well as the SplashScreen are deployed to the Assets subfolder. |
I have also been experiencing this problem. I am on the latest preview build. I relocated an included project to a different folder and that is when the problem started. I was able to resolve the issue in the same way that @Mephisztoe resolved the problem - by removing the reference to the Assets/ folder. |
I found the same issue and workaround as @Mephisztoe and @MichaelLant after upgrading to VS 2022 17.2.0 preview 1 / MAUI preview 13 from the latest preview of VS 2022 17.1.0 and MAUI preview 12. <ItemGroup>
...
<!-- Raw Assets (also remove the "Resources\Raw" prefix) -->
<MauiAsset Include="Resources\Raw\**" LogicalName="%(RecursiveDir)%(Filename)%(Extension)" />
</ItemGroup> (Btw, I needed to explicitly update the templates using |
Folks - if you're having any issues please make sure there is an open issue tracking it. This issue is closed and is unlikely to get a response from the dev team. |
Description
When using the Blazor bindings template, attempting to run the app on a windows machine throws an error complaining about a missing splash screen. The package name is a cryptic string.
Possibly related issue.
Steps to Reproduce
Version with bug
Preview 10 (current)
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
Windows 10.0.17763.0
Did you find any workaround?
No.
Relevant log output
The text was updated successfully, but these errors were encountered: