feat: Add failed response error reporting using the feedback system#452
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds an SDK-level “failed request report” flow that captures details from failed HTTP requests and allows developers to submit those details to LootLocker via the existing feedback system (category lootlocker_request_failure) for debugging/diagnostics.
Changes:
- Added
LootLockerSDKManager.SendLootLockerErrorReport(...)andLootLockerResponse.ReportFailure(...)convenience method to submit a captured failure report. - Extended response/request context plumbing to carry a client-generated
request_idthrough responses. - Implemented failed-request history capture in
LootLockerHTTPClientand category-id discovery for the failure feedback category.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 11 comments.
| File | Description |
|---|---|
| Runtime/Game/LootLockerSDKManager.cs | Adds a public API to send an error report for a previously failed request. |
| Runtime/Client/LootLockerResponse.cs | Adds response convenience method and extends response factory to include request IDs in context. |
| Runtime/Client/LootLockerRequestContext.cs | Extends request context to store a client-generated request ID. |
| Runtime/Client/LootLockerHTTPClient.cs | Captures failed request details into a bounded history and fetches the feedback category ID for reporting. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
9968b3c to
fdf7742
Compare
JohannesLoot
approved these changes
Apr 9, 2026
Contributor
JohannesLoot
left a comment
There was a problem hiding this comment.
Really awesome feature!
Great work 👍
Merge it!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Will result in a report like this:

Requires that the developer creates a game feedback category named exactly "lootlocker_request_failure", otherwise report sending won't work.
Added a
LootLockerSDKManager.method and a convenience overload on the response itself to send the report. Example code (ignore logging/OutputText.text parts, that's my test game logging to screen):How this works under the hood is that I generate "report objects" for each failed request and keep the latest 10. Then when a report is requested to send to lootlocker we simply match the id and send the pregenerated report.