Android Studio 3.3 (Canary 12) does not have an option called "Activity & Fragment + ViewModel" and related configuration to create a Jetpack app (running on Windows 10).
Any suggestions?
This is a late follow-up, but I am experiencing the same bug on the now stable version 3.3 of Android Studio ("Activity & Fragment + ViewModel" does not appear on creation of a Jetpack application).
My current workaround is to create an application with "No Activity" and add the activity after the project has been created by going to New -> Activity -> Fragment + Viewmodel and adding it that way.
I assume it is a bug, not a feature and am looking for other posts about this issue. Not sure if Google is aware of it.
Related
I'm using the latest version of Android Studio and recent SDK tools and I'm following this guide to create a sample Jetpack app, but the Create Project wizard in my Android Studio does not have an option called Activity & Fragment + ViewModel and related configuration to create a Jetpack app (Tested on Linux). Any ideas?
Additional info:
Android Studio version: 3.1.2
Build your first Jetpack app
Launch Android Studio 3.2 or higher, and enter information in the Create Android Project and Target Android Devices as always.
I'm on Android Studio 3.3.1 in Linux and also not getting Activity & Fragment + ViewModel as an option in the Wizard. However I have a work around.
The Activity & Fragment + ViewModel code snippet shows up once you've created a project.
So create your new project with an Empty Activity. Right click inside the file view. Click on: New -> Activity -> Activity & Fragment + ViewModel
Then you can continue with the rest of the Jetpack tutorial.
I am new in android studio, and i just installed the version 3.0 canary 5 because it's supports Kotlin (and i want to learn kotlin). When I create i new project, the design editor seems to not work properly. When i drag a a component like a button, he just go on the corner and become not visible. But when i run the app and view it in my android phone it works correctly. The problem i guess is just with the design editor of android studio.
Screenshot of the problem
Any ideas?
Here is the solution Android Studio does not show layout preview
I had the same issue with AS 3.0 canary 5
Screen Shot #1 - Android Studio Project Gradle Build View
Screen Shot #2 - Android Studio Project Gradle Sync View
Going through the "Android Studio 2.2 Development Essentials book" and following along with the tutorial in chapter 3. Everything was OK until I completed a task in the Development Essentials book (chapter 3, page 24 in book) that said,
As we can see from the component tree hierarchy, the user interface
layout consists of a layout parent with a single child in the form of
a TextView object. If Android Studio has used a RelativeLayout manager
for the project, the first step is to convert it to a
ConstraintLayout. ConstraintLayout is a new and flexible layout
manager that is used in most projects in this book. To achieve this
conversion, right-click on the content_android_sample entry in the
Component Tree and select the Convert RelativeLayout to
ConstraintLayout menu option as shown below:
Upon completion of the above quoted tutorial task (in chapt. 3 of the Development Essentials book), an error was presented that said:
Error: Failed to resolve: com.android.support.constraint:constraint-layout:1.0.0-alpha1
Also, a rendering error was listed as well that said:
Rendering Problems The following classes could not be found:
- android.support.constraint.ConstraintLayout ( Add constraint-layout library dependency to the project, Fix Build Path, Edit XML, Create Class)
Any thoughts on how to fix this? Please see screen shots attached (above). I'm new to Android Studio.
Thank you very much for your time.
I am using the following OS and Android Studio version below:
Win7 professional 64 bit OS
Android Studio 2.2
Build# AI-145,3330264, Built on October 6, 2016
You need add check in..
exist a icon with name "SDK Manager" just click
open Settings -> Appearance & Behavior -> System Settings -> Android SDK -> SDK Tools
And in this dialog add:
ConstraintLayout for Android
Solver for ConstrainLayout
Then, here only you need close and open Android Studio.
Maybe only you can update to:
compile 'com.android.support.constraint:constraint-layout:1.0.0-alpha8'
Or update your dependency to:
compile 'com.android.support.constraint:constraint-layout:latest_version'
This should solve your error. Go to your build.gradle and change your implementation 'com.android.support.constraint:constraint-layout:1.0.0-beta7' to implementation 'com.android.support.constraint:constraint-layout:2.0.0-beta7' or to any latest
I recently upgraded to Android Studio 2.2.2 and the ability to add an activity during the Create New Project quick start is no longer available. Where/how can I add my first activity in to a project?
Thank you!
Unfortunately, there are some issues with latest 2.2.2 version of Android Studio, especially on Linux systems. Please delete/uninstall existing version and download 2.2.1 from tools.android.com.
I faced the same issue in android.2.2.3 "new activity" not listed, but a simple restart of android studio solves it. I restarted android studio and now it shows new activity option..
We have a 4 year old MonoTouch application, now a Xamarin.iOS application. It has a tag in each project
<MtouchSdkVersion>3.0</MtouchSdkVersion>
In the list of warnings with the current Xamarin.iOS and Xcode 6.1.1, I see
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets: Warning: The iOS SDK version '3.0' is not installed. Using newer version '8.1' instead'. ({myProjectName})
I could manually update this tag or remove it. I do not see in the Xamarin Studio where to configure this on each project. Thanks much.
That should map to the Project options, Build, iOS Build, General, SDK version combobox.
If not found it could show you Default (not sure about the logic) but, beside Default it will only let you select the SDK that the presently configured Xcode provides (e.g. for Xcode 6.1 would see 8.1 for device builds).
note: it's possible it was left over to that value during the project's conversion to unified (which implies switching to msbuild).