-
Notifications
You must be signed in to change notification settings - Fork 119
Configurations not available to run #17
Comments
I am facing same issue. |
You need to add following line in AndroidManifest file in corresponding to that step you are solving - Currently no filter has that line. |
virat-shukla, what do I need to add to the AndroidManifest.xml file? Your answer was not clear. |
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. since there were many activities in this code, they left it to us - which activity we want to open. |
If it helps, please close the issue. Thanks |
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. |
On 12/9 I am having the same problem. PLEASE update codelab |
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. |
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 |
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.
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.
The text was updated successfully, but these errors were encountered: