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
Hi, I currently experience issues with release library on Windows. SDK seems like sending requests but they do not appear in Sentry at all.
If I link to Debug library - everything works perfectly and events appear in Sentry, if I link to Release - nothing is being sent and folder for sentry db contains only folder with name "00000000-0000-0000-0000-000000000000", while debug version creates something like this: "1e33f629-8ebe-4ea9-7bbb-206651458677".
I have built library with crashpad and without crashpad backend - nothing has changed.
I was able to retrieve logs of the sdk and for both (Debug and Release) everything seems the same:
Debug logs:
folder for sentry db contains only folder with name "00000000-0000-0000-0000-000000000000"
That is definitely wrong. Maybe our random / uuid generation code is broken when doing release builds. I will check that.
Also: When you post the logs here, pleas make sure to remove/obfuscate your sentry_key :-D Because now everyone could be uploading stuff to your project. Please generate a fresh DSN, and keep that in mind for next time ;-)
Hi, I currently experience issues with release library on Windows. SDK seems like sending requests but they do not appear in Sentry at all.
If I link to Debug library - everything works perfectly and events appear in Sentry, if I link to Release - nothing is being sent and folder for sentry db contains only folder with name "00000000-0000-0000-0000-000000000000", while debug version creates something like this: "1e33f629-8ebe-4ea9-7bbb-206651458677".
I have built library with crashpad and without crashpad backend - nothing has changed.
I was able to retrieve logs of the sdk and for both (Debug and Release) everything seems the same:
Debug logs:
Release logs:
Maybe I'm missing something?
The text was updated successfully, but these errors were encountered: