We haven't uploaded front-end for your local hash to the server. If you compile desktop version of the browser, I can tell you what to tweak so that it was using local front-end version. Alternatively, consider using legacy remote debugging workflow:
- adb forward android's named socket to 9222
- visit localhost:9222 to obtain debugging web socket name
- open chrome-devtools://devtools/bundled/inspector.html?ws=<WS> in your canary.

Yep, another workaround is to 'git checkout' the last valid commit and run gclient runhooks, then re-checkout the local commit again.

Just wanted to point out that this was explicitly fixed in that second commit I linked, and seems to have been unintentionally broken again.

This is not just broken for local commits; this is also broken for all non-.0 tagged release versions I think. The extra commit in, say, 60.0.3112.116 which updates DEPS to the right versions of the dependencies for the .116 build changes the hash and the frontend doesn't match any more.

The hook should probably find the last "real" committed commit with a commit position like it used to..

The issue I point out in comment 4 is pretty bad and makes chromium release builds (unlike Chrome) largely unusable for remote debugging. Was that fixed elsewhere? If not then I think this needs addressing still..

Merging this into a still-open dupe