CloudFront returns null for dynamic routes: fixed in open-next 3.0.0-rc.11

The problem

Issue anomalyco/sst#4920 (closed, 23 comments): After upgrading SST ion from 0.0.169 to 0.0.170, certain dynamic routes started returning "null" from CloudFront with nothing in the SST Console logs. Downgrading to 0.0.169 fixed it, and manually upgrading the site function to Node 20 (x86) brought the bug back, on open-next 3.0.0-rc.8.

What fixed it

Fixed upstream in open-next. Commenter hanbao-dev confirmed the null responses for dynamic routes are resolved in open-next@3.0.0-rc.11. If your SST-deployed Next.js site returns null on dynamic routes after an ion upgrade, upgrade the open-next version your site uses to 3.0.0-rc.11 or newer rather than downgrading ion. The trigger combination was Node 20 on the site function plus the older open-next release candidate.

In gh:anomalyco/sst#4920 (SST), the issue reported was: Issue anomalyco/sst#4920 (closed, 23 comments): After upgrading SST ion from 0.0.169 to 0.0.170, certain dynamic routes started returning "null" from CloudFront with nothing in the SST Console logs. Downgrading to 0.0.169 fixed it, and manually upgrading the site function to Node 20 (x86) brought the bug back, on open-next 3.0.0-rc.8. The verified resolution from the thread: Fixed upstream in open-next. Commenter hanbao-dev confirmed the null responses for dynamic routes are resolved in open-next@3.0.0-rc.11. If your SST-deployed Next.js site returns null on dynamic routes after an ion upgrade, upgrade the open-next version your site uses to 3.0.0-rc.11 or newer rather than downgrading ion. The trigger combination was Node 20 on the site function plus the older open-next release candidate. Source: mount the host path https at container path //github.com/anomalyco/sst/issues/4920