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
Recording exception in .NET app seems to be working (the URL that SDK creates returns result = success), but they don't appear on the server (using Lite edition).
@cherpake Thank you for letting us know. Can you share the 'Utilities > Incoming Data Logs' from your server if possible? Also do you have multiple apps on your server? If so, the app you are looking at and the app the data is has been sent to can be different. Can you verify that?
Parse crash JSON failed {"_os":"Windows 10 Pro","_os_version":"10.0.22631","_resolution":"2560x1440","_app_version":"2024.11","_ram_current":10246144000,"_ram_total":33970991104,"_online":true,"_name":"Object reference not set to an instance of an object.","_error":" at Remote_for_Windows.SettingsForm.resetComputerIdButton_Click(Object sender, EventArgs e) in D:\\source\\win\\Remote for Win\\SettingsForm.cs:line 568\r\n at System.Windows.Forms.Control.OnClick(EventArgs e)\r\n at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)\r\n at System.Windows.Forms.Control.WmMouseUp(Message /i?app_key=fa31a6c00afd2a8871880b41a6c6a7b070396fc2&device_id=CLY_AFDD29ECC45D4BE4BE7791D1D336D0B2&t=3&sdk_name=csharp-net45&sdk_version=24.1.0×tamp=1716445747510&dow=4&hour=6&tz=180&av=2024.11&crash=%7B%22_os%22:%22Windows%2010%20Pro%22,%22_os_version%22:%2210.0.22631%22,%22_resolution%22:%222560x1440%22,%22_app_version%22:%222024.11%22,%22_ram_current%22:10246144000,%22_ram_total%22:33970991104,%22_online%22:true,%22_name%22:%22Object%20reference%20not%20set%20to%20an%20instance%20of%20an%20object.%22,%22_error%22:%22%20%20%20at%20Remote_for_Windows.SettingsForm.resetComputerIdButton_Click(Object%20sender,%20EventArgs%20e)%20in%20D:%5C%5Csource%5C%5Cwin%5C%5CRemote%20for%20Win%5C%5CSettingsForm.cs:line%20568%5Cr%5Cn%20%20%20at%20System.Windows.Forms.Control.OnClick(EventArgs%20e)%5Cr%5Cn%20%20%20at%20System.Windows.Forms.Button.OnMouseUp(MouseEventArgs%20mevent)%5Cr%5Cn%20%20%20at%20System.Windows.Forms.Control.WmMouseUp(Message&%20m,%20MouseButtons%20button,%20Int32%20clicks)%5Cr%5Cn%20%20%20at%20System.Windows.Forms.Control.WndProc(Message&%20m)%5Cr%5Cn%20%20%20at%20System.Windows.Forms.ButtonBase.WndProc(Message&%20m)%5Cr%5Cn%20%20%20at%20System.Windows.Forms.Button.WndProc(Message&%20m)%5Cr%5Cn%20%20%20at%20System.Windows.Forms.NativeWindow.Callback(IntPtr%20hWnd,%20Int32%20msg,%20IntPtr%20wparam,%20IntPtr%20lparam)%22,%22_nonfatal%22:false,%22_logs%22:%22%22,%22_run%22:4,%22_custom%22:%7B%7D%7D&rr=2
@cherpake Thanks for the logs, they pinpointed it. Your stack trace contains & (Message& m), and 24.1.0 sent crash reports without URL-encoding them. The server cut each report at the first & and couldn't read it, while still answering "Success". This was fixed in 24.1.1. Windows 11 being reported as Windows 10 was fixed in 25.4.1. Updating to the latest version fixes both. Closing this; feel free to reopen if you still see it after updating.
Activity
turtledreams commentedon May 23, 2024
@cherpake Thank you for letting us know. Can you share the 'Utilities > Incoming Data Logs' from your server if possible? Also do you have multiple apps on your server? If so, the app you are looking at and the app the data is has been sent to can be different. Can you verify that?
Also a small guide for these kind of issues: https://support.count.ly/hc/en-us/articles/900000908046-Getting-Started-with-SDKs#h_01HABSX9KXE6YKVETHDWPP8J3K
cherpake commentedon May 23, 2024
@turtledreams Hey, thanks for responding.
Checked again and the right app is selected, Crashes view is empty but in the incoming logs I have this
cherpake commentedon May 23, 2024
By the way for some reason Windows 11 Pro is detected as Windows 10...
cherpake commentedon May 23, 2024
If this helps - this appears in the logs:
turtledreams commentedon Oct 16, 2026
@cherpake Thanks for the logs, they pinpointed it. Your stack trace contains & (Message& m), and 24.1.0 sent crash reports without URL-encoding them. The server cut each report at the first & and couldn't read it, while still answering "Success". This was fixed in 24.1.1. Windows 11 being reported as Windows 10 was fixed in 25.4.1. Updating to the latest version fixes both. Closing this; feel free to reopen if you still see it after updating.