Android Studio Integration Guide

Overview

Android Studio is JetBrains-based and increasingly uses Gemini assistance for Compose, Gradle, crashes, logs, and Android workflows. Cup’n’String governs provider traffic, project secrets, local services, emulators, and build tooling.

Support level

Native Integration through JetBrains-family adapter + Gemini-aware governance

What Cup’n’String detects

• Android Studio process
• Gemini/Gemini Code Assist activity where observable
• Gradle/build/test subprocesses
• Emulator/local-service network access

What it governs

• Gemini/provider traffic
• Secrets and signing materials
• Localhost/emulator/container access
• Build and test network behavior

Recommended policies

• Protect keystores, signing configs, and cloud credentials
• Allow approved Google/Gemini endpoints
• Audit AI-assisted Gradle/build troubleshooting flows

Setup outline

1. Verify the Cup’n’String client is running.
2. Launch Android Studio; it is intercepted via the JetBrains-family native process adapter.
3. Configure shielding policies for keys (keystore, google-services.json).

Verification

Trigger an emulator run and check the logs in the console to ensure local network routing is attributed and protected under Android Studio.

Troubleshooting

If gradle sync fails, check if the system proxy settings are correctly picked up by gradle.properties.

Known limitations

Depth depends on available JetBrains/Android Studio hooks.