IssueTracker

Thanks for the report. To let you know about progress on this:

• the project won't open on 4.0, as it uses AGP 4.1 features, which Studio 4.0 doesn't support;
• the PlayCoreKtx project has been updated so that it should open without trouble on 4.1 RC1;
• the issue with Studio looping over upgrading the plugin version is a real one, so it won't open on current canaries, which automatically attempt (and fail) to upgrade the project. I'm expecting that we will fix this before 4.2 Beta.

Thanks again!

I'm glad that it works for you in 4.1 RC 1 -- as and when new RCs (and 4.1 final) in the 4.1 series are released, the project will need a manual upgrade (which I expect we will do) in order for it to be cleanly openable.

I just tried with 4.2 Canary 10, and the project opened and built cleanly here. In your video from comment #5, one of the fixes suggested was to restart the Gradle daemons; my guess (only a guess) as to what happened there is that you had some stale daemons still running from a different session. I'd definitely be interested if you can reproduce a failure to open with 4.2 Canary 10 and definitively no stale state.

Thanks!

Hi,

Thanks for confirming that this works for you with Canary. I expect this to be generally the case from now on.

The upgrade code in 4.2 has been substantially rewritten compared to what will be released with 4.1. That means that (as I wrote in comment #6) if the version of Studio (e.g. 4.1 RC 3) is different from the version of AGP declared in the sample (e.g. 4.1.0-rc02), the project will fail to upgrade. This is a bug, but one that will have to wait for the 4.2 release for the fix to be available in a stable release. In mitigation, once Android Studio 4.1 is released, the sample projects will open in that without warnings about compatibility, though automatic project upgrades will continue not to work; the issues surrounding compatibility errors when opening the samples in beta/RC are inherent to the pre-release nature, and will not be an issue once 4.1 is released.

To try to answer the question about the state of your system and why it matters: starting Android Studio also starts up a bunch of other processes; closing Android Studio doesn't always close them (for valid reasons; they might have longer-running tasks to complete). If you start up a different version of Studio while those tasks are still running, the new Studio may be unable to start its own versions of those processes, or may try to communicate with the already existing ones, only to discover that they don't speak the same protocol. This can happen; Android Studio detects it, and tries to guide the user into fixing it appropriately (by terminating the old processes, if they judge that it's safe to do so).

Thanks once again for the update.

I think that we have made substantial improvements to the compatibility story between different versions of AGP and different versions of sample projects. It's not perfect, but I think it's better, and we continue to try to communicate best practice.

Broadly, there will always be windows of time where some artifacts will be incompatible with some others; projects might use features in new versions of build tools, or experimental development in the tools may accidentally break old projects. We try to catch these things, but also our resources to do that are not infinite, so we sadly have to accept that sometimes things will not be compatible with each other, even if Google is ultimately responsible for many of the things (in this case, Android Studio and the sample projects).

I hope that the general improvements in compatibility and project upgrades have made an impact. And if you do happen to notice specific current releases being incompatible with each other, please do continue to report that: it's a signal that something might have gone wrong somewhere! Thanks once again for the report.

@10 Can't confirm. It's not "sometimes". It's almost always. Steps:

1. Choose "File"->"import sample"
2. Choose something quite basic. I chose "Recycler view sample (kotlin)"

It gives you an error right away:

• Exception is: org.gradle.groovy.scripts.ScriptCompilationException: Could not compile settings file 'C:\Users\User\AndroidStudioProjects\RecyclerViewSampleKotlin\settings.gradle'. ...

This is the experience you provide to new developers. And I know for a fact this issue exists many years. Compatibility with projects can get broken even in less than a year than the project was created. Doesn't even have to be a part of the official samples.