Repository navigation
Provide Report a Problem from LoopSupport - #40
Merged
Merged
Conversation
* Leave the GitHub issues link to Loop's Report a Problem screen Loop now lists every way to report a problem on one screen, including GitHub issues, so LoopSupport no longer adds its own Submit Bug Report row to Support. Also drops supportMenuItem, which nothing calls. * Provide Report a Problem from LoopSupport The Report a Problem screen, the developer report form and its submitter move here from Loop, so each support plugin decides what its users can report and where it goes. LoopSupport adds one Report a Problem row to Support with all four options: send to the Loop developers, share a diagnostic report, open a GitHub issue, and export critical event logs through the app. The report context is built from the app's bundle and BuildDetails plus the pump and CGM status the delegate provides.
marionbarker
approved these changes
Oct 20, 2026
marionbarker
left a comment
marionbarker
left a comment
There was a problem hiding this comment.
Approve by test.
Only question is: could the spacing between rows in the Also Sent section need reduced.
Not shown in screenshots, but successfully tested the customization list is included in the "Also Sent" section when customizations are applied.
Screenshots from the combined changes of 4 PR are found in the Loop PR (instead of here.)
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
2 participants
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.
Backport of #39 to dev: DIY Loop's ways to report a problem live in LoopSupport, behind a single Report a Problem row in Support:
Differences from next-dev:
SupportInfoProvider.generateIssueReporttakes a completion handler, so a small private async wrapper calls it.Needs LoopKit/LoopKit#661 and LoopKit/LoopOnboarding#37, and merges together with LoopKit/Loop#2595, which removes Loop's own report form.
Testing, with the
LoopWorkspacebuild in the simulator: the Report a Problem screen, sharing a diagnostic report (274 KB file) and exporting critical event logs.