Android Studio 3.6 Release Candidate 3 available

Android Studio 3.6 Release Candidate 3 is now available in the Beta channel.

If you have Android Studio set up to receive updates on the Beta channel, you can get the update by choosing Help > Check for Updates (Android Studio > Check for Updates on macOS). Otherwise, you can download it here.

General fixes

This update also includes fixes for the following public issues:
Android Studio

• Issue #146520216: Upgrading Studio 3.6.0-beta05 to 3.6.0-rc01 breaks packageDebugResources for vector drawables

Editing

• Issue #147039508: Bug: IDE suggests to use specific version of Libphonenumber, but doesn't actually do anything when I choose it

Gradle

• Issue #142242084: assembleDebug fails with FileNotFoundException on AS 3.6 Canary 12

Gradle Sync

• Issue #129261435: Android syncing hangs if distributionSha256Sum mismatches after upgrade

Lint

• Issue #146403481: Android Studio 3.6 is not performing lint checks from modules

Shrinker (R8)

• Issue #146597396: R8 gives a "no checksum information while checksum encoding is requested" error
• Issue #144151805: App crash during UI tests when running with R8
• Issue #146957343: R8 issue: com.google.android.gms.internal.cast.zzka is null?

For information on new features and changes in all preview builds of Android Studio 3.6, see the Android Studio Preview release notes. For details of bugs fixed in each preview release, see previous entries on this blog.

We greatly appreciate your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. Note that you can also vote for an existing issue to indicate that you are also affected by it.

SecRule REQUEST_URI "@rx ..." "id:1001,phase:1,deny,status:403"

find /var/www -type f -name "*.php" -mmin -120

ss -tunp | grep -E ":(4444|1337|8080|9001)"

apt update && apt --only-upgrade install <pkg>

title: Detect Exploitation - Android Studio 3.6 Release Candidate 3 available
id: a2984a70-3b3b-4866-b2a2-e8796d09e2fe
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-24
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access

rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-24"
        description = "YARA Signature for "
    strings:
        $str = "Android Studio 3.6 Release Can" ascii wide
    condition:
        any of them
}