You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When selecting an image or recovery that does not match the device codes, I was bothered by the lack of transparency and specificity in the error message, which just said the files "don't work with the device".
We now show an error message that gives the user a better clue about why we rejected the file they chose. It explicitly shows the discovered and expected device codes.
For instance:
"This image lists support for device codes {supported_devices}. One of these should match one of your device's code names {supported_device_codes}."
For screen-shots see the issue in my own repository.
For the patch, you can review the diff of my branch against upstream dev branch (when I last synchronised it).
You can merge this into the dev branch of your fork using a standard git command (why not a github PR?):
When selecting an image or recovery that does not match the device codes, I was bothered by the lack of transparency and specificity in the error message, which just said the files "don't work with the device".
We now show an error message that gives the user a better clue about why we rejected the file they chose. It explicitly shows the discovered and expected device codes.
For instance:
For screen-shots see the issue in my own repository.
For the patch, you can review the diff of my branch against upstream
dev
branch (when I last synchronised it).You can merge this into the
dev
branch of your fork using a standardgit
command (why not a github PR?):The text was updated successfully, but these errors were encountered: