[Bug]: SPA navigation to /search failed. Final path: (empty). Twitter may have changed its routing. Add --verbose for details, or report: https://github.com/jackwener/opencli/issues

[shawnzlx01]

Description

SPA navigation to /search failed. Final path: (empty). Twitter may have changed its routing.
Add --verbose for details, or report: https://github.com/jackwener/opencli/issues

Steps to Reproduce

SPA navigation to /search failed. Final path: (empty). Twitter may have changed its routing.
Add --verbose for details, or report: https://github.com/jackwener/opencli/issues

Expected Behavior

SPA navigation to /search failed. Final path: (empty). Twitter may have changed its routing.
Add --verbose for details, or report: https://github.com/jackwener/opencli/issues

OpenCLI Version

1.5.8

Node.js Version

20.x

Operating System

macOS

Logs / Screenshots

[0xsline]

I was able to reproduce this issue on v1.5.9 (macOS, Node 25.x).

Root cause: Twitter/X updated their React Router configuration. The pushState + popstate approach used in navigateToSearch() no longer triggers client-side re-rendering — the URL changes but React does not respond, so [data-testid="primaryColumn"] never appears in the DOM.

Other commands that use primaryColumn with direct page.goto() navigation (e.g. twitter profile) still work fine, confirming the selector itself is not the problem.

Fix: Use the search input ([data-testid="SearchBox_Search_Input"]) on /explore to type the query and press Enter. This triggers Twitter's own form submission handler, which performs proper SPA navigation and preserves the fetch interceptor.

PR: #695

[jackwener]

我无法复现

[Astro-Han]

Update: I've also left a review on PR #695 with some additional findings.

To summarize the current state:

• Cannot reproduce locally: Ran twitter search multiple times, all succeeded. The pushState + popstate approach still works in my environment.
• Likely intermittent: The Final path: (empty) error points to a timing issue (pathname not updated when checked) rather than complete failure. Twitter may be running an A/B test, or behavior varies by browser version / login state.
• PR fix(twitter): use search input for SPA navigation instead of pushState #695 review: The dual-strategy approach is reasonable, but the root cause analysis ("pushState completely broken") doesn't match my observations. Also flagged a regression in the fallback (fixed delay instead of selector-based wait) and noted that the search input approach was previously abandoned in commit fix(twitter): use pushState for search SPA navigation #105.

If you're still hitting this, could you share:

1. How often it happens (every time or intermittently)?
2. Your browser/Chrome version if visible in verbose output?
3. Any additional output from --verbose?