Next app open blank screen on DingTalk app

[AlwaysLoveme]

Verify canary release

• [X] I verified that the issue exists in the latest Next.js canary release

Provide environment information

┌─[zhuxian@zhuxiandeMacBook-Pro] - [~/Documents/projects/learn/next-app] - [Mon Apr 10, 10:03]
└─[$]> next info      

    Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64
    Binaries:
      Node: 16.17.1
      npm: 9.6.2
      Yarn: 1.22.19
      pnpm: 8.1.0
    Relevant packages:
      next: 13.3.0
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0

warn  - Latest canary version not detected, detected: "13.3.0", newest: "13.3.1-canary.3".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue

Which area(s) of Next.js are affected? (leave empty if unsure)

CLI (create-next-app)

Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/github/vercel/next.js/tree/canary/examples/reproduction-template-app-dir?file=README.md&selection=%5B%7B%22endColumn%22%3A20%2C%22endLineNumber%22%3A9%2C%22startColumn%22%3A14%2C%22startLineNumber%22%3A9%7D%5D

To Reproduce

use DingTalk app to open a next blank project which created by create-next-app, page show nothing on Android, and show error "TypeError: undefined is not an object(evaluating 'stream.getReader')" when navigate to other page on IOS

Describe the Bug

use DingTalk app to open a next blank project which created by create-next-app, page show nothing on Android, and show error "TypeError: undefined is not an object(evaluating 'stream.getReader')" when navigate to other page on IOS

Expected Behavior

next-app can open and use fine on DingTalk

Which browser are you using? (if relevant)

DingTalk app with latest version

How are you deploying your application? (if relevant)

next dev

[xurenlu]

I had this problem too. I think it's because DingTalk app has a chrome 69.

[sanriqing]

I had the same problem. It is found that response does not have body attribute in the DingTalk app

[sanriqing]

workaround: just disabled link prefetch

[nxl3477]

I had the same problem

[j-joker]

I had the same problem

[j-joker]

for god sake , is there any one of next can response to this issue,