Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DevTools inspect window doesn't render properly #696

Open
AresProductions opened this issue Mar 4, 2021 · 52 comments
Open

DevTools inspect window doesn't render properly #696

AresProductions opened this issue Mar 4, 2021 · 52 comments

Comments

@AresProductions
Copy link

Hello everyone,

I've been using Stetho for over a year in my Macbook Pro (Intel Chip).
Since yesterday after I try to inspect my app through the device via Chrome.
A badly rendered DevTool window appears which doesn't show anything.

Here's a screenshot:
Screenshot 2021-03-04 at 16 34 03

I've tried to use another device already. Restarted my Laptop, re-installed Chrome. Nothing appears to be working anymore. 😞

Any ideas? Thank you in advance.

@jnovinger
Copy link

jnovinger commented Mar 4, 2021

This appears to have broken with the most recent release of Chrome and Chromium, which for me is 89.0.4389.72 on Linux x64. According to the Chrome Releases blog, that appears to be the new stable that was released two days ago.

Apparently, Google does not make older versions of Chrome available after new stable releases, but you can still get old versions of Chromium. I ultimately followed the directions of the Chromium's project Download Chromium page in the "Downloading old builds of Chrome / Chromium" section. This gave me a locally runnable version 88.0.4324.0 of Chromium in which Stetho tools do work.

Release links:

@AresProductions
Copy link
Author

AresProductions commented Mar 4, 2021

That was it! It was driving me crazy for the past 2 days. Let's hope they fix it soon.

Thank you!!! 🥳

@jnovinger
Copy link

FWIW, this is the changelog between the two versions: https://chromium.googlesource.com/chromium/src/+log/88.0.4324.0..89.0.4389.0?pretty=fuller&n=10000

I have not yet had a chance to look through it to see what might have caused the issue.

@vallividhya
Copy link

Our team is also facing this issue on Chrome for Mac version 89.0.4389.7.

@Praeterii
Copy link

I have the same issue on intel mac with 89.0.4389.72. Unfortunatly due to company policy I am not able to downgrade my browser. Can you think of any other workaround?

@jingjoeh
Copy link

jingjoeh commented Mar 7, 2021

For me, Using Edge Version 89.0.774.45 instead.

@ClarkXP
Copy link

ClarkXP commented Mar 9, 2021

On Linux, using edge dev version 90.0.810.1

@NunoPontes
Copy link

Yes, our team is also facing the same issue. We are using Edge as a workaround

@something15525
Copy link

Having this issue as well on Chrome Version 89.0.4389.82 (Official Build) (x86_64)

@ehorvat
Copy link

ehorvat commented Mar 17, 2021

Thank you @jnovinger you're my savior

@valeriyo
Copy link

89.0.4389.90 on Mac is still broken. What's the link to the Chrome bug?

@xayo69
Copy link

xayo69 commented Mar 19, 2021

遇到同样的问题,怎么解决了?

@thumbb13555
Copy link

截圖 2021-03-20 下午12 22 28

It can work on edge, but still broken on Mac's Chrome.

@zongxiaomi
Copy link

遇到同样的问题,怎么解决1了?

  1. 降级
  2. 用微软的Edge浏览器
  3. Chromium 浏览器

@h3clikejava
Copy link

遇到同样的问题,怎么解决1了?

  1. 降级
  2. 用微软的Edge浏览器
  3. Chromium 浏览器

I've try Chromium by Version 91.0.4458.0 (Developer Build) (x86_64) on Mac 11.2 (20D64) , but still not working

@astamato
Copy link

Same issue here, currently using old version of Chrome Version 88.0.4324.192 (Official Build) (x86_64).

@Alshayib
Copy link

This appears to have broken with the most recent release of Chrome and Chromium, which for me is 89.0.4389.72 on Linux x64. According to the Chrome Releases blog, that appears to be the new stable that was released two days ago.

Apparently, Google does not make older versions of Chrome available after new stable releases, but you can still get old versions of Chromium. I ultimately followed the directions of the Chromium's project Download Chromium page in the "Downloading old builds of Chrome / Chromium" section. This gave me a locally runnable version 88.0.4324.0 of Chromium in which Stetho tools do work.

Release links:

it's working with me thanks

@JuliaC28
Copy link

This appears to have broken with the most recent release of Chrome and Chromium, which for me is 89.0.4389.72 on Linux x64. According to the Chrome Releases blog, that appears to be the new stable that was released two days ago.
Apparently, Google does not make older versions of Chrome available after new stable releases, but you can still get old versions of Chromium. I ultimately followed the directions of the Chromium's project Download Chromium page in the "Downloading old builds of Chrome / Chromium" section. This gave me a locally runnable version 88.0.4324.0 of Chromium in which Stetho tools do work.
Release links:

it's working with me thanks

Thanks for the link!
But ... may I ask how I can use the files from the link to download the downgraded version of Chrome?
My current version doesn't support Stetho either ...

Thank you in advance!

@SamTobias
Copy link

Just pointing that Edge doesn't show shared preferences but Chromium 88 does

@zekapp
Copy link

zekapp commented Apr 6, 2021

Just add a note that the issue hasn't been fixed with the latest Chrome release.

I am using Mac with Google Chrome Version 89.0.4389.114 (Official Build) (x86_64)
and the issue still exists.

@xayo69
Copy link

xayo69 commented Apr 6, 2021

下载Chromium版本 88.0.4324.0(开发者内部版本) (32 位)还是不行

@niezhe
Copy link

niezhe commented Apr 19, 2021

版本 90.0.4430.72(正式版本) (64 位)这个版本也还是不行,没有解决

@valeriyo
Copy link

Chrome 90.0.4430.85 (Official Build) (x86_64) is still broken. F U C K

@valeriyo
Copy link

Here is the Chromium bug report --- they have no clue how to even reproduce it
https://bugs.chromium.org/p/chromium/issues/detail?id=1187142

@JuliaC28
Copy link

JuliaC28 commented Apr 22, 2021 via email

@valeriyo
Copy link

Here is a nice article on how to switch from Stetho to Flipper. Enjoy, you guys!

https://foxum.medium.com/flipper-replaces-stetho-c11d20e81ca0

@JuliaC28
Copy link

JuliaC28 commented Apr 24, 2021 via email

@e16din
Copy link

e16din commented Apr 28, 2021

Thaaanks 😊 Von: Valeriy @.> Gesendet: Samstag, 24. April 2021 06:25 An: @.> Cc: @.>; @.> Betreff: Re: [facebook/stetho] DevTools inspect window doesn't render properly (#696) Here is a nice article on how to switch from Stetho to Flipper.https://fbflipper.com/docs/getting-started/android-native Enjoy, you guys! https://foxum.medium.com/flipper-replaces-stetho-c11d20e81ca0 — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#696 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATO3P2BU36JCVVLE5FYWAA3TKJB4NANCNFSM4YTLZROA.

Flipper has terrible network logging functionality :(

@vusimoy0
Copy link

vusimoy0 commented May 1, 2021

I also had this issue. also running MacOS on intel chip. I ended up switching to Brave browser which is also based on chromium. It looks so much better and I can see my Api calls again! You just use brave://inspect and then do the normal Stetho things. Hope this helps.

image

@JuliaC28
Copy link

JuliaC28 commented May 1, 2021 via email

@bhavin1994
Copy link

Thank you so much for helping me out! 😊 Von: Vusi @.> Gesendet: Samstag, 1. Mai 2021 09:53 An: @.> Cc: @.>; @.> Betreff: Re: [facebook/stetho] DevTools inspect window doesn't render properly (#696) I also had this issue. I ended up switching to Brave browser which is also based on chromium. It looks so much better and I can see my Api calls again! You just use brave://inspect and then do the normal Stetho things. Hope this helps. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#696 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATO3P2EV2EIYGWDZT4DJIJDTLOXPHANCNFSM4YTLZROA.

yeah but edge and brave not showing sharedpreferences

@hbmartin
Copy link

If you're switching to Flipper but want to keep using custom dumpapp plugins, I created a library to help migrate: https://github.com/hbmartin/flipper-plugin-stetho

@JuliaC28
Copy link

JuliaC28 commented May 29, 2021 via email

@debashishmahato-muvi
Copy link

Yes same issue. i am also facing. Might be due to new chrome update

@debashishmahato-muvi
Copy link

This appears to have broken with the most recent release of Chrome and Chromium, which for me is 89.0.4389.72 on Linux x64. According to the Chrome Releases blog, that appears to be the new stable that was released two days ago.

Apparently, Google does not make older versions of Chrome available after new stable releases, but you can still get old versions of Chromium. I ultimately followed the directions of the Chromium's project Download Chromium page in the "Downloading old builds of Chrome / Chromium" section. This gave me a locally runnable version 88.0.4324.0 of Chromium in which Stetho tools do work.

Release links:

Its working.. for me in Windows . I installed the Chromium .

@zhenghuiC
Copy link

下载Chromium版本 88.0.4324.0(开发者内部版本) (32 位)还是不行

用微软的Edge我这边可以

@oguz-sahin
Copy link

I installed microsoft edge Version 91.0.864.54 and work perfect dev tools.

@teffy
Copy link

teffy commented Jul 28, 2021

Hey, guys, any update here?
So We need Edge now?

I'm guided here from j2v8-debugger

@Turnsole
Copy link

Hey, guys, any update here?
So We need Edge now?

I'm guided here from j2v8-debugger

I've switched to Edge, Chrome + Stetho never worked again for me on any of my machines.

@john-rsvp
Copy link

Any progress on this? Any plans on having this fixed?

@ashu5398
Copy link

Why do you guys introduce such bugs and didn't roll them back if you can't fix them? It's been 5 months and still have no updates

@vegeta2102
Copy link

Is there any workaround with new release chrome version?

@1gravity
Copy link

Still broken in Chrome (Version 94.0.4606.81 (Official Build) (64-bit)) on Ubuntu:
image

Works perfectly with the Brave Browser:
image

@JohnsonEricAtSalesforce

I see this issue is still open and can confirm Stetho will not function with Chrome 95. It will, of course, with Chromium 88.

Stetho would be a valuable tool and much more convenient if it worked with the latest Chromium builds. I reached out to the Chromium project and they have an open issue as well. Stetho is still used in a lot of projects, for now, which are forced to keep Chromium 88 installed because of this issue.

https://bugs.chromium.org/p/chromium/issues/detail?id=1187142#c5

I've been investigating this issue from Stetho's side, but it's still a bit over my head at this time. Does anyone with a background in Stetho have a moment to see what happened in Chrome 89 that broke everything? The Chromium issue thread above might be a great place to ask questions.

@baladai
Copy link

baladai commented Jan 4, 2022

The same problem. Why they haven't fixed such an important feature yet? Or haven't found a workaround?

@astamato
Copy link

astamato commented Jan 4, 2022

Anyone at Stetho could help take a look? @jasta @mdzyuba @funfoolsuzi -- Since integration with Chrome is broken it would make sense for both parties to work together to figure this out? There hasn't really been updates to Stetho since last April.

@hashseed
Copy link

hashseed commented Jan 4, 2022

Hi folks,

I lead the Chrome DevTools team. I also commented on the Chromium issue on this matter.

The problem is that from my team's perspective, this is an unsupported use case. We don't have bandwidth to support every product that is based on Chrome DevTools.

That said, I'd be willing to help fix the problem if someone helps me reproduce the issue. I'm entirely unfamiliar with the Android/Java ecosystem, and from what I read in the README, also don't understand how DevTools is integrated in this.

Alternatively, I'd be open to accept patches. Chrome DevTools is open source, after all.

@xiaomeng3419
Copy link

This appears to have broken with the most recent release of Chrome and Chromium, which for me is 89.0.4389.72 on Linux x64. According to the Chrome Releases blog, that appears to be the new stable that was released two days ago.

Apparently, Google does not make older versions of Chrome available after new stable releases, but you can still get old versions of Chromium. I ultimately followed the directions of the Chromium's project Download Chromium page in the "Downloading old builds of Chrome / Chromium" section. This gave me a locally runnable version 88.0.4324.0 of Chromium in which Stetho tools do work.

Release links:

so good

@Vanuan
Copy link

Vanuan commented Sep 6, 2022

It looks like the issue is that DevTools tries to render infinite width viewport and crashes. Maybe somehow the viewport width is not passed correctly from Stetho to DevTools?

@Vanuan
Copy link

Vanuan commented Sep 6, 2022

Maybe has something to do with this experimental feature:
https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-startScreencast

It says both maxWidth and maxHeight are optional. But I don't see anywhere they are checked to be null. Also, Java supports Infinity value.

int viewWidth = rootView.getWidth();
int viewHeight = rootView.getHeight();
float scale = Math.min((float) mRequest.maxWidth / (float) viewWidth,
(float) mRequest.maxHeight / (float) viewHeight);
int destWidth = (int) (viewWidth * scale);
int destHeight = (int) (viewHeight * scale);
mBitmap = Bitmap.createBitmap(destWidth, destHeight, Bitmap.Config.RGB_565);

This whole screencasting thing appears to be undocumented and is used internally:
https://developer.chrome.com/docs/devtools/remote-debugging/

Maybe something changed with regards to how screencasting works between chrome 88 and chrome 89?

@astamato
Copy link

astamato commented Sep 6, 2022

I guess its pretty obvious that either the community fixes this or it does not get fixed, or we use a workaround whatever that is. No contribution in 2 years effectively means the team behind stetho has ditched this project.

@Turnsole
Copy link

Turnsole commented Sep 7, 2022

I guess its pretty obvious that either the community fixes this or it does not get fixed, or we use a workaround whatever that is. No contribution in 2 years effectively means the team behind stetho has ditched this project.

Yeah, there hasn't been a release in seventeen months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests