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

Configurations not available to run #17

Open
drewahearn opened this issue Apr 27, 2018 · 9 comments
Open

Configurations not available to run #17

drewahearn opened this issue Apr 27, 2018 · 9 comments

Comments

@drewahearn
Copy link

drewahearn commented Apr 27, 2018

Downloaded the source and compiled/updated. the "Step 1" configuration is not available to run. The only config available is "app" which doesn't run.
as1

How can one fix this?

Android Studio Version 3.1.1
The resolution for this is to either update the source code, adding the appropriate Run Configurations, or update the CodeLab Instructions describing how users can properly create the needed Run Configurations.

@ashu879
Copy link

ashu879 commented Apr 27, 2018

I am facing same issue.

@virat-shukla
Copy link

virat-shukla commented Apr 30, 2018

You need to add following line in AndroidManifest file in corresponding to that step you are solving -
<category android:name="android.intent.category.LAUNCHER"/>

Currently no filter has that line.

@drewahearn
Copy link
Author

virat-shukla, what do I need to add to the AndroidManifest.xml file? Your answer was not clear.

@viratshukla
Copy link

viratshukla commented May 2, 2018

In order to launch an activity from your phone's default launcher, you need to have following lines of code in one of your activity. Only then it will be listed in your list of installed apps.
<intent-filter> <action android:name="android.intent.action.MAIN"/> <category android:name="android.intent.category.LAUNCHER"/> </intent-filter>

since there were many activities in this code, they left it to us - which activity we want to open.
You have to put these lines in activity tag which you are currently working `upon.

@virat-shukla
Copy link

If it helps, please close the issue. Thanks

@drewahearn
Copy link
Author

The instructions for the CodeLab need to be updated to reflect the need to create/update your own Run Configurations.

The existing CodeLab instructions assume all the pre-defined Run Configurations are in place.

@thigbie
Copy link

thigbie commented Dec 10, 2018

On 12/9 I am having the same problem. PLEASE update codelab

@thigbie
Copy link

thigbie commented Dec 10, 2018

I give up. I got step 1 and 2 to work. But, from 3 on nothing works. I went back to step1 and now it doesn't work. I'm spending so much time figuring out the lessons, I'm not able to focus on the purpose of the lesson. I'll go somewhere else to learn.

@alketola
Copy link

alketola commented Mar 3, 2019

Sad but true, the codelab is not updated to reflect the instructions, and work as such in AndroidStudio 3.3.

Anyway, the (blunt) advice given already above helps to compile... one just need to consider carefully what to copy and paste, understanding the meaning and purpose of AndroidManifest.xml. :

in AndroidManifest.xml , The intents and actions for each Activity are defined. In the codelab, all actions are incomplete, is missing. Just within each <Intent>, within <IntentFilter>, after <action /> tag, please paste
<category android:name="android.intent.category.LAUNCHER"/>
Do it to one activity in the AndroidManifest.xml at a time, and then the activity with the line above gets run as app configuration. I hope this helps to workaround the issue.

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

6 participants