You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Causing/replicating the error: a Unity project with over 260 .pdb files.
Results in:
Sentry: (Error) Failed to add the Sentry native integration to the built application System.ComponentModel.Win32Exception (0x80004005): ApplicationName='C:\Users\xxx\Library\PackageCache\io.sentry.unity@cfd1f01ace\Editor\sentry-cli\sentry-cli-Windows-x86_64.exe' [...many many pdb files....], Native error= The filename or extension is too long.
Hey, sorry to see you run into issues here.
The command does not contain all 260 individual .pdb files but a few individual ones we know of (i.e. UnityPlayer.dll) and directories to navigate recursively.
One thing that comes to mind to unblock you is to embed the package into your project. That means moving it from Unity's global package cache into your project's local /Packages directory.
Causing/replicating the error: a Unity project with over 260 .pdb files.
Results in:
Sentry: (Error) Failed to add the Sentry native integration to the built application System.ComponentModel.Win32Exception (0x80004005): ApplicationName='C:\Users\xxx\Library\PackageCache\io.sentry.unity@cfd1f01ace\Editor\sentry-cli\sentry-cli-Windows-x86_64.exe' [...many many pdb files....], Native error= The filename or extension is too long.
BuildFailedException: Sentry Native BuildPostProcess failed
Sentry.Unity.Editor.Native.BuildPostProcess.OnPostProcessBuild (UnityEditor.BuildTarget target, System.String executablePath) (at /sentry-unity/src/Sentry.Unity.Editor/Native/BuildPostProcess.cs:61)
Reason: generating a sentry_cli command line that exceeds the windows native command line size limit (which I belief is 8191 characters).
Solution (my initial thoughts, but you probably know better):
Version: https://github.com/getsentry/unity.git#1.8.0
Thanks for looking into this,
Pieter (paying Sentry customer :-)
The text was updated successfully, but these errors were encountered: