Skip to content
This repository has been archived by the owner on Oct 27, 2020. It is now read-only.

No default configurations such as "TeamCode" #272

Open
rsshilli opened this issue Sep 21, 2020 · 5 comments
Open

No default configurations such as "TeamCode" #272

rsshilli opened this issue Sep 21, 2020 · 5 comments

Comments

@rsshilli
Copy link

rsshilli commented Sep 21, 2020

The Android Studio Guide on page 120 says:

Look towards the top of the Android Studio user interface and find the little green Play or Run button (which is
represented by a green triangle) next to the words “Team Code”. 

image

I don't have a "Team Code" configuration available by default. Maybe the latest version of Android Studio screwed it up somehow? I did attempt to clone SkyStone from scratch and re-import it into Android Studio. No run/debug configurations defined.

Either way, can somebody please show me the configuration that should be there? I'm trying to set it up myself:

image

@rsshilli
Copy link
Author

I found a workaround! I had to install old versions of the Android SDK:
image

Then when I re-opened my project they were there. Nice! It would be nice if this project just opened correctly at the start. Or if the Android Studio Guide was updated.

@Windwoes
Copy link
Member

"Please select Andorid SDK" likely means that AS didn't know where to find your Android SDK directory.

@TesDevelopment
Copy link

Just to clarify to fix this go to Tools > SDK Manager > an select Android 9.0(Pie) click apply and say yes to everything else. I had this problem and that fixed it. If this solved it remember to close the issue!

@rsshilli
Copy link
Author

rsshilli commented Oct 5, 2020

@TesDevelopment I thought that the final solution would be to fix the documentation (or even better, this repository to use Android 10.0).

Is every FTC student learning to code supposed to come find this ticket?

@Windwoes
Copy link
Member

Windwoes commented Oct 5, 2020

Android studio normally will automatically suggest to install the needed SDK version. In any case, changing the SDK to target 10.0 is by no means a trivial change, as targeting 10.0 requires significant changes in the handling of external storage and accessing USB devices.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants