← Back to dashboard

Bugs found

Human-readable list. Last generated 15 Sep 2026, 06:01 PM IST. Download Word file.

#Module/ScreenBug DescriptionSeverityFound OnStatus
1Splash screenWhen the app is launched with no network (Wi-Fi and mobile data off), it does not show an error or retry message. The first screen is still the notification permission dialog, with no indication that the device is offline. Expected: a clear offline or retry message so the user knows there is a network problem, rather than appearing stuck on the permission prompt.Medium15 Sep 2026Open
2Onboarding carousel"Skip" on Onboarding slide 1 behaves identically to "Next" — it advances to slide 2 ("Manage Everything In One Place") and does not bypass onboarding to Sign up, making the control functionally redundant. Get started on slide 2 is the only path to Sign up. Observed 15 Sep 2026 on com.l2b.app.qa (OnboardingCarouselTest.skipFromSlideOneGoesToSlideTwo).Medium15 Sep 2026Open
3Onboarding carouselRapid double/triple tap on slide 1 Next also activates slide 2 Get started (same bottom CTA slot). Three fast taps on Next skip slide 2 entirely and open Sign up. Rapid Skip does not do this (lands on slide 2 once). Observed 15 Sep 2026 (OnboardingCarouselTest.rapidDoubleTapSkipAndNextDoesNotDuplicate, Allure rapidNextLanding=signup).Medium15 Sep 2026Open
4Onboarding carouselPressing Back from onboarding slide 2 exits the app to the Android launcher instead of navigating to slide 1, AND the onboarding carousel does not persist across relaunch — combined effect: a single Back tap can force a user to repeat the entire onboarding flow from Language selection. Isolated 15 Sep 2026: Back from slide 2 landed on com.google.android.apps.nexuslauncher; Case 9 relaunch after Get started → Sign up returned to Welcome to L2B (language). (OnboardingCarouselTest.androidBackOnCarouselDoesNotCrash + carouselPersistenceAfterRelaunch).Medium15 Sep 2026Open
5Onboarding carouselOnboarding carousel progress dots (pill + circle above Next / Get started) have no content-desc or selected state in the UiAutomator tree. Screen readers cannot announce current slide position (page 1 of 2 vs page 2 of 2), and this also blocks reliable automated verification of dot-highlight sync. Visual screenshots show the correct pill, but the nodes are unlabelled. (OnboardingCarouselTest.progressDotsAreVisualOnlyNotInSelectedState).Low15 Sep 2026Open