Release notes

Android 12 Beta 5

Beta 5

Release date: September 8, 2021
Build: SPB5.210812.002
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: August 2021
Google Play services: 21.26.21
API diff:

About Android 12 Beta 5

Beta 5 is now available with the latest features and changes to try. Beta 5 is the last milestone before the final release, so update your environment and perform your final compatibility testing so you can publish any necessary compatibility updates ahead of the final release.

As with previous versions, Android 12 includes behavior changes to help improve performance, battery life, security, and privacy. In some cases, these changes can affect apps until they are updated to support Android 12, so you might see impacts ranging from minor issues to more significant limitations. In general, most apps will work as expected, as will most APIs and features, but please review the known issues listed on this page to get a better idea of what to expect.

How to get Beta 5

You can install this release on any Pixel 3, 3a, 4, 4a, 5, or 5a series device.

If you’re already running a Developer Preview or Beta build, you will automatically receive an over-the-air (OTA) update to Beta 5. Remember to update your Android 12 SDK and the Android Emulator as well before you continue trying the latest features and changes. The best way to do this is using the SDK Manager in the latest preview version of Android Studio.

If Beta 5 is the first Android 12 release that you're trying, see Get Android 12 for details on how to get started.

General advisories

Please be aware of these general notes about the release:

  • This release might have various stability, battery, or performance issues on supported devices.
  • For users with accessibility needs, this release might not be appropriate for daily use.
  • Some apps might not function as expected when running on this release. This includes Google’s apps as well as other apps.
  • Android 12 Beta builds are not Compatibility Test Suite (CTS) approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 12 Beta builds.

Get support

Two primary support channels are available to you when developing and testing with the Android 12 Beta. The channel you should use to get support depends on where you are encountering your issue.

Support for issues with Pixel devices, system issues, and issues with Google apps

Use the Android Beta issue tracker to create new issues and to view and track issues that you and other developers have submitted. Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .

See Where to report issues to find an issue template that best matches the type of issue that you are encountering.

Support for issues with non-Pixel devices

To report issues with eligible devices from our device-maker partners, see the Android 12 Beta devices page to find a link to the device-maker's Android 12 Beta site.

Support for issues with other apps

Contact the app developer directly.

To discuss issues or ideas with other developers working with the Android 12 Beta, join the android_beta community on Reddit.

Top resolved issues

The following top issues have been resolved in Android 12 Beta 5:

Developer-reported issues

  • Fixed an issue where the media controls sometimes wouldn't appear after rotating the device. (Issue #196305826)
  • Fixed an issue that caused Android System Intelligence to crash intermittently. (Issue #197053372)
  • Fixed an issue where the Settings app would stop responding when the preferred mobile network type was changed. (Issue #196729167)
  • Fixed an issue that prevented the device from switching between a physical SIM and an eSIM in certain cases. (Issue #196560081)

Other resolved issues

  • Fixed an issue where, in some cases after updating a device to the next Beta release, Google Maps crashed whenever it was launched by a secondary user.
  • Fixed an issue for devices with multiple users where, in some cases after updating the device to the next Beta release, the device crashed and rebooted when trying to switch to a secondary user.

Top open issues

See top open issues for the latest list of top open issues that have been reported by developers and users.

Other known issues

Based on our testing, you might encounter the following issues when using Android 12 Beta 5. These issues are already known, so there’s no need to file additional reports for similar issues.

All apps

  • In some scenarios, users of apps that have been granted the Display over other apps permission and render full screen overlays might find touches blocked on Android 12 until the developer updates the app. Affected users can temporarily turn off the permission in Settings, which can always be accessed using the settings icon in the notification shade. If an app you use is affected by this issue, you can contact the app developer directly to let them know.
  • When a user attempts to add another account to the device under Settings > Passwords & accounts, the UI turns black and the back button becomes unresponsive.

Google apps

  • When connected to a Bluetooth headset, users running the beta version of the Phone by Google app might experience a crash loop when trying to make a call. This issue is caused by the Phone app not having the required Nearby Devices permission.

    To work around this issue, grant the Nearby Devices permission to the Phone app. To do this, long press the Phone app and tap App info , then go to Permissions > Nearby devices and select Allow.

    Users should also check the Play Store for any Phone by Google beta updates that are available to receive the latest fixes.

Android platform

  • Apps that target Android 12 can currently request the ACCESS_FINE_LOCATION by itself, without also requesting the ACCESS_COARSE_LOCATION permission. Normally, such apps must also request the ACCESS_COARSE_LOCATION permission if they request the ACCESS_FINE_LOCATION permission, as described in the guide about approximate location.

Android Studio and tools

  • When installing an app that has a targetSdkVersion of "S" from Android Studio, developers might see the following error:

    Installation did not succeed.
    The application could not be installed: INSTALL_FAILED_VERIFICATION_FAILURE
    List of apks:
    [0] '.../build/outputs/apk/debug/app-debug.apk'
    Installation failed due to: 'null'
    

    The likely cause is that one or more of the app's activities, services, or broadcast receivers includes intent-filters, but does not explicitly set a value for android:exported. Android 12 requires setting an explicit value for this attribute on all <activity>, <service>, and <receiver> components that also have an <intent-filter> defined. For more information, see Safer exporting of components. Note: This issue is already solved in the latest release of Android Studio Arctic Fox. To get the latest fixes and enhancements when targeting Android 12, we recommend installing a preview version of Android Studio alongside your stable version.

  • The latest version of the Android SDK Build Tools (31.0.0) is not compatible with Android Studio versions prior to Android Studio Arctic Fox.

Android Auto

  • While using Android Auto, on the launcher page, the scroll bar may not work for some users. We are working on a fix for this issue.
  • Some users may experience device and/or Android Auto freezing when using Android Auto. We are investigating this issue.

Android TV

  • Hotplugging the HDMI cable might cause video playback to fail on some display sinks.

Previous Beta releases

Android 12 Beta 4.1 and 4

Beta 4.1

Release date: August 25, 2021
Build: SPB4.210715.014
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: August 2021
Google Play services: 21.24.18
API diff:

Beta 4

Release date: August 11, 2021
Build: SPB4.210715.011
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: August 2021
Google Play services: 21.24.18
API diff:

Android 12 Beta 4.1 (August 2021)

If you’re already running a Developer Preview or Beta build, you will automatically receive an over-the-air (OTA) update to Beta 4.1.

This minor update to Android 12 Beta 4 includes the following fixes:

  • Fixed an issue that caused some devices to get stuck in a boot loop after restarting the device. (Issue #193789343)
  • Fixed an issue where heads-up notifications were sometimes not shown, requiring the user to swipe into the notification drawer to view them. (Issue #196264672)
  • Fixed an issue where the device volume controls sometimes did not work when casting. (Issue #196528545)
  • Fixed an issue where Face Unlock did not work on some devices. (Issue #189819846)
  • Fixed an issue that prevented users from granting the Nearby Devices permission to the Phone app in settings. Users who are experiencing a crash loop with the Phone app when trying to make a call over Bluetooth can now grant the required permission. To do this, long press the Phone app and tap App info , then go to Permissions > Nearby devices and select Allow. (Issue #196325588)
  • Fixed an issue where, after connecting the phone to a VPN, the phone could not connect to the internet. (Issue #196237480)

What's new in Beta 4

Google Play services Ad ID

As previously announced, Google Play services will introduce some changes to Ad ID functionality. When users opt out of interest-based advertising or ads personalization, their advertising ID will be removed and replaced with a string of zeros. Also, apps that update their target API level to 31 must declare a new Google Play services permission in the manifest in order to use advertising ID.

The roll out of these changes in Google Play services version 21.30.13 and higher will begin with Android 12 Beta 4 on Pixel and will expand to all apps running on devices that support Google Play in early 2022.

Top resolved issues

The following top issues have been resolved in Android 12 Beta 4:

Developer-reported issues
  • Fixed issues that prevented some notifications about missed calls from being dismissed. (Issue #193718971, Issue #194388100)
  • Fixed issues where system theme colors did not apply to some Quick Settings tiles. (Issue #190633032, Issue #190338020)
  • Fixed an issue where Quick Settings tiles did not align to the grid when dragging or rearranging them. (Issue #188641280)
  • Fixed an issue where the alarm and mute icons did not display in the notification bar. (Issue #186769656)
  • Fixed an issue where the primary Home screen was blank when swiping back to it from another page. (Issue #189435745)
  • Fixed an issue where, when a Bluetooth device was connected, audio could not be heard after routing the audio to the phone during a call. (Issue #192585637)
  • Fixed an issue where the Calendar widget wouldn't load after it was added to the Home screen. (Issue #188799206)
  • Fixed an issue where toggles for some options in the Settings app were not visible. (Issue #193727765)
  • Fixed an issue where widgets would sometimes disappear after restarting the device. (Issue #191363476)
  • Fixed an issue where RCS messages did not work when a VPN was active. (Issue #189577131)
  • Fixed issues that sometimes caused devices to crash and restart. (Issue #194272305)
  • Fixed an issue that caused multiple notifications about foreground service launch restrictions to display. (Issue #194081560)
  • Fixed an issue where the wrong app would sometimes open when opening an app from the dock or Home screen area. (Issue #194766697)
  • Fixed an issue where double-tapping the device's screen would not wake it in some cases. (Issue #190453834)
  • Fixed an issue where the cell signal strength was not displayed in the status bar. (Issue #190894572)
  • Fixed an issue where if a screen recorder was active, the notification shade did not animate properly when closing. (Issue #191276597)

Other resolved issues

  • Fixed an issue where, when playing music on Youtube Music on Android Auto, some users experienced audio playing out of the phone instead of the vehicle speakers or no audio at all in Toyota Cars.
  • Fixed an issue where, when using Google Maps navigation on Android Auto, some users experienced issues with text being blurry.
  • Fixed an issue where users couldn't select a destination in Waze while using Android Auto.
  • Fixed an issue where the phone became unresponsive or stuck on the lock screen after starting Android Auto.
  • Fixed an issue where, in some scenarios, Google Maps could not provide different route options while using Android Auto.
  • Fixed an issue on Android Auto where music would pause when the phone was locked.
  • Fixed an issue on Android Auto where users sometimes heard Music audio while trying to reply to an SMS using the Google Assistant.
  • Fixed an issue on Android Auto where Automatic Day and Night switching did not work.

Top open issues

See top open issues for the latest list of top open issues that have been reported by developers and users.

Other known issues

Based on our testing, you might encounter the following issues when using Android 12 Beta 4. These issues are already known, so there’s no need to file additional reports for similar issues.

All apps
  • In some scenarios, users of apps that have been granted the Display over other apps permission and render full screen overlays might find touches blocked on Android 12 until the developer updates the app. Affected users can temporarily turn off the permission in Settings, which can always be accessed using the settings icon in the notification shade. If an app you use is affected by this issue, you can contact the app developer directly to let them know.
  • When a user attempts to add another account to the device under Settings > Passwords & accounts, the UI turns black and the back button becomes unresponsive.
Google apps
  • When connected to a Bluetooth headset, users running the beta version of the Phone app might experience a crash loop when trying to make a call. This issue is caused by the Phone app not having the required Nearby Devices permission. In addition, users can't grant the Nearby Devices permission to the Phone app in system settings, either from the Permissions screen in App info, or through the Permissions manager.

    To work around these issues, users can grant the Nearby Devices permissions to the Phone app using the following adb commands. If you need to set up adb first, see Connect to a device over Wi-Fi.

    adb shell pm grant com.google.android.dialer android.permission.BLUETOOTH_SCAN && adb shell pm grant com.google.android.dialer android.permission.BLUETOOTH_CONNECT && adb shell pm grant com.google.android.dialer android.permission.BLUETOOTH_ADVERTISE 
    

    Users should also check the Play Store for any Phone by Google beta updates that are available to receive the latest fixes.

  • In some cases after updating a device to Beta 4, Google Maps crashes whenever it is launched by a secondary user.

Android platform
  • Apps that target Android 12 can currently request the ACCESS_FINE_LOCATION by itself, without also requesting the ACCESS_COARSE_LOCATION permission. Normally, such apps must also request the ACCESS_COARSE_LOCATION permission if they request the ACCESS_FINE_LOCATION permission, as described in the guide about approximate location.
  • For devices with multiple users, in some cases after updating the device to Beta 4, the device crashes and reboots when trying to switch to a secondary user.
Android Studio and tools
  • When installing an app that has a targetSdkVersion of "S" from Android Studio, developers might see the following error:

    Installation did not succeed.
    The application could not be installed: INSTALL_FAILED_VERIFICATION_FAILURE
    List of apks:
    [0] '.../build/outputs/apk/debug/app-debug.apk'
    Installation failed due to: 'null'
    

    The likely cause is that one or more of the app's activities, services, or broadcast receivers includes intent-filters, but does not explicitly set a value for android:exported. Android 12 requires setting an explicit value for this attribute on all <activity>, <service>, and <receiver> components that also have an <intent-filter> defined. For more information, see Safer exporting of components. Note: This issue is already solved in the latest release of Android Studio Arctic Fox. To get the latest fixes and enhancements when targeting Android 12, we recommend installing a preview version of Android Studio alongside your stable version.

  • The latest preview version of the Android SDK Build Tools (31.0.0) is not compatible with Android Studio versions prior to Android Studio Arctic Fox.

Android Auto
  • After a user receives the OTA from Android 11 to Android 12 Beta and using Wireless Android Auto, some users may encounter a crash with Android Auto when trying to establish a Bluetooth connection. We are looking into this and a fix will be made available in the next Android 12 Beta release.
Android TV
  • Hotplugging the HDMI cable might cause video playback to fail on some display sinks.
  • Android Google Home App (GHA) version 2.42.1.11 or above is required to perform the 2nd screen set up. Performing set up using the iOS app or by using the remote are intact.

Android 12 Beta 3.1 and 3

Beta 3.1

Release date: July 26, 2021
Build: SPB3.210618.016
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: July 2021
Google Play services: 21.24.13
API diff:

Beta 3

Release date: July 14, 2021
Build: SPB3.210618.013
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: July 2021
Google Play services: 21.24.13
API diff:

Android 12 Beta 3.1 (July 2021)

If you’re already running a Developer Preview or Beta build, you will automatically receive an over-the-air (OTA) update to Beta 3.1.

This minor update to Android 12 Beta 3 includes stability improvements as well as the following fixes:

  • Fixed an issue that caused some devices to get stuck in a boot loop after restarting the device. (Issue #193789343)
  • Fixed an issue that sometimes caused the System UI to crash.
  • Fixed an issue that sometimes caused the Android low memory killer daemon (lmkd) to excessively kill processes.

What's new in Beta 3

Android 12 Beta 3 includes several new features and changes to try out:

Top resolved issues

The following top issues have been resolved in Android 12 Beta 3:

Developer-reported issues
  • Fixed various issues with WebView that could make apps crash intermittently.
  • Fixed an issue where the date did not appear in the notification shade. (Issue #189569006)
  • Fixed issues where a device sometimes stopped responding to touch input in apps or on the Home screen. (Issue #189426854)
  • Fixed an issue where screen-on time was missing from battery usage information in the Settings app. (Issue #188657464)
  • Fixed an issue where the estimated amount of remaining battery in the status bar displayed off of the screen. (Issue #188616134)
  • Fixed an issue where sometimes a black bar appeared on the lock screen. (Issue #190738110)
  • Fixed an issue where the App Overview button stopped working when using 3-button navigation. (Issue #188969484)
  • Fixed an issue where volume controls and sliders were not displayed correctly. (Issue #190795682)
  • Fixed an issue where the brightness slider in Quick Settings moved to the minimum value when the phone was locked. (Issue #190784671)
  • Fixed an issue where the phone locked when launching the camera by double-pressing the power button. (Issue #188797848)
  • Fixed issues where the system incorrectly applied fullscreen and immersive mode on the home screen and in some apps. (Issue #189233176, Issue #180691018)
  • Fixed an issue where the page indicator dots for Quick Settings were incorrect. (Issue #189108526)
  • Fixed an issue where the notification shade sometimes flickered when swiping down to access notifications. (Issue #189744186)
  • Fixed an issue where sometimes the brightness was lower on one half of the screen when viewing apps in landscape mode. (Issue #190064553)
  • Fixed an issue where the phone indicated that a phone call was still ongoing even after the call had ended. (Issue #191838222)
  • Fixed issues that prevented notification bubbles from opening in some apps. (Issue #189350738)
  • Fixed an issue where toggling wallet options off in a device's lock screen settings did not remove wallet options from the lock screen. (Issue #190805901)
  • Fixed an issue where the Settings app crashed when a user tried to access Themes and Styles settings. (Issue #190786058)
  • Fixed issues that prevented some apps from printing files or photos. (Issue #190169675)
  • Fixed an issue where the icon in the volume slider was not centered when the volume was set to the minimum level. (Issue #190577754)
Other resolved issues
  • Fixed an issue where app icons were sometimes cut off when using the SplashScreen API.
  • Fixed an issue where, after setting an Animated Vector Drawable and a setOnExitAnimationListener(), the vector drawable's animation stopped when the callback was called.
  • Fixed an issue for devices that had both a device-wide password and a work profile security challenge where the work challenge did not prompt the user to unlock when a user tapped a work app’s notification on the lock screen.

Top open issues

See top open issues for the latest list of top open issues that have been reported by developers and users.

Other known issues

Based on our testing, you might encounter the following issues when using Android 12 Beta 3. These issues are already known, so there’s no need to file additional reports for similar issues.

All apps
  • In some scenarios, users of apps that have been granted the Display over other apps permission and render full screen overlays might find touches blocked on Android 12 until the developer updates the app. Affected users can temporarily turn off the permission in Settings, which can always be accessed using the settings icon in the notification shade. If an app you use is affected by this issue, you can contact the app developer directly to let them know.
  • When a user attempts to add another account to the device under Settings > Passwords & accounts, the UI turns black and the back button becomes unresponsive.
Google apps
  • In some cases after updating a device to Beta 3, Google Maps crashes whenever it is launched by a secondary user.
Android platform
  • For devices with multiple users, in some cases after updating the device to Beta 3, the device crashes and reboots when trying to switch to a secondary user.
Android Studio and tools
  • When installing an app that has a targetSdkVersion of "S" from Android Studio, developers might see the following error:

    Installation did not succeed.
    The application could not be installed: INSTALL_FAILED_VERIFICATION_FAILURE
    List of apks:
    [0] '.../build/outputs/apk/debug/app-debug.apk'
    Installation failed due to: 'null'
    

    The likely cause is that one or more of the app's activities, services, or broadcast receivers includes intent-filters, but does not explicitly set a value for android:exported. Android 12 requires setting an explicit value for this attribute on all <activity>, <service>, and <receiver> components that also have an <intent-filter> defined. For more information, see Safer exporting of components. Note: This issue is already solved in the latest preview release of Android Studio Arctic Fox. To get the latest fixes and enhancements when targeting Android 12, we recommend installing a preview version of Android Studio alongside your stable version.

  • The latest preview version of the Android SDK Build Tools (31.0.0) is not compatible with Android Studio versions prior to Android Studio Arctic Fox.

Android Auto
  • When playing music on Youtube Music on Android Auto, some users may experience audio playing out of the phone instead of the vehicle speakers or no audio at all in Toyota Cars.
  • When using Google Maps navigation on Android Auto, some users may experience issues with text being blurry.
  • Users may face issues while selecting a destination in Waze.
  • Phone may become unresponsive or stuck on the lock screen after starting Android Auto.
  • In some scenarios, Google Maps might not be able to provide different route options while using Android Auto.
  • Music may get paused when the phone is locked.
  • Users might hear Music audio while trying to reply to an SMS using the Google Assistant.
  • Automatic Day and Night switching may not work.
Android TV
  • Hotplugging the HDMI cable might cause video playback to fail on some display sinks.

Android 12 Beta 2.1 and 2

Beta 2.1

Release date: June 23, 2021
Build: SPB2.210513.011
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: June 2021
Google Play services: 21.18.16
API diff:

Beta 2

Release date: June 9, 2021
Build: SPB2.210513.007
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: June 2021
Google Play services: 21.18.16
API diff:

Android 12 Beta 2.1 (June 2021)

If you’re already running a Developer Preview or Beta build, you will automatically receive an over-the-air (OTA) update to Beta 2.1.

This minor update to Android 12 Beta 2 includes various stability improvements as well as the following fixes:

  • Fixed an issue that prevented users from accessing things on the lock screen. For example, swiping down for the notification shade, swiping away notifications, or swiping up to unlock the phone. (Issue #190702454)
  • Fixed issues that caused information such as weather and calendar events to not appear in the At a Glance widget on the home screen or lock screen. (Issue #190700432, Issue #190644743)
  • Fixed an issue that sometimes caused flickering or jittery animations when accessing recent apps with gesture navigation.
  • Fixed an issue that sometimes caused microphone and camera permission indicators to get stuck and disappear until the phone was rebooted.
  • Fixed an issue when using the Android Emulator with an Android Virtual Device (AVD) running Android 12 that prevented the AVD from connecting to the internet.
  • Fixed an issue where after taking Beta and resetting the device, some users were stuck on the setup wizard (Issue #190082536).

What's new in Beta 2

Android 12 Beta 2 includes several new features and changes to try out:

Top resolved issues

The following issues have been resolved in Android 12 Beta 2:

Developer-reported issues
  • Fixed various issues that could cause devices to crash and restart. (Issue #188608172)
  • Fixed an issue that caused the Settings app to crash when accessing the Accounts screen. (Issue #188572264)
  • Fixed issues that caused the gesture navigation indicator to be displayed in the wrong place on the screen after switching the device's screen orientation. (Issue #186487188, Issue #186203723)
  • Fixed issues that caused live wallpapers to crash and revert back to another wallpaper. (Issue #188636390, Issue #186092946)
  • Fixed an issue that caused the one-handed mode overlay information to remain even after the user exited one-handed mode. (Issue #188809589)
  • Fixed an issue that prevented notifications from being cleared when a user tapped Mark as read or Done on a notification. (Issue #183140902)
  • Fixed issues that caused no haptic feedback to occur when using certain gestures or performing certain actions. (Issue #188643385, Issue #188647132)
  • Fixed an issue that caused the system volume bar to appear larger than intended. (Issue #188865157)
  • Fixed an issue that prevented Always On Display mode from working in certain cases. (Issue #189298635)
  • Fixed an issue that caused a NullPointerException to be thrown when calling the setDeviceAddress() method using a device Bluetooth address that was null. (Issue #186574846)

Top open issues

See top open issues for the latest list of top open issues that have been reported by developers and users.

Other known issues

Based on our testing, you might encounter the following issues when using Android 12 Beta 2. These issues are already known, so there’s no need to file additional reports for similar issues.

All apps
  • Due to an issue with WebView, users who install Android Beta 2 on a device that is currently running a public release version of Android may experience intermittent app crashes. To work around this issue, disable and then re-enable Android System WebView by going to Settings > Apps > All apps > Android System WebView > Disable > Disable app > Enable.
  • In some scenarios, users of apps that have been granted the Display over other apps permission and render full screen overlays might find touches blocked on Android 12 until the developer updates the app. Affected users can temporarily turn off the permission in Settings, which can always be accessed using the settings icon in the notification shade. If an app you use is affected by this issue, you can contact the app developer directly to let them know.
  • When a user attempts to add another account to the device under Settings > Passwords & accounts, the UI turns black and the back button becomes unresponsive.
Google apps
  • In some cases after updating a device to Beta 2, Google Maps crashes whenever it is launched by a secondary user.
  • The Block calls from unidentified callers dialer setting is disabled in Android Beta 1 and Beta 2. This setting is enabled again starting with Beta 2.1.
Android platform
  • When using the SplashScreen API, app icons are sometimes cut off.
  • When using the SplashScreen API, after setting an Animated Vector Drawable and a setOnExitAnimationListener(), the vector drawable's animation stops when the callback is called.
Android Studio and tools
  • When installing an app that has a targetSdkVersion of "S" from Android Studio, developers might see the following error:

    Installation did not succeed.
    The application could not be installed: INSTALL_FAILED_VERIFICATION_FAILURE
    List of apks:
    [0] '.../build/outputs/apk/debug/app-debug.apk'
    Installation failed due to: 'null'
    

    The likely cause is that one or more of the app's activities, services, or broadcast receivers includes intent-filters, but does not explicitly set a value for android:exported. Android 12 requires setting an explicit value for this attribute on all <activity>, <service>, and <receiver> components that also have an <intent-filter> defined. For more information, see Safer exporting of components. Note: This issue is already solved in the latest canary release of Android Studio Arctic Fox. To get the latest fixes and enhancements when targeting Android 12, we recommend installing a preview version of Android Studio alongside your stable version.

  • The latest preview version of the Android SDK Build Tools (31.0.0 rc5) is not compatible with Android Studio versions prior to Android Studio Arctic Fox.

Android Enterprise
  • A device can have a device-wide password and a work profile security challenge. When you tap a work app’s notification on the lock screen, you are first prompted to unlock the device, and then prompted to unlock the work profile. If the work challenge does not prompt you to unlock, swipe away the task from the recent apps or Overview screen, and then open the work app again.
Android Auto
  • When playing music on Youtube Music on Android Auto, some users may experience audio playing out of the phone instead of the vehicle speakers or no audio at all in Toyota Cars.
  • When using Google Maps navigation on Android Auto, some users may experience issues with text being blurry.
  • Users may face issues while selecting a destination in Waze.
  • Phone may become unresponsive or stuck on the lock screen after starting Android Auto.
  • In some scenarios, Google Maps might not be able to provide different route options while using Android Auto.
  • Music may get paused when the phone is locked.
  • Users might hear Music audio while trying to reply to an SMS using the Google Assistant.
  • Automatic Day and Night switching may not work.
Android TV
  • Hotplugging the HDMI cable might cause video playback to fail on some display sinks.
  • Some pages in the TV Settings app contain empty placeholders in this release.

Android 12 Beta 1

Beta 1

Release date: May 18, 2021
Build: SPB1.210331.013
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: May 2021
Google Play services: 21.12.13
API diff:

What's new in Beta 1

Android 12 Beta 1 includes several new features and changes to try out:

Top resolved issues

The following issues have been resolved in Android 12 Beta 1:

Developer-reported issues
  • Fixed an issue that caused extra space to remain in the app drawer interface after a user disabled app suggestions. (Issue #186096754)
  • Fixed an issue that prevented Pixel phones from detecting when they were placed on a Pixel Stand. (Issue #186184469)
  • Fixed an issue that caused the Google app to crash when opening Discover or tapping an article in the Discover feed. (Issue #187540137)
  • Fixed an issue that prevented some devices from being able to boot after applying an OTA image. (Issue #180636356)
  • Fixed an issue that caused the system to prompt a user to turn off their mobile carrier connection when they were navigating advanced mobile network settings. (Issue #181585057)
  • Fixed an issue that prevented a device's display cutout from being hidden using the developer options. (Issue #183342310)
  • Fixed issues with RenderEngine that caused jankiness and, in some cases, caused a device to crash and restart. (Issue #183873177, Issue #184544726)
  • Fixed an issue that caused some devices to crash and fail to boot after the device was manually restarted. (Issue #184760958)
  • Fixed an issue that could cause CompatibilityChangeReporter log messages to be erroneously printed when calling SensorManager.registerListener(). (Issue #184660151)
Other resolved issues
  • Fixed an issue where, when Android Auto was set up for the first time on a vehicle and a user invoked Google Assistant, some users experienced a crash with Assistant.
  • Fixed an issue where, when playing Google Podcast on Android Auto, some users experienced a crash with Google Podcast.
  • Fixed an issue where, when connecting to a wireless compatible head unit, users sometimes had wireless connectivity issues if they were using Android Auto version 6.2 or lower.

Top open issues

See top open issues for the latest list of top open issues that have been reported by developers and users.

Other known issues

Based on our testing, you might encounter the following issues when using Android 12 Beta 1. These issues are already known, so there’s no need to file additional reports for similar issues.

Android platform
  • When using the SplashScreen API, app icons are sometimes cut off.
  • When using the SplashScreen API, after setting an Animated Vector Drawable and a setOnExitAnimationListener(), the vector drawable's animation stops when the callback is called.
  • The Block calls from unidentified callers dialer setting is disabled in Android Beta 1 and Beta 2. This setting is enabled again starting with Beta 2.1.
Apps
  • In some scenarios, users of apps that have been granted the Display over other apps permission and render full screen overlays might find touches blocked on Android 12 until the developer updates the app. Affected users can temporarily turn off the permission in Settings, which can always be accessed using the settings icon in the notification shade. If an app you use is affected by this issue, you can contact the app developer directly to let them know.
Android Studio and tools
  • When installing an app that has a targetSdkVersion of "S" from Android Studio, developers might see the following error:

    Installation did not succeed.
    The application could not be installed: INSTALL_FAILED_VERIFICATION_FAILURE
    List of apks:
    [0] '.../build/outputs/apk/debug/app-debug.apk'
    Installation failed due to: 'null'
    

    The likely cause is that one or more of the app's activities, services, or broadcast receivers includes intent-filters, but does not explicitly set a value for android:exported. Android 12 requires setting an explicit value for this attribute on all <activity>, <service>, and <receiver> components that also have an <intent-filter> defined. For more information, see Safer exporting of components. Note: This issue is already solved in the latest canary release of Android Studio Arctic Fox. To get the latest fixes and enhancements when targeting Android 12, we recommend installing a preview version of Android Studio alongside your stable version.

Android Enterprise
  • A device can have a device-wide password and a work profile security challenge. When you tap a work app’s notification on the lock screen, you are first prompted to unlock the device, and then prompted to unlock the work profile. If the work challenge does not prompt you to unlock, swipe away the task from the recent apps or Overview screen, and then open the work app again.
Android Auto
  • When playing music on Youtube Music on Android Auto, some users may experience audio playing out of the phone instead of the vehicle speakers or no audio at all.
  • When using Google Maps navigation on Android Auto, some users may experience issues with text being blurry.
  • Users may face issues while selecting a destination in Waze.
Android TV
  • Setup using the Google Home App is not supported on this build.
  • Hotplugging the HDMI cable might cause video playback to fail on some display sinks.
  • Some pages in the TV Settings app contain empty placeholders in this release.