.NET-SDK wirft eine Nullpointer Exception wenn eine Submission ohne Attachment abgerufen wird.
Description of the bug:
Kunde nutzt das .NET-SDK und bekommt einen Fehler, wenn er eine Submission ohne Anlage abholt.
- Kunde übermittelt eine Einreichung ohne Anlage
- Kunde holt Einreichung ohne Anlage ab
Current behavior:
Das .NET-SDK wirft eine NPE, wenn versucht wird, eine Einreichung ohne Anlage abzuholen
Expected behavior:
Eine fehlende Einreichung sollte keine Nullpointer Exception verursachen. Wenn ein Fehlverhalten vorliegt, sollte eine Fehlermeldung erzeugt werden, die den Nutzer/Entwickler darauf hinweist, dass ein Fehler vorliegt
Environments:
Additional Information:
Dependency / relationship to other issues:
Ticket über Jira FCONSD-497 geöffnet
Responsible person / team:
SDK
Contact persons including contact details:
Screenshots / Logs / Requests:
Callstack:
FIT-Connect[0]
Error while receiving submission
System.NullReferenceException: Object reference not set to an instance of an object.
at FitConnect.Subscriber.CheckAttachments(Submission submission, SecurityEventToken submitEvent)
at FitConnect.Subscriber.CheckSubmissionAsync(Submission submission)
at FitConnect.Subscriber.RequestSubmissionAsync(Guid submissionId)
fail: FIT-Connect[0]
Error while getting submission
FitConnect.Exceptions.FitConnectSubscriberException: Error while receiving submission
---> System.NullReferenceException: Object reference not set to an instance of an object.
at FitConnect.Subscriber.CheckAttachments(Submission submission, SecurityEventToken submitEvent)
at FitConnect.Subscriber.CheckSubmissionAsync(Submission submission)
at FitConnect.Subscriber.RequestSubmissionAsync(Guid submissionId)
— End of inner exception stack trace —
at FitConnect.Subscriber.RequestSubmissionAsync(Guid submissionId)
at Fit_Connect.Subscriber.Run(IConfiguration config, ILogger logger) in C:\git__NO_fit-connect\Fit-Connect\Subscriber.cs:line 170
Checklist:
-
Add Severity label -
Add team label -
Related/affected issues/stories/epics linked and explained in the bug issue -
Creation of an automated test -
Bugfix deployed on DEV -
Bugfix tested on DEV -
Bugfix deployed on TEST -
Bugfix tested on TEST (possibly also by the connection project itself) -
Successful fix reported to Team Operations (Teams channel) -
Bugfix deployed on STAGE -
Bugfix tested on STAGE if necessary -
Bugfix deployed on PROD -
Bugfix tested on PROD (possibly also by the connection project itself) -
Final communication by Team Operations if necessary -
Internal documentation was checked and updated if necessary -
External documentation has been checked and updated if necessary -
Updated changelog if necessary
Approach/Solution:
Release version of the artifact:
Edited by Andreas Huber