Re: [chromium-dev] DevTools chrome//:inspect returns 404 not found on my Android Chrome build apk

[Mikhail Naganov]

The problem is due to "@0" part in your URL. This is supposed to be a Blink revision number. Please check in the tree where you were building Chrome for Android, what "build/util/LASTCHANGE.blink" file contains -- it should be something like "LASTCHANGE=<6-digits number>". This number corresponds to the SVN revision of Blink -- you can look it up in the revision history of "third_party/WebKit" repository.

On Wed, Sep 23, 2015 at 3:21 AM, Dmitry Dmitry <frankdr...@gmail.com> wrote:

Hi!

I'm new in Chromium. I have two identical Ubuntu machine(one clone from another for experiments). But when i run inspect in chrome//:inspect#devices tab on ChromePublic.apk(which was built in clone machine) window appears with title "chrome-devtools://remote/serve_rev/@0/inspector.html?&remoteFrontend=true&dockSide=undocked" and contents "404 Not Found The resource could not be found". But with ChromePublic.apk from original virtual machine chrome//:inspect works fine. Why this can happen? What source files may be broken which affect this problem?

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Dmitry Dmitry]

Thanks!

среда, 23 сентября 2015 г., 19:03:35 UTC+3 пользователь Mikhail Naganov написал:

[Hsing-Wang Liao]

Hello, I have build with Chromium 58, has the same issue, I set the "LASTCHANGE" to Webkit git reversion by the command:

./build/util/lastchange.py  build/util/LASTCHANGE

./build/util/lastchange.py -s third_party/WebKit/ -o build/util/LASTCHANGE.blink

The url looks ok now, but still 404.

How can I sove this problem? Thanks.

在 2015年9月24日星期四 UTC+8上午12:03:35，Mikhail Naganov写道：

[Hsing-Wang Liao]

Solved:

We need to get the latest commit hash of dir

src/third_party/WebKit

Not the latest commit of src.

For example: 60.0.3112.113

See: https://chromium.googlesource.com/chromium/src/+log/60.0.3112.113/third_party/WebKit

[Андрей Кадацкий]

Hello, have the same issue. Could you describe your solution more in more details, please?
How to get the latest commit hash? I see that src/third_party/WebKit dir under the same git root as src, so hash will be the same. 
What to do next with it?
Put into LASTCHANGE.blink?

[Hsing-Wang Liao]

Maybe it's too late.

First, get your source tag. eg. 60.0.3112.113

then, visit https://chromium.googlesource.com/chromium/src/+log/60.0.3112.113/third_party/WebKit

click on the first commit: 33e2e84, you can see the full commit hash.

put it to src/build/util/LASTCHANGE

LASTCHANGE=33e2e848ee23a2d32462733a891f7274ac2290c0-

rebuild.

在 2017年9月26日星期二 UTC+8下午11:07:44，Андрей Кадацкий写道：

[Igor Yanishevskiy]

Thanks, it helped a lot!

четверг, 1 марта 2018 г., 9:09:15 UTC+1 пользователь Hsing-Wang Liao написал: