Troubleshooting
Android: the SDK AAR does not resolve
Section titled “Android: the SDK AAR does not resolve”Registry install (default). The Android SDK (com.byterialab:alphyn-sdk) resolves from the Alphyn
package registry through the custom Main Gradle Template, so a failed Android build usually means one
of:
- Custom Main Gradle Template is off. Enable it under Player Settings > Publishing Settings so
Unity uses
Assets/Plugins/Android/mainTemplate.gradle. ALPHYN_REGISTRY_KEYis not set in the build environment (a 401, or “could not resolve com.byterialab:alphyn-sdk”). See SDK Registry Access.mainTemplate.gradleis not wired. Re-runalphyn-cli integrateand confirm withalphyn-cli doctor.
Offline install. If you used the self-contained plugin, ensure alphyn-sdk.aar is in
Assets/AlphynSDK/Plugins/Android/.
iOS: xcframework Not Found
Section titled “iOS: xcframework Not Found”The iOS Alphyn.xcframework is bundled in the plugin on both the registry and the offline paths.
Ensure it is in Assets/AlphynSDK/Plugins/iOS/.
JNI Errors on Android Device
Section titled “JNI Errors on Android Device”Check that the native libraries are included for your target architecture.
SDK Not Initializing
Section titled “SDK Not Initializing”Android:
- Check Android logcat for detailed errors
- Ensure minimum API level is 26+
iOS:
- Check Xcode console for detailed errors
- Ensure minimum iOS version is 15.0+
- Verify the xcframework is properly linked in Xcode project settings
Editor Testing
Section titled “Editor Testing”The SDK provides mock data in Unity Editor. Deploy to Android device or iOS device for real security detection.