This plan does not support using a custom splash. Please revert to the default splash.
This error will occur when trying to customize the Hybrid application's startup splash screen without a paid plan. You can view licensing options here:
You can restore the default splash using this image:
To build this project, the following workloads must be installed: android
This error occurs when the android workload is not installed.
Run dotnet workload install android from the command prompt.
To build this project, the following workloads must be installed: wasm-tools
This error occurs when wasm-tools are not installed.
Run dotnet workload install wasm-tools from the command prompt.
DEP0700: Registration of the app failed. [0x80073CF6] AppxManifest.xml(34,27): error 0x80070002: Cannot install or update package [PACKAGE] because the splash screen image [splashSplashScreen.png] cannot be located. Verify that the package contains an image that can be used as a splash screen for the application, and that the package manifest points to the correct location in the package where this splash screen image can be found.
This error can occur when the package is locked. Either wait a minute and rebuild or change the GUID of the project inside of the Hybrid Client csproj file.
System.IO.FileNotFoundException: 'Could not load file or assembly '.../Xamarin.HotReload.Contracts.dll' or one of its dependencies.'
and
System.IO.FileNotFoundException: 'Could not load file or assembly '.../Microsoft.VisualStudio.DesignTools.TapContract.dll' or one of its dependencies.'
The solution for these errors is to disable Hot Reload while debugging or disable Common Language Runtime Exceptions.
Go to Tools -> Options -> Debugging -> XAML Hot Reload -> Uncheck Android and iOS (.NET MAUI)
System.AggregateException: 'One or more errors occurred. (Only one usage of each socket address (protocol/network address/port) is normally permitted.)'
Application works in Debug mode but fails in Release mode configuration
Wisej.NET Hybrid Projects do not support trimming, linking or Ahead-of-Time (AOT) compilation at the moment. Please ensure all of these features are disabled when compiling a release build.
If your .NET MAUI iOS app or ARM64-based Mac Catalyst app works correctly as a debug build but then crashes as a release build, try enabling the interpreter for your app's release build. It may be that your app, or one of its libraries, uses a feature that requires the interpreter.
Application Stuck when All Common Runtime Exceptions enabled
Ensure Options > General > Just My Code is enabled.
"ALToolValidate" task was not given a value for the required parameter "FilePath"
