Bug: Fix Hamburger Menu Not Opening on Read Articles Page

[SB2318]

🐞 Bug Report

Description

The hamburger menu on the Read Articles page is not opening when tapped. Users are unable to access the navigation drawer from this screen.

This issue should be investigated and fixed to ensure consistent navigation behavior across the application.

---

📱 Affected Screen

• Read Articles (Mobile View)

---

🐛 Current Behavior

• Tapping the hamburger menu icon does not open the navigation drawer.
• No navigation action or visual feedback is triggered.
• Users cannot access the drawer menu from the Read Articles page.

---

✅ Expected Behavior

• Tapping the hamburger menu should immediately open the application's navigation drawer.
• The interaction should behave consistently with other screens in the app.
• The menu button should remain responsive after navigation, refresh, or theme changes.

---

🔍 Investigation Checklist

• Verify the hamburger icon's onPress handler is correctly wired.
• Ensure the screen is wrapped with the appropriate navigation container or drawer navigator.
• Confirm the correct navigation method (e.g., openDrawer()) is being called.
• Check for overlays, gestures, or components intercepting touch events.
• Validate header configuration and custom header implementation.
• Test on both Android and iOS.

---

🧪 Testing

Verify the following scenarios:

• Tap the hamburger icon to open the navigation drawer.
• Open and close the drawer multiple times.
• Confirm functionality after navigating back to the screen.
• Test in both Light and Dark themes.
• Ensure no touch or layout issues prevent interaction.

---

✅ Acceptance Criteria

• Hamburger menu opens the navigation drawer when tapped.
• Navigation works consistently with other application screens.
• No touch interception or layout issues prevent interaction.
• Functionality works after navigation and screen refresh.
• Compatible with both Light and Dark themes.
• Verified on both Android and iOS (if applicable).

[github-actions]

Thank you for creating this issue! We'll look into it as soon as possible. Your contributions are highly appreciated! 😊

---

🤖 Assignment Guidelines

To get assigned to this issue, simply leave a comment requesting assignment.
The AI bot will automatically assign you if you meet the following eligibility criteria:

1. You do not currently have any other active assigned issues in this repository.
2. If you were previously assigned an issue, you must have submitted a Pull Request for it before requesting a new one.

[github-actions]

This issue appears to already be tracked in an existing issue or pull request (#1329).

To keep discussions centralized, this issue will be closed as a duplicate.

Reasoning: The issue provides a clear problem statement, reproduction steps, and expected behavior, making it valid and in scope. It's a frontend-mobile bug related to navigation. It is a duplicate of issue #1329, which describes the same root problem of the hamburger menu being unresponsive on mobile devices, affecting a similar component and user flow. The difficulty is intermediate as it involves debugging core navigation functionality.

[Rashmi2806525]

hy @SB2318 i would like to solve this issue , assign it to me

[Rashmi2806525]

"Hi @SB2318, the bot is not assigning me automatically. Both my previous PRs #2027 and #2135 have been merged. Can you please manually assign issue #2168 to me? Thank you!"

[SB2318]

hy @SB2318 i would like to solve this issue , assign it to me

ask for assignment with this command

"/assign"

[SB2318]

/assign