Command upload unity-android Failing With Embedded NDK Tools

[troysteinbauer]

Describe the bug

Using Bugsnag Unity v8.5.0 and the new auto symbol uploads feature fails during NDK version check. It appears it attempts to identify the version via substringing the path, which appears to not work when running an embedded version of the NDK.

[FATAL] unable to determine ndk version from /Applications/Unity/Hub/Editor/6000.0.35f1/PlaybackEngines/AndroidPlayer/NDK

Steps to reproduce

1. Install Unity 6 via Unity Hub, including Android with NDK and SDK Tools bundled.
2. Install Bugsnag Unity v8.5.0 and compile project
3. See error during upload unity-android command

Environment

• bugsnag-cli version: v2.9.1
• bugsnag-unity version: v8.5.0
• Platform: Unity Android

Example code snippet

Failed to upload Android symbol files to BugSnag. Error: Error uploading symbols: 
Output: [DEBUG] Extracting launcher-release.aab into a temporary directory
[DEBUG] Reading data from AndroidManifest.xml
[DEBUG] Using 442db60fad1b64cacfe134a77921cad41c71b219 as build ID from dex signatures
[DEBUG] Using 1 as version code from AndroidManifest.xml
[DEBUG] Using 0.1.0 as version name from AndroidManifest.xml
[DEBUG] Found NDK (.so) files at: /var/folders/bs/x688xcq13lz1j_zlxpbgrty00000gq/T/bugsnag-cli-aab-unpacking-3341614674/BUNDLE-METADATA/com.android.tools.build.debugsymbols
[DEBUG] Using [PATH/TO/PROJECT/ROOT] as the project root
[FATAL] unable to determine ndk version from /Applications/Unity/Hub/Editor/6000.0.35f1/PlaybackEngines/AndroidPlayer/NDK

[clr182]

Hi @troysteinbauer

Thanks for reaching out.

This does look to be a bug on our CLI tool, we have raised this with our engineering team and will be sure to follow up on this thread with an update when possible.