[Xamarin Android][Xamarin.iOS] API not working anymore since 1.1.0 – CryptographicException in LoadEcPrivateKey (CryptoUtils.cs)

[jdufaud]

Hello team,

Since updating to version 1.1.0, our Xamarin Android and Xamarin iOS integration no longer works.
After investigation, the problem appears to be related to the cryptography code in CryptoUtils.cs, specifically during the LoadEcPrivateKey call.

We are targeting .NET 9.

An easy way to reproduce:
• Open the attached test project
• Call: await auth.Login(username, password);

This fails systematically on Android with a CryptographicException.

Could you please review this issue?

[sk-keeper]

Thank you for reporting this issue. We were able to duplicate it.
Keeper .Net SDK 1.1.0 adds net8 target. It lets us get rid of BouncyCastle dependency. Net8 API contains all cryptographic functions our application requires.
Unfortunately, .NET 8 on Android behaves slightly differently from the desktop implementation.
It seems that Android requires both private and public key components to import a private key.
We are going to fix this issue.
Meanwhile you can force your application to use netstandard2.0 target of Keeper.Sdk library.
Replace the default Keeper.Sdk package reference with the following AI generated text

	<ItemGroup>
          <!-- Add a compile-time reference to the netstandard2.0 DLL -->
          <PackageDownload Include="Keeper.Sdk" Version="[1.1.1]" />
          <Reference Include="Keeper.Sdk">
            <HintPath>$(NuGetPackageRoot)keeper.sdk\1.1.1\lib\netstandard2.0\KeeperSdk.dll</HintPath>
            <Private>true</Private> <!-- copy to output -->
          </Reference>
          <PackageReference Include="Portable.BouncyCastle" Version="1.9.0" />
          <PackageReference Include="Google.Protobuf" Version="3.28.3" />
	</ItemGroup>

This solution works with Android Maui applications

[jdufaud]

Thanks, this workaround works.