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

Unity 2019 Android crash: library "Crypt32" not found #1431

Closed
bartofzo opened this issue Oct 15, 2019 · 5 comments
Closed

Unity 2019 Android crash: library "Crypt32" not found #1431

bartofzo opened this issue Oct 15, 2019 · 5 comments

Comments

@bartofzo
Copy link

bartofzo commented Oct 15, 2019

I'm trying to run a Unity project on an Android device with the AWS .net SDK.

But when using the Cognito Identity service, the app crashes with the following message logged:

10-15 14:39:58.907 12657 12765 E Unity   : Unable to find Crypt32
10-15 14:39:58.908 12657 12765 W Unity   : Plugins: Couldn't open Crypt32, error: dlopen failed: library "Crypt32" not found

I've cloned this repository and built the .NET Standard solution. Then added the neccessary DLL's to my project.

Everything works fine inside the Unity editor and it also works for iOS builds. However on Android the app crashes.

The error occurs for both IL2CPP and Mono backends on Android. Also occurs on .NET standard 2.0 and .NET 4.x API compatibility levels.

Unity version is 2019.2.9f1

Thanks.

@klaytaybai
Copy link
Contributor

What is the Android version?

@bartofzo
Copy link
Author

Android 9 on a Samsung Galaxy S8 (SM-G950F)

@bartofzo
Copy link
Author

Is there anyone using the SDK with Unity 2019 that doesn't have this problem? Wondering if it's as simple as including the DLL with the project. Strange that it does work on iOS and MacOS.

@bartofzo
Copy link
Author

Found out the crash was not due to this error. Although the message still gets logged, cognito and lambda seem te work correctly, so I'm assuming it's harmless.

@advantage-software
Copy link

Found out the crash was not due to this error. Although the message still gets logged, cognito and lambda seem te work correctly, so I'm assuming it's harmless.

What was it due to?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants