Third-party contextual advertising may also be permitted in limited cases provided that the services have publicly documented practices and policies for Kids Category apps that include human review of ad creatives for age appropriateness. People need to know how to reach you with questions and support issues.

Make sure your app and its Support URL include an easy way to contact you; this is particularly important for apps that may be used in the classroom. Failure to include accurate and up-to-date contact information not only frustrates customers, but may violate the law in some countries. Also ensure that Wallet passes include valid contact information from the issuer and are signed with a dedicated certificate assigned to the brand or trademark owner of the pass. Apps should implement appropriate security measures to ensure proper handling of user information collected pursuant to the Apple Developer Program License Agreement and these Guidelines see Guideline 5.

Apps for reporting alleged criminal activity must involve local law enforcement, and can only be offered in countries where such involvement is active.

Submissions to App Review, including apps you make available for pre-order, should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission. Make sure your app has been tested on-device for bugs and stability before you submit it, and include demo account info and turn on your back-end service! If you offer in-app purchases in your app, make sure they are complete, up-to-date, and visible to the reviewer, or that you explain why not in your review notes.

We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems. Any app submitted for beta distribution via TestFlight should be intended for public distribution and should comply with the App Review Guidelines.

Note, however, that apps using TestFlight cannot be distributed to testers in exchange for compensation of any kind, including as a reward for crowd-sourced funding. Significant updates to your beta build should be submitted to TestFlight App Review before being distributed to your testers.

To learn more, visit the TestFlight Beta Testing page. There are many ways to monetize your app on the App Store. If we find that you have attempted to manipulate reviews, inflate your chart rankings with paid, incentivized, filtered, or fake feedback, or engage with third-party services to do so on your behalf, we will take steps to preserve the integrity of the App Store, which may include expelling you from the Apple Developer Program.

Coming up with a great design is up to you, but the following are minimum standards for approval to the App Store. And remember that even after your app has been approved, you should update your app to ensure it remains functional and engaging to new and existing customers. Apps that stop working or offer a degraded experience may be removed from the App Store at any time. Come up with your own ideas. We know you have them, so make yours come to life. Your app should include features, content, and UI that elevate it beyond a repackaged website.

Apps that are simply a song or movie should be submitted to the iTunes Store. Apps that are simply a book or game guide should be submitted to the Apple Books Store. If your app has different versions for specific locations, sports teams, universities, etc. Also avoid piling on to a category that is already saturated; the App Store has enough fart, burp, flashlight, fortune telling, dating, drinking games, and Kama Sutra apps, etc. We will reject these apps unless they provide a unique, high-quality experience.

Spamming the store may lead to your removal from the Apple Developer Program. Apps hosting or containing extensions must comply with the App Extension Programming Guide or the Safari App Extensions Guide and should include some functionality, such as help screens and settings interfaces where possible. Stickers are a great way to make Messages more dynamic and fun, letting people express themselves in clever, funny, meaningful ways.

Apps may display customized icons, for example, to reflect a sports team preference, provided that each change is initiated by the user and the app includes settings to revert to the original icon.

All icon variants must relate to the content of the app and changes should be consistent across all system assets, so that the icons displayed in Settings, Notifications, etc. This feature may not be used for dynamic, automatic, or serial changes, such as to reflect up-to-date weather information, calendar notifications, etc.

Apps may contain or run code that is not embedded in the binary e. HTML5-based games, bots, etc. These additional rules are important to preserve the experience that App Store customers expect, and to help ensure user safety. Your app is an education, enterprise, or business app that requires the user to sign in with an existing education or enterprise account. Your app uses a government or industry-backed citizen identification system or electronic ID to authenticate users.

Your app is a client for a specific third-party service and users are required to sign in to their mail, social media, or other third-party account directly to access their content.

Streaming games are permitted so long as they adhere to all guidelines—for example, each game update must be submitted for review, developers must provide appropriate metadata for search, games must use in-app purchase to unlock features or functionality, etc. Of course, there is always the open Internet and web browser apps to reach all users outside of the App Store.

To record native allocations on devices running Android 10 and higher, select Record native allocations , then select Record. The recording continues until you click Stop , after which the Memory Profiler UI transitions into a separate screen displaying the native recording.

If the device is running Android 8 or higher, the Memory Profiler UI transitions to a separate screen displaying the ongoing recording. You can interact with the mini timeline above the recording for example, to change the selection range. To complete the recording, select Stop. On Android 7. We have moved files unrelated to configuration from the. Projects generated by CMake are expensive to generate and are expected to survive across gradle clean. For this reason, they're stored in a folder called.

Typically, Android Gradle plugin will notice configuration changes and automatically regenerate the Ninja project. However, not all cases can be detected. Instrumentation tests can now run across multiple devices in parallel and can be investigated using a specialized instrumentation test results panel. Using this panel, you can determine if tests are failing due to API level or hardware properties. Testing your app across a wide variety of API levels and form factors is one of the best ways to ensure that all users have a great experience when using your app.

The new test results panel allows you to filter your test results by status, device, and API level. Additionally, you can sort each column by clicking the header. By clicking on an individual test, you can view logs and device information individually for each device. For Kotlin apps that use coroutines, you can now use StateFlow objects as a data binding source to automatically notify the UI about changes in the data.

Your data bindings will be lifecycle aware and will only be triggered when the UI is visible on the screen.

To use a StateFlow object with your binding class, you need to specify a lifecycle owner to define the scope of the StateFlow object, and in your layout, assign the properties and methods of your ViewModel component to the corresponding views using binding expressions, as shown in the following example:. If you're in a Kotlin app that uses AndroidX, StateFlow support is automatically included in the functionality of data binding, including the coroutines dependencies.

To learn more, see Work with observable data objects. Suggested import helps you quickly and easily import certain Google Maven artifacts into both your class and Gradle project. When Android Studio detects unresolved symbols from certain Google libraries, the IDE suggests importing the library into both the class and the project. Build Analyzer now identifies when a project doesn't have configuration cache enabled, and offers it as an optimization.

Build Analyzer runs a compatibility assessment to inform you if there are any issues with configuration cache in your project before it gets enabled. The Upgrade Assistant for Android Gradle plugin now has a persistent tool window with the list of steps that will be completed.

Additional information is also presented on the right side of the tool window. If needed, you can also choose a different version of AGP to upgrade to. Clicking on the Refresh button updates the corresponding update steps. You can use non-transitive R classes with the Android Gradle plugin to build faster builds for applications with multiple modules. This leads to more up-to-date builds and the corresponding benefits of compilation avoidance. We now offer additional support for previewing and testing apps that use Jetpack Compose.

For the best experience developing with Jetpack Compose, you should use the latest version of Android Studio Arctic Fox so that you can benefit from smart editor features , such as New Project templates and the ability to immediately preview your Compose UI.

The following parameters for Preview methods are now available:. You can use this feature to interact with your UI components, click them, and see how the state changes. It's a quick way to get feedback on how your UI reacts and to preview the animations.

To enable it, click the Interactive icon , and the preview will switch modes. You can use this feature to deploy a snippet of your UI to a device. This helps test small parts of your code in the device without having to start the full application.

Click the Deploy to Device icon next to the Preview annotation or at the top of the preview, and Android Studio will deploy that Preview to your connected device or emulator. We have added Live Edit of literals to help developers using Compose quickly edit literals strings, numbers, booleans in their code and see the results immediately without needing to wait for compilation.

The goal of this feature is to help increase your productivity by having code changes appear near instantaneously in the previews, emulator, or physical device. The Layout Inspector allows you to see rich detail about your app's layout running on your connected device.

You can interact with your app and see live updates in the tool to quickly debug issues that might arise. Whether your app uses layouts fully written in Compose or layouts that use a hybrid of Compose and Views, the Layout Inspector helps you understand how your layouts are rendered on your running device.

If the Layout Inspector doesn't automatically connect to your app process, select the desired app process from the process pulldown. You should soon see your app's layout rendered in the tool window. To get started inspecting your Compose layout, select the layout component visible in the rendering or select it from the Component Tree.

The Attributes window shows you detailed information about the Compose function currently selected. In this window, you can inspect the function's parameters and their values, including modifiers and lambda expressions. For lambda expressions, the inspector provides a shortcut to help you navigate to the expression in your source code.

The Layout Inspector shows all Compose functions in the call stack that emit components to your app's layout. In many cases, this includes Compose functions that are called internally by the Compose Library. If you want to see only the Compose functions in the Component Tree that your app calls directly, click the filter action, which might help reduce the number of nodes shown in the tree to the ones you are likely to want to inspect.

The device dropdown now distinguishes between different kinds of errors within your chosen device configuration. Iconography and stylistic changes now differentiate between errors device selections that result in a broken configuration and warnings device selections that may result in unexpected behavior but are still runnable.

In addition, Android Studio will now warn you if you attempt to launch your project to a device that has an error or a warning associated with it. The new Wear OS pairing assistant guides developers step-by-step through pairing Wear OS emulators with physical or virtual phones directly in Android Studio.

The assistant can help you get the right Wear OS Companion app installed on your phone and set up a connection between the two devices.

Android Studio Arctic Fox now includes a new layout template that adapts to various display dimensions and app resizing, such as phones, foldables, tablets, and split screen modes. When creating a new project or module, select the Responsive Activity template to create a layout with components that dynamically resize. We have integrated Android Accessibility Test Framework in Android Studio to help you find accessibility issues in your layouts.

The tool reports accessibility related issues and offers suggested fixes for some common problems i. To launch the panel, click on the error report button in the Layout Editor. Android Studio and Android Emulator now contain initial support for core developer workflows when running the Apple silicon arm64 hardware architecture, including corresponding emulator system images. You may have to run Rosetta 2 on your machine to run some tools. This minor update includes various bug fixes.

To see a list of notable bug fixes, read the related post on the Release Updates blog. This minor update bundles Kotlin plugin 1. In previous releases, JDK 8 was bundled with Studio.

When using the new bundled JDK to run Gradle, this may result in some incompatibility or impact JVM performance due to changes to the garbage collector. These issues are described in the AGP release notes. To improve Gradle Sync performance, Android Studio skips building the task list during sync.

This allows Gradle Sync to complete faster and improves UI responsiveness for very large projects. This option is on by default in Android Studio 4.

The Database Inspector includes some improvements to help you write and execute your custom SQL statements. When you open the inspector and open a New query tab, you should notice a larger, resizable editor surface to author and format your queries, as shown below.

Additionally, we now provide a history of your previous queries. When you click on the Show query history button, you should see a list of queries you previously ran against the currently selected database. Click a query in the list to see a preview of the full query in the editor and press Enter to copy it to the editor. Then, click Run to execute the statement. In previous versions of Android Studio, disconnecting from an app process while using the Database Inspector resulted in closing the inspector and its data.

In Android Studio 4. When a disconnect occurs, the Database Inspector downloads your databases and then makes them available to you in offline mode. When offline, you can open tables and run queries. Keep in mind, when you reconnect to a live app process, the Database Inspector returns to live mode and shows you only the data that is on the device. That is, data shown in offline mode doesn't persist when you reconnect to an app process. Because of this, the Database Inspector does not allow editing or running modification statements while in offline mode.

In the CPU profiler, the System Trace feature now includes new metrics for analyzing app performance and includes the following:. In the Display section, this new track shows the buffer count of the app's surface BufferQueue 0, 1, or 2 to help you understand the state of image buffers as they move between the Android graphics components.

CPU Frequency. Process Memory RSS. This new window shows the amount of physical memory currently in use by the app. Introduced in Android Studio 4. Pause live updates and refresh the screen capture in the Layout Inspector. To manually load a snapshot of UI data from your app, first disable the Live updates option.

You can then click the Refresh button to take a new snapshot of the UI stack for inspection. The Layout Inspector now remembers your preference to keep Live updates enabled or disabled between sessions.

Safe Args is a Gradle plugin that generates simple object and builder classes for type-safe navigation and access to any associated arguments. Android Studio now includes richer support when working with Safe Args, as described below:. Available in version 4. Alternatively, you can download the standalone command-line tools package. For usage information, see R8 retrace in the user guide. To help streamline app testing across devices and API levels, you can now deploy your app to multiple devices or emulators simultaneously by following these steps:.

Android Gradle plugin 4. This new setting optimizes fusing of install-time modules with the base module, potentially improving app performance for some apps. For more information on this new setting, see the documentation for the dist:removable tag in the documentation for feature module manifest. To help you be more productive as you iterate on your app, we've made the following enhancements to Apply Changes for devices running Android 11 or higher:.

For devices running Android 11 or higher, you can now add static final primitive fields and then deploy those changes to your running app by clicking either Apply Code Changes or Apply Changes and Restart Activity. You can now also add resources and then deploy those changes to your running app on Android 11 devices by clicking Apply Changes and Restart Activity.

The New Project and New Module wizards have been updated to make it easier to browse, select a template, and input information about the new project or module. The option to Import. Android Studio 4.

Check out the Kotlin 1. For more information, see Emulator Environment Variables. This section describes known issues that exist in Android Studio 4. For a complete list, go to the Known issues page. If you are using Android Studio 4. As a workaround, replace "1. Starting with version 4. This update causes an underlying behavior change related to signing keys. Studio tries to import previous. To work around this issue, we recommend commenting out custom options in.

If Studio still doesn't start after trying this workaround, see Studio doesn't start after upgrade below. Inspect, query, and modify your databases in your running app using the new Database Inspector.

To learn more, see Debug your database with the Database Inspector. You can now run the Android Emulator directly in Android Studio. Use this feature to conserve screen real estate, to navigate quickly between the emulator and the editor window using hotkeys, and to organize your IDE and emulator workflow in a single application window. To learn more, see the Android Emulator documentation. ML Model Binding makes it easy for you to directly import. Android Studio generates easy-to-use classes so you can run your model with less code and better type safety.

The current implementation of ML Model Binding supports image classification and style transfer models, provided they are enhanced with metadata. Over time, support will be expanded to other problem domains, like object detection, image segmentation, and text classification. A wide range of pre-trained models with metadata are provided on TensorFlow Hub. To see the details for an imported model and get instructions on how to use it in your app, double-click the model file in your project to open the model viewer page, which shows the following:.

As the example demonstrates, Android Studio creates a class called MobilenetVQuantized for interacting with the model. If the model does not have metadata , this screen will only provide minimal information. This feature is still under development, so please provide feedback or report bugs. With the Native Memory Profiler, you can record memory allocations and deallocations from native code and inspect cumulative statistics about native objects.

Support for profiling Android 11 devices is currently available in the 4. As of the initial 4. This option will be enabled in an upcoming release. As a workaround, you can use the Perfetto standalone command-line profiler to capture startup profiles. Box selection: In the Threads section, you can now drag your mouse to perform a box selection of a rectangular area, which you can zoom into by clicking the Zoom to Selection button on the top right or use the M keyboard shortcut.

When you drag and drop similar threads next to each other, you can select across multiple threads to inspect all of them at once. For example, you may want to perform analysis on multiple worker threads.

Summary tab: The new Summary tab in the Analysis panel displays:. With the new standalone profilers, it's now possible to profile your app without running the full Android Studio IDE. For instructions on using the standalone profilers, see Run standalone profilers. Android Studio makes it easier to navigate between your Dagger-related code by providing new gutter actions and extending support in the Find Usages window.

New gutter actions: For projects that use Dagger, the IDE provides gutter actions that help you navigate between your Dagger-annotated code. For example, clicking on the gutter action next to a method that consumes a given type navigates you to the provider of that type. Conversely, clicking on the gutter action navigates you to where a type is used as a dependency. Find Usages node: When you invoke Find Usages on a provider of a given type, the Find window now includes a Dependency consumer s node that lists consumers of that type.

Conversely, invoking this action on a consumer of a Dagger-injected dependency, the Find window shows you the provider of that dependency. Updates include:.

Check out the 1. When creating a custom view for example, by extending the View or Button class , Android Studio now shows you a preview of your custom view. Use the dropdown menu in the toolbar to switch between multiple custom views, or click the buttons to wrap vertically or horizontally to the content. When a crash or ANR occurs in native code, the system produces a stack trace, which is a snapshot of the sequence of nested functions called in your program up to the moment it crashed.

These snapshots can help you to identify and fix any problems in the source, but they must first be symbolicated to translate the machine addresses back into human-readable function names. The Play Console uses these debug symbols files to symbolicate your app's stack traces, making it easier to analyze crashes and ANRs.

To learn how to upload debug symbols files, see Native crash support. To help you be more productive as you iterate on your app, we've made the following enhancements to Apply Changes for devices running Android 11 Developer Preview 3 or higher:. We've invested heavily in optimizing your iteration speed by developing a method to deploy and persist changes on a device without installing the application.

After an initial deploy, subsequent deploys to Android 11 devices using either Apply Code Changes or Apply Changes and Restart Activity are now significantly faster.

To learn more about the difference between these two actions, see Apply Changes. For devices running Android 11 Developer Preview 3 or higher, you can now add methods and then deploy those changes to your running app by clicking either Apply Code Changes or Apply Changes and Restart Activity. This minor update includes various bug fixes, as well as support for new default settings for Package visibility in Android For more information, see the release notes for Android Gradle plugin 4.

To see a list of notable bug fixes for this release, read the related post on the Release Updates blog. Important: After updating, you need to restart Android Studio to apply any memory settings migrated from an earlier version of the IDE. For more information, see the Known Issues page. The latest version of the Android Gradle plugin includes many updates, such as Java 8 desugaring for older versions of Android and feature-on-feature dependencies.

Additionally, Android Studio now includes new features to help you improve your build performance. When using Android Studio 4. To open the Build Analyzer window, proceed as follows:. The Build Analyzer window organizes possible build issues in a tree on the left.

You can inspect and click on each issue to investigate its details in the panel on the right. You can also get details on warnings by expanding the Warnings node. This means that you can now include standard language APIs that were available only in recent Android releases such as java. Note that you may also need to include the above code snippet in a library module 's build. The library module's instrumented tests use these language APIs either directly or through the library module or its dependencies.

You want to run lint on the library module in isolation. This is to help lint recognize valid usages of the language APIs and avoid reporting false warnings. In previous versions of the Android Gradle plugin, all feature modules could depend only on the app's base module. When using Android Gradle plugin 4.

That is, a :video feature can depend on the :camera feature, which depends on the base module, as shown in the figure below. Feature module :video depends on feature :camera , which depends on the base :app module. This means that when your app requests to download a feature module, the app also downloads other feature modules it depends on.

For example, the :video module declares a dependency on :camera as follows:. When building your app using Android Gradle plugin 4.

When uploading your app, the Play Console inspects this metadata to provide you with the following benefits:. The data is compressed, encrypted by a Google Play signing key, and stored in the signing block of your release app. When used with Android Studio, certain IDE features, such as the Project Structure dialog and build script quick fixes, now also support reading and writing to Kotlin build script files.

Based on your feedback, we've focused our efforts on improving the user experience in the CPU Profiler in two important ways. Some notable UI changes include the following:.

This version of Android Studio includes updates to the design tools, such as the Layout Inspector and an all-new Motion Editor. Android Studio now includes a visual design editor for the MotionLayout layout type, making it easier to create and preview animations. The Motion Editor provides a simple interface for manipulating elements from the MotionLayout library that serves as the foundation for animation in Android apps. In previous releases, creating and altering these elements required manually editing constraints in XML resource files.

Now, the Motion Editor can generate this XML for you, with support for start and end states, keyframes, transitions, and timelines. To learn more about how to use the Motion Editor, see the user guide. Along with many of the same features of the existing Layout Inspector, the Live Layout Inspector also includes:. You can use the Live Layout Inspector only when deploying your app to a device or emulator running API level 29 or higher.

Then click the checkbox next to Live updates above the Layout Display. Layout Validation is a visual tool for simultaneously previewing layouts on different devices and configurations, helping you detect layout errors and create more accessible apps. You can access this feature by clicking on the Layout Validation tab in the top-right corner of the IDE window:. In the Layout Validation window, you can select from four different configuration sets, including:.

Android Studio now provides smart editor features when you open code shrinker rules files for R8, such as syntax highlighting, code completion, and error checking. The editor also integrates with your Android Studio project to provide full symbol completion for all classes, methods, and fields, and includes quick navigation and refactoring.

Android Studio now includes Android live templates for your Kotlin classes. For example, you can now type toast and press the Tab key to quickly insert a Toast. To learn more about developing for Android 11, see the Android 11 documentation. The value for ndk. To learn more about the improvements from other IntelliJ versions that are included cumulatively with version We'd also like to thank all of our community contributors who have helped with this release.

This version of Android Studio includes updates to several design tools, including the Layout Editor and Resource Manager. Design editors, such as the Layout Editor and Navigation Editor, now provide a Split view that enables you to see both the Design and Code views of your UI at the same time. In the top-right corner of the editor window, there are now three buttons for toggling between viewing options:.

The controls for zooming and panning within design editors have moved to a floating panel in the bottom-right corner of the editor window.

To help you quickly update color resource values in your app when you're using the color picker in your XML or the design tools, the IDE now populates color resource values for you. The latest version of the Android Gradle plugin includes many updates, including optimizations for build speed, support for the Maven publishing plugin, and support for View Binding.

To learn more, read the full release notes. View binding allows you to more easily write code that interacts with views by generating a binding class for each XML layout file.

These classes contain direct references to all views that have an ID in the corresponding layout. Because it replaces findViewById , view binding eliminates the risk of null pointer exceptions resulting from an invalid view ID. To enable view binding, you need to use Android Gradle plugin 3. You can now add a class and then deploy that code change to your running app by clicking either Apply Code Changes or Apply Changes and Restart Activity.

You can now instant-enable your base module at any time after creating your app project as follows:. To learn more, read Overview of Google Play Instant. Automatically create a stub implementation function for a JNI declaration. Unused native implementation functions are highlighted as a warning in the source code. Document Sharing profiles manage two aspects of the documents being shared, the metadata about the document and the contents of the document. Metadata encodes the properties of Documents, the environments they come from, circumstances of their submission, terms to reference in queries, and grouping with other Documents.

There is no concept of equivalent Documents. If the byte sequence is different, then the Documents are different. Those standards have concepts like "insignificant whitespace".