Repository navigation
Merge dev into next-dev - #44
Merged
Merged
Conversation
language modification
Usage data now goes to the LoopKit ingest endpoint instead of Amplitude's default API host.
Send analytics to ingest.loopkit.org
Adds the build number and the LoopWorkspace and Loop git branch and revision from BuildDetails.plist, so builds sharing a version string can be told apart. This event is sent at the version-only sharing level.
Sends the identifiers Loop's build-details script collected from .loopcustomization marker files.
Include build details on the instantiation event
* Require iOS 17.6 * Provide Report a Problem from LoopSupport * 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. * Generate the diagnostic report through dev's completion handler * update string catalog --------- Co-authored-by: marionbarker <marionbarker@earthlink.net>
Share a Diagnostic Report now opens a viewer showing the report, with a Share button for saving or sending it as a file. The developer report form gains View Diagnostic Report under Include Diagnostic Report, so the attachment can be checked before submitting.
# Conflicts: # LoopSupportKitUI/IssueReport/ReportProblemView.swift
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.
Merges
devintonext-devso that LoopKit/LoopWorkspace#454 (next-dev → dev) no longer conflicts and drops nothing from dev.Brings in dev's translation updates and the Report a Problem work. The only conflict was the dev-only callback wrapper at the end of
ReportProblemView.swift; next-dev's async API doesn't need it, so it is dropped.Built as part of the whole workspace (LoopWorkspace scheme, iOS Simulator) with every submodule at its merge commit.
Please merge with "Create a merge commit" (not squash or rebase); otherwise the merge history is lost and dev will conflict with next-dev again.