Dibya Sarothi
Dibya Sarothi
Automation & BotsProduction ReadySeptember 2026

TinDog Auto-Swiping Bot

Multi-Window OAuth Popup & Onboarding Automation Bot

Automates detached Chrome startup, Facebook/Facebark OAuth popup switching via window_handles, permission modals, and JS swipe execution.

TinDog Auto-Swiping Bot overview
Project Overview

An automated profile swiping bot built with Python and Selenium WebDriver for TinDog. Orchestrates OAuth popup window context switching (driver.window_handles), sequences through location, push notification, and cookie consent dialogs via explicit waits, and triggers swipes cleanly.

Problem Statement

OAuth logins open secondary browser popups that stall standard single-window Selenium scripts, while animated card overlays often intercept native WebDriver clicks.

Engineering Rationale

Multi-window focus switching and direct JavaScript event dispatch are essential skills for automating real OAuth web apps.

Engineering Objectives

Switch context seamlessly between base app window and OAuth popup window using driver.window_handles.
Handle sequential onboarding permission dialogs via WebDriverWait + expected_conditions.
Bypass UI animation interception using execute_script click dispatch.
Architecture Blueprint

System Architecture

Detached Chrome WebDriver script managing window handle lifecycles and explicit wait synchronization.

01

Multi-Window OAuth Switching

Captures base and popup handles dynamically via driver.window_handles, authenticates in popup, and restores primary window focus.

Core & Backend Implementation

  • Window-handle orchestration authenticating third-party login popups.
  • JavaScript click dispatch bypassing element-click-intercepted animation states.

Client & Interface Layer

  • Automated onboarding modal clearance (Location, Notifications, Cookie Consent) and card liking.

Data & Schema Design

Engine / Tier: Session Window State

Tracks multi-window handles and OAuth cookie tokens across tabs.

Core Models & Entities
WindowContextSwipeIteration

Authentication & Security Controls

Auth Model: OAuth credentials injected through python-dotenv
  • No plaintext credentials stored in repository.

Engineering Challenges & Technical Decisions

Key Challenges Solved

Challenge: ElementClickInterceptedException triggered by card transition overlays.
Engineering Solution: Executed arguments[0].click() directly through Selenium's browser JavaScript runtime.

Trade-Off Decisions

Decision: Explicit WebDriverWait Over Fixed Sleeps for Modals
Architectural Rationale: Responds deterministically as soon as permission dialogs become clickable.

Testing & Verification Methodology

Frameworks & Approach: End-to-End Detached Browser Verification
  • Confirmed seamless popup OAuth handoff and consecutive swipe loop.

Results & Engineering Takeaways

Gained fluency in multi-window WebDriver context switching and JS event dispatch workarounds.