desktop-pwas: Don't DCHECK launcher update result
This change removes a DCHECK from the result of updating Progressive Web App (PWA) launchers, to prevent debug builds of Chrome from crashing when an update fails. PWA launcher update could fail for any of the following reasons: * Latest launcher version path does not exist * Failed to create a temporary directory * Failed to rename any launcher path to "_old" * Failed to create a hardlink/copy of the latest launcher Because some of the above failures are file operations that could reasonably fail, a DCHECK on their success is misleading as it implies "this should never happen". A more appropriate way to handle update failure is to stop the update (without crashing) and emit a UMA metric indicating the failure reason. This change adds TODOs for that as a next step. Bug: 1067241 Change-Id: If2f2145fc62619618917c80f26234930d3a26d0d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134584Reviewed-by:Olivier Yiptong <oyiptong@chromium.org> Commit-Queue: Jesse McKenna <jessemckenna@google.com> Cr-Commit-Position: refs/heads/master@{#756831}
Showing
Please register or sign in to comment