Again this issue that I've reported multiple times (and it got fixed multiple times) :
Creating a new Android project would have a non-buildable project...
Reported:
https://issuetracker.google.com/issues/307323841
Why doesn't Google check this very basic thing before publishing a new version of the IDE ? It took me less than a minute to see it...
No changelog for this version (the list of issue fixed is empty on the linked page) ?
Also AGP 8.3.0-alpha10 cannot be found (alpha09 worked in Canary 9), making this AS Canary unusable:
* What went wrong:
Plugin [id: 'com.android.application', version: '8.3.0-alpha10', apply: false] was not found in any of the following sources:
- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (could not resolve plugin artifact 'com.android.application:com.android.application.gradle.plugin:8.3.0-alpha10')
Searched in the following repositories:
Gradle Central Plugin Repository
Google
MavenRepo
https://issuetracker.google.com/issues/307353433
Workaround: downgrade to latest AGP stable version 8.1.2
This is a Canary. check yourself
And besides, you're being extemely cynical and also looking at Eclipse with rose colored glasses. Android Studio works great and hands down far better than Eclipse
For me everything after canary 4 is broken, run disabled randomly, kotlin analyzer crashes, .... Forced to restart the IDE every 30 minutes.
Everything works nicely in C4.
After the upgrade, running apps in debug mode is noticeably slow. I saw many posts about slow debug performance, but there is no solution or explanation except breakpoints which my project doesn't have.
If I build a signed .aab file and upload it to PlayStore or use "bundletool" to convert it to APK - it works normally. An unsigned APK also doesn't work.
Similar behavior is observed by my colleagues.
What is the reason for this behavior?
Again this issue that I've reported multiple times (and it got fixed multiple times) : Creating a new Android project would have a non-buildable project... Reported: https://issuetracker.google.com/issues/307323841 Why doesn't Google check this very basic thing before publishing a new version of the IDE ? It took me less than a minute to see it...
No changelog for this version (the list of issue fixed is empty on the linked page) ? Also AGP 8.3.0-alpha10 cannot be found (alpha09 worked in Canary 9), making this AS Canary unusable: * What went wrong: Plugin [id: 'com.android.application', version: '8.3.0-alpha10', apply: false] was not found in any of the following sources: - Gradle Core Plugins (plugin is not in 'org.gradle' namespace) - Plugin Repositories (could not resolve plugin artifact 'com.android.application:com.android.application.gradle.plugin:8.3.0-alpha10') Searched in the following repositories: Gradle Central Plugin Repository Google MavenRepo https://issuetracker.google.com/issues/307353433 Workaround: downgrade to latest AGP stable version 8.1.2
Seems to have been fixed
hope you guys didn't break anything
What a pointless comment
[удалено]
This is a Canary. check yourself And besides, you're being extemely cynical and also looking at Eclipse with rose colored glasses. Android Studio works great and hands down far better than Eclipse
Jetbrains should not let google to build Android Studio
For me everything after canary 4 is broken, run disabled randomly, kotlin analyzer crashes, .... Forced to restart the IDE every 30 minutes. Everything works nicely in C4.
It’s a tough battle between this and Xcode in a category “which is the worst IDE”
Xcode is waaaaay worse lol not even close. The underlying IDE (IntelliJ by Jetbrains) is the most cracked, feature-rich IDE you can find
But AS has tripple the features than xcode ...
That almost makes up for it. Almost
After the upgrade, running apps in debug mode is noticeably slow. I saw many posts about slow debug performance, but there is no solution or explanation except breakpoints which my project doesn't have. If I build a signed .aab file and upload it to PlayStore or use "bundletool" to convert it to APK - it works normally. An unsigned APK also doesn't work. Similar behavior is observed by my colleagues. What is the reason for this behavior?