Xamarin Component throws System.NotSupportedException while creating a .xam package - c#

I am trying to upload a Xamarin Component by using xamarin-component.exe tool as written in this guide. While it is building the .xam package file, the command console is throwing the following error:
What is the problem? I am running it on windows. Is this related to machine permission?

I've found the reason for the error message.The file paths format I've given for build,libraries,samples in the component.yaml file was not in the specified format. Also the spaces between the build,libraries,samples's keys and their respective values should be maintained as per the component submission guide.Like this, build:
- src/samplecomponent.sln
libraries:
ios-unified: ../src/samplecomponent/bin/release/Awesome.dll

Related

The type initializer for 'Amazon.AWSConfigs' threw an exception

I'm trying to log in using AWS Cognito by running the app after building it in Unity.
I couldn't log in properly, and when I tried debugging, I found the phrase "The type initializer for Amazon.AWSConfigs' thread an exception."
This error occurs when executing the following code:
Amazon.CognitoIdentityProvider.AmazonCognitoIdentityProviderClient provider =
new Amazon.CognitoIdentityProvider.AmazonCognitoIdentityProviderClient(new Amazon.Runtime.AnonymousAWSCredentials(), regionTable[REGION]);
The app itself is built normally, but there seems to be a problem with logging in using AWS.
(I found this error in the PC and oculus environment.)
Some of the answers told me to modify the Config file. But I couldn't find the Config file. The location of this file was also unknown.
I found this answer "https://github.com/aws/aws-sdk-net/issues/310" but I couldn't apply this for me.
I found this Document "https://docs.unity3d.com/kr/2021.1/Manual/upm-config.html#upmconfig" but the Config file didn't exist in this path. My environment is Mac.
additionally,
I use AWS SDK called aws-sdk-net45-3.7.193.0.
UnityInitializer.AttachToGameObject(this.gameObject);
Amazon.AWSConfigs.HttpClient = Amazon.AWSConfigs.HttpClientOption.UnityWebRequest;
In this code, my Project Cannot understand UnityInitializer, HttpClient, and HttpClientOption.
What else changes are needed in order to mitigate the above issue.
I solved this problem.
The problem was that I was using IL2CPP as Script backend.
Simply using Script backend as Mono is one way. But my project had to use IL2CPP.
In order to use IL2CPP and use the Unity project using AWS Cognito, it is recommended that you:
Use .NetStandard2.0.
Use AWS SDK that is compatible with .NetStandard 2.0.
I used Unity 2020.3.19f version to use .NetStandard 2.0.
If you are using a URP project and there is an error in URP due to downgrade of Unity version, it is recommended that you act as follows.
Enter the Package folder for that project
Open Manifest.json and Package-lock.json files
Change the Render Pipeline version to 10.8.1 (for 2020.3.19f1 version. I didn't experiment with other versions.)
Reference found to resolve this issue.
https://forum.unity.com/threads/issue-with-system-configuration-configurationmanager-get_appsettings-on-ios.1026877/#post-6656764
https://docs.aws.amazon.com/ko_kr/mobile/sdkforunity/developerguide/aws-unity-sdk.pdf
https://docs.unity3d.com/Packages/com.unity.render-pipelines.universal#10.8/manual/index.html

Error Disk image malformed while building WinUI 3 c# project

I am attempting to build my first WINUI 3 Hello World app following the process in https://learn.microsoft.com/en-us/windows/apps/winui/winui3/create-your-first-winui3-app?tabs=desktop-csharp
After following all the steps without error I build and run resulting in a DEP0600 error.
I am using VS 2019 version 16.10.4, C# Windows 10.0.19042 I am also using Project Reunion v 0.8.1
I deleted the AppData\Local\Microsoft\VisualStudio files as suggested and now get
I tried your suggestion and now get
System.Reflection.TargetInvocationException Inner exception: Class not
registered REGDB_E_CLASSNOTREG
Any suggestions how to get this barebones example to run?

Error hresult 0xc8000222 in Net Framework installation c# setup file

I create a set up file. I attach .Net Framework 4 client profile along with the setup file creation.I am trying to install it on other machine it will not in work properly. It will produce error
error hresult 0xc8000222
Follow the steps here..........
I just googled it....try that next time....
https://answers.microsoft.com/en-us/windows/forum/all/problem-installing-net-framework-4-hresult/bfac5cac-10e8-4eb9-b87d-64a3266522f7

Xamarin Push Notifications Build Error

I am implementing push notifications within an application using the Azure Messaging component from Xamarin - iOS only.
I have been able to successfully build, deploy to a device, and test
locally.
The component is installed using the Nuget package for the component.
However, when I check the changes into source control and try to
build on our build server
I receive the following error message:
MTOUCH: error MT1304: The embedded framework
'WindowsAzureMessaging.framework' in
/Users/Clinician/TeamCity/buildAgent/work/b535d319c25da2ee/Frameworks
/packages/Xamarin.Azure.NotificationHubs.iOS.1.2.5.2/lib/Xamarin.iOS10/Xamarin.Azure.NotificationHubs.iOS.dll
is invalid: it does not contain an Info.plist.
I haven't been able to find a lot of information about the MT1304 error.
Has anyone else encountered this or have any suggestions on how to resolve?

Windows store app fails AppContainerCheck

I'm getting the below error when I try to run the app certification test on my windows 8.1 app. I've looked around for a while and can't seem to find any solutions for this. The app is written in C#/xaml which I wasn't aware even had a linker.
I'm hoping that someone can guide me in the right direction on how I should start to investigate an error like this as web searches have thus far failed me
Binary analyzer
•Error Found: The binary analyzer test detected the following errors:
◦File [MyTabletApplication.exe] has failed the AppContainerCheck check.
•Impact if not fixed: If the app doesn’t use the available Windows protections, it can increase the vulnerability of the customer's computer to malware.
•How to fix: Apply the required linker options - SAFESEH, DYNAMICBASE, NXCOMPAT, and APPCONTAINER - when you link the app. See links below for more information:
If you are using Visual Studio 2015 and this is a new solution/project make sure the 'Compile with .NET Native tool chain' check box is cleared in the startup project properties in the Release configuration.

Categories