Discord Notifications broke w/ new update

Sonarr version (exact version): v3.0.4.986
Mono version (if Sonarr is not running on Windows):
OS: Ubuntu 18.04
Debug logs:
(Make sure debug logging is enabled in settings and post the full log to hastebin/pastebin/dropbox/google drive or something similar, do not post them directly here. Post in .txt not .doc, .rtf or some other formatted document)
20-10-21 09:15:01.9|Info|DownloadService|Report sent to qb. [SubsPlease] Noblesse - 03 (720p) [C89248B9].mkv
20-10-21 09:15:01.9|Error|NotificationService|Unable to send OnGrab notification to DiscordAiring

[v3.0.4.986] System.NullReferenceException: Object reference not set to an instance of an object
at NzbDrone.Core.Notifications.Discord.Discord.OnGrab (NzbDrone.Core.Notifications.GrabMessage message) [0x001e1] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Discord\Discord.cs:71
at NzbDrone.Core.Notifications.NotificationService.Handle (NzbDrone.Core.Download.EpisodeGrabbedEvent message) [0x000b9] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\NotificationService.cs:125

20-10-21 09:15:02.5|Info|RssSyncService|RSS Sync Completed. Reports found: 275, Reports grabbed: 1
20-10-21 09:16:35.3|Warn|NotificationService|Unable to send OnDownload notification to: DiscordAiring

[v3.0.4.986] System.NullReferenceException: Object reference not set to an instance of an object
at NzbDrone.Core.Notifications.Discord.Discord.OnDownload (NzbDrone.Core.Notifications.DownloadMessage message) [0x00216] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Discord\Discord.cs:162
at NzbDrone.Core.Notifications.NotificationService.Handle (NzbDrone.Core.MediaFiles.Events.EpisodeImportedEvent message) [0x000ed] in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\NotificationService.cs:161

Description of issue:

Discord notifications used to work fine and the test message still sends but now with the new update to them it seems to be trying to point to some path that doesn’t exist.

This is the docker deployment with latest image.

Looks like that’ll happen whenever the overview is null and included in the payload, we’ll get a fix in for that.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.