Bolt mobile

Hamburger Menu Not Opening on Mobile in Bolt App

The hamburger menu icon in your Bolt.new application is visible on mobile screens but nothing happens when users tap it. Alternatively, the menu opens once but then refuses to close, or it opens behind other page content and is invisible.

Mobile navigation is critical for user experience, and a broken hamburger menu effectively makes your entire app unusable on phones and tablets. Users cannot access any page other than the one they landed on, causing immediate bounce rates and lost conversions.

This issue is extremely common in Bolt-generated apps because the AI creates the toggle logic and CSS transitions but doesn't always handle the interaction between state management, z-index stacking, and touch events correctly on real mobile devices.

Error Messages You Might See

Cannot read property 'classList' of null Warning: Maximum update depth exceeded TypeError: toggle is not a function Element is not clickable at point (x, y)
Cannot read property 'classList' of nullWarning: Maximum update depth exceededTypeError: toggle is not a functionElement is not clickable at point (x, y)

Common Causes

  • State toggle not updating — The isOpen state is set but the component doesn't re-render because of a stale closure or missing dependency in the toggle function
  • Z-index too low — The mobile menu panel renders behind the main content or hero section because its z-index is lower
  • Click event not firing on mobile — The onClick handler works with mouse clicks but doesn't respond to touch events on iOS Safari
  • CSS transition broken — The menu is set to translate off-screen but the transition property is missing, so the menu moves but is never visible
  • Menu overlay blocking scroll — The menu opens but a transparent overlay prevents tapping any menu items
  • Conditional rendering removes menu — Using {isOpen && } instead of toggling visibility, causing animation issues

How to Fix It

  1. Debug the toggle state — Add a console.log inside your toggle handler: const toggleMenu = () => { console.log('toggling', !isOpen); setIsOpen(!isOpen); } and verify it fires on tap
  2. Fix z-index stacking — Set the mobile menu to z-50 (or z-index: 50) and ensure parent containers don't create new stacking contexts that trap it
  3. Use button element for toggle — Replace div or span with a proper <button> element which handles both click and touch events natively
  4. Keep menu in DOM always — Instead of conditional rendering, use CSS classes to show/hide: className={`fixed inset-0 z-50 transition-transform ${isOpen ? 'translate-x-0' : '-translate-x-full'}`}
  5. Add backdrop and close behavior — Add a semi-transparent backdrop that closes the menu when tapped: <div onClick={() => setIsOpen(false)} className="fixed inset-0 bg-black/50 z-40" />

Real developers can help you.

BurnHavoc BurnHavoc Been around fixing other peoples code for 20 years. Daniel Vázquez Daniel Vázquez Software Engineer with over 10 years of experience on Startups, Government, big tech industry & consulting. AUXLE AUXLE I am a Full Stack Developer experienced in building Websites, Web apps and Cross Platform Mobile Apps for Startups and Companies. Meïr Ankri Meïr Ankri Full-stack developer specializing in React / Next.js / Node.js with 6+ years of experience. I've worked across various sectors including automotive (Reezocar/Société Générale), healthcare (Medical Link SaaS), and e-commerce (Glasman). I build web apps end-to-end, from architecture to production, with a focus on scalability, performance, and code quality. I also mentor junior developers and contribute to technical decisions and code reviews. Jared Hasson Jared Hasson Full time lead founding dev at a cyber security saas startup, with 10 yoe and a bachelor's in CS. Building & debugging software products is what I've spent my time on for forever PawelPloszaj PawelPloszaj I'm fronted developer with 10+ years of experience with big projects. I have small backend background too Alvin Voo Alvin Voo I’ve watched the tech landscape evolve over the last decade—from the structured days of Java Server Pages to the current "wild west" of Agentic-driven development. While AI can "vibe" a frontend into existence, I specialize in the architecture that keeps it from collapsing. My expertise lies in the critical backend infrastructure: the parts that must be fast, secure, and scalable. I thrive on high-pressure environments, such as when I had only three weeks to architect and launch an Ethereum redemption system with minimal prior crypto knowledge, turning it into a major revenue stream. What I bring to your project: Forensic Debugging: I don't just "patch" bugs; I use tools like Datadog and Explain Analyzers to map out bottlenecks and resolve root causes—like significantly reducing memory usage by optimizing complex DB joins. Full-Stack Context: Deep experience in Node.js and React, ensuring backends play perfectly with mobile and web teams. Sanity in the Age of AI: I bridge the gap between "best practices" and modern speed, ensuring your project isn't just built fast, but built to last. Anthony Akpan Anthony Akpan Developer with 8 years of experience building softwares fro startups Luca Liberati Luca Liberati I work on monoliths and microservices, backends and frontends, manage K8s clusters and love to design apps architecture David Olverson David Olverson Solo dev shipping production apps with AI-assisted development. I specialize in rescuing broken Lovable/Bolt/Cursor builds and taking them to production. 10+ apps shipped including SaaS CRMs, gaming platforms, real estate tools, and Discord bots. Stack: Next.js 16, TypeScript, Tailwind CSS, FastAPI, PostgreSQL, Prisma. I use Claude Code with 50+ custom skills for rapid delivery. Average turnaround: 2-4 weeks from broken prototype to production.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

Frequently Asked Questions

Why does my menu work on desktop but not on mobile?

Desktop browsers handle click events differently than mobile browsers. Touch events on iOS Safari have a 300ms delay and may not fire on non-interactive elements like div or span. Always use button elements for interactive controls.

How do I prevent the page from scrolling when the menu is open?

Add overflow-hidden to the body when the menu opens: useEffect(() => { document.body.style.overflow = isOpen ? 'hidden' : 'auto'; return () => { document.body.style.overflow = 'auto'; }; }, [isOpen]);

Related Bolt Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help