Skip to content

Web inspector(devtools) freezed when I accessed local dev server on iOS Safari #78528

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

Open
edoko opened this issue Apr 25, 2025 · 2 comments
Open

Comments

@edoko
Copy link

edoko commented Apr 25, 2025

Link to the code that reproduces this issue

https://github.com/edoko/next-js-15-freeze-devtools

To Reproduce

  1. Used macOS 15.4.1 and iOS 18.4(simulator)/16.3(real device)
  2. Create a basic app with create-next-app@latest.
    2-1. I enabled ESLint, tailwindcss, page router, webpack, and import alias.
  3. Changed npm to yarn(v4.9.1/pnp)
  4. Run with yarn dev
  5. Access the local dev server(http://xxx.xxx.xxx.xxx:3000) on a real device/simulator and connect it to a mac via USB.
  6. Run the web inspector for that page in Safari.
  7. The web inspector is running, but stops without displaying all elements.
    The console tab is also empty, and the network tab shows the last record as webpack-hmr.
  8. Even after waiting for tens of seconds, the freezed state continues.
  9. The same thing happens even if I run the web inspector again.

The screenshot below is a screenshot taken when the issues occurred.
Image

Current vs. Expected behavior

Current behavior:

Web inspector stops.

Expected behavior:

Web inspector should be operational and all tabs should display data normally.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.4.0: Fri Apr 11 18:32:50 PDT 2025; root:xnu-11417.101.15~117/RELEASE_ARM64_T6041
  Available memory (MB): 65536
  Available CPU cores: 16
Binaries:
  Node: 20.19.1
  npm: 10.8.2
  Yarn: 4.9.1
  pnpm: N/A
Relevant Packages:
  next: 15.4.0-canary.9
  eslint-config-next: N/A
  react: 19.1.0
  react-dom: 19.1.0
  typescript: N/A
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

  • The same issue occurs when running devtools in Safari on macOS.
  • The same result is also in Next.js v15.3.1.
  • Chrome's devtools function normally.
  • It works correctly after downgrading to Next.js v14.
@HMarzban
Copy link

I'm running into the same issue.
Any suggestions? I can't downgrade to v14, it would require too many changes.

@edoko
Copy link
Author

edoko commented Apr 28, 2025

I'm running into the same issue. Any suggestions? I can't downgrade to v14, it would require too many changes.

I'm also the same 😢 The cost of downgrading to v14 is high, so I am maintaining the current status.
There is #78524 with a similar issue to, but it seems there is no solution.
I'm also curious if it's only some users experiencing this.

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

2 participants