Skip to lesson
Westlake RoboticsLearn
Vault

FIRST Tech Challenge

Loading progress…

  • Your FTC Software Map
  • Install Android Studio and SDK Tools
  • Connect with the Android Studio ADB Plugin
  • Open and Build the FTC SDK Project

Open and Build the FTC SDK Project

Open the reviewed FTC SDK project, identify TeamCode, complete Gradle sync, and produce a clean local build.

Workstation SetupSetup

In this lesson, you will:

  • Open the reviewed FTC SDK project root in Android Studio.
  • Distinguish Gradle sync, compilation, and deployment results.
  • Use the project requirement and exact error before changing any Java runtime.
  • Record a clean local build with the project revision and tool versions.

Freeze the project before troubleshooting

Record the FTC SDK release or repository commit and the team project revision before opening the build. A tutorial written for another SDK generation may have different Gradle files, package names, or APIs.

TeamCode is the team-owned boundary

Open the project root, allow Gradle sync to finish, and locate the TeamCode module. Treat sync errors, Java compile errors, and device deployment errors as separate outcomes. Android Studio already includes a runtime, so install or select another JDK only when the reviewed project requirement or exact Gradle error calls for it.

A local build is a software checkpoint

A successful build proves that the frozen source compiled in the recorded workstation environment. It does not prove installation, OpMode registration, wiring, or physical robot behavior.

Build with the project wrapperShell

# macOS or Linux
./gradlew -version
./gradlew assembleDebug

# Windows PowerShell
.\gradlew.bat -version
.\gradlew.bat assembleDebug

Practice

Open the reviewed project, complete Gradle sync, locate TeamCode, run the wrapper version and approved build commands, and save the project revision, reported runtime, tool versions, command, and final result. If it fails, record the first error without changing multiple versions at once.

Checks

  • The project release or commit is recorded.
  • Android Studio opened the project root and completed or precisely failed Gradle sync.
  • The TeamCode module is identified.
  • No Java runtime was changed without a project-specific requirement or error.
  • The wrapper build command and result are saved.
  • The result is described as a local compile check, not a robot deployment proof.

Lesson check

Check your understanding before moving on.

What does a successful assembleDebug result establish?
What should be recorded before changing versions after a failure?

0 of 2 answered

References

FTC Robot Controller repositoryOfficial FTC SDK source, releases, and release notes.Android build JDK guidanceUse only when a project-specific build requirement or error needs runtime troubleshooting.FIRST Tech Challenge Programming ResourcesOfficial FTC programming downloads and supported resources.
Loading lesson progress
Previous lessonConnect with the Android Studio ADB PluginNext lessonWhat an OpMode Does