How ethanarbuckle/carplay-cast works
Project Type & Purpose
• This is an iOS jailbreak tweak (“carplay-cast”) that hooks into SpringBoard/CarPlay/UIApplication processes to enable any app on CarPlay (iOS 14+).
• It includes:
• A Theos build system for compiling Objective-C++/logos hooks
• A Preference pane bundle for Settings
• Debian packaging metadata & a repo uploader script
• A Python Cloud Function for crash reporting
• End-to-end tests (Cypress)
• GitHub Actions for CI
High-Level Components
A. Developer & CI Environment
• Source code (src/, carplayenableprefs/, control, Makefile)
• .github/workflows/c-cpp.yml (build & test)
• tests/*.cy (Cypress E2E tests)
B. Packaging & Distribution
• control, postinst_postrm, repo/push_deb_to_repo.py
• Debian repo (repo/Release)
C. Device Runtime (Jailbroken iOS)
• Tweak injection into:
– SpringBoard (hooks/SpringBoard.xm)
– CarPlay daemon (hooks/CarPlay.xm)
– UIApplication (hooks/UIApplication.xm)
• Core logic (src/CRCarplayWindow.mm, src/CRPreferences.mm, src/common.h)
• Preference bundle (carplayenableprefs/)
D. Crash-Reporting Backend
• Cloud Function (crash_reporting_cloud_function/main.py, tasks.py)
• Requirements, Pipfile, log_browser.py
• External storage or Pub/Sub (implicit)
Interactions & Data Flows
1. Developer commits → GitHub Actions builds & runs Cypress tests → produces .deb
2. push_deb_to_repo.py uploads .deb to package repo
3. User on jailbroken device installs .deb from repo
4. Tweak code hooks into system processes at runtime
5. If a crash occurs, reporting.mm captures stack trace & POSTs to Cloud Function endpoint
6. Cloud Function processes & stores logs; log_browser.py fetches them for review
Architectural Patterns & Principles
• Modular Theos project: separate hook libraries, common code, preference UI
• Debian packaging for distribution via APT repo
• Serverless crash reporting (event-driven Cloud Function)
• CI/CD with GitHub Actions
• E2E automated testing (Cypress)