Menu
Google is committed to advancing racial equity for Black communities. See how.
Android SDK Build-Tools is a component of the Android SDK required forbuilding Android apps. It's installed in the
<sdk>/build-tools/
directory.If you are looking to download iOS IPSW for your iPhone, iPad or iPod touch then you have come to the right place. On this page you can find all versions of iOS ever released by Apple starting from iPhone OS 1 all the way up to the latest version of iOS 12. Install the VS Code extensions. To use the DevTools from VS Code, you need the Dart extension.If you’re debugging Flutter applications, you should also install the Flutter extension. Start an application to debug.
You should always keep your Build Tools component updated by downloading the latest version using the Android SDK Manager. If you're using Android plugin for Gradle 3.0.0 or higher, your project automatically uses a default version of the build tools that the plugin specifies. To use a different version of the build tools, specify it using
buildToolsVersion
in your module's build.gradle
, as follows:- View All Software Products Discover our productivity and customization tools. Volume Licensing Increase productivity, design intelligent controls and reinforce branding with our enterprise products. Games Star Control The space action/adventure classic returns. Sins of a Solar Empire Real-time strategy. Unrivaled scale.
- Internally created and released for different platforms, NeuroSky's Development Tools are the set of software tools and APIs for all NeuroSky EEG headsets that make it easy for developers to create innovative applications that interact with a user's mental state. To download the Development Tools, choose the target pla.
Revisions
The sections below provide notes about releases of the Build Tools. To determine whichrevisions of the Build Tools are available in your SDK, refer to the Installed Packageslisting in the Android SDK Manager.
Build Tools, Revision 30.0.0 rc4 (May 2020)
This update includes support for building with Android 11 Preview APIs.
Build Tools, Revision 29.0.3 (January 2020)
This update fixes the following issue:
- Build issue with Renderscript on macOS Catalina. (See issue #142590626)
Build Tools, Revision 29.0.2 (August 2019)
This update fixes the following issue:
Build Tools, Revision 29.0.0 (June 2019)
This update includes support for building with API level 29.
Build Tools, Revision 28.0.3 (September 2018)
This update includes support for Android Gradle plugin 3.2.0 and fixes the following issues:
- Fixed a JNI library bug that caused apps to crash when calling
androidx.renderscript.RenderScript.create()
. - Fixed a bug that caused
Program type already present
build errors withandroidx.annotation
resources.
Build Tools, Revision 28.0.2 (August 2018)
Includes the latest version of D8.
Build Tools, Revision 27.0.3 (December 2017)
Improves support for compiling lambdas when you enable Java 8 language features.
Build Tools, Revision 27.0.2 (December 2017)
Improves support for Java 8 language features.
Build Tools, Revision 27.0.1 (November 2017)
Adds support for legacy multidex for test APKs. (Issue #37324038)
Build Tools, Revision 26.0.2 (October 2017)
In addition to general bug fixes, this release includes the following updates:
- Updates
apksigner
to version 0.8:- Compatibility with Java 9. (Issue #37137869)
- New
--pass-encoding
parameter to handle keystores and keys that are encrypted using non-ASCII passwords. If you switch to Java 9 andapksigner
fails to decrypt your keystore or key, use this parameter to specify the character encoding you used to create the keystore or key. For more information, see theapksigner
documentation or runapksigner sign --help
from the commandline. - Better error message when
apksigner
can't verify a JAR signature due to an unsupported digest or signature algorithm. (Issue #63525618)
- Support for AAPT2 daemon mode when using Android plugin for Gradle
3.0.0-beta7
or higher.
Build Tools, Revision 26.0.1 (July 2017)
In addition to general bug fixes, this release restores
apksigner
to the build tools package (it was omitted by mistake in version 26.0.0) and includes the following updates to the tool:- Adds PKCS #11 support to allow signing with keys held in secure hardware. (Issue #37140484)
- Adds support for loading additional JCA Providers before signing.
- Honors
android:targetSandboxVersion
when verifying APKs. - When signing, rejects APKs with files that include 'CR' (carriage return), 'LF' (line feed), or 'NUL' (null) special characters in the file name.
- Fixes
apksigner.bat
to correctly handle parameters containing spaces. (Issue #38132450) - Fixes a bug in JAR signature verification when multiple digests are present for the same entry in
MANIFEST.MF
. (Issue #38497270)
Build Tools, Revision 26.0.0 (June 2017)
Adds support for building with API level 26 and contains general bug fixes. Numi 3 18 3 download free.
Build Tools, Revision 25.0.3 (April 2017)
Updates to
apksigner
:- Added
--in
parameter for symmetry with existing--out
parameter. - If you do not specify the key password using
--key-pass
,apksigner
uses the keystore password as key password. However, if the key requires a different password, you are now prompted to enter the key password from the command line. (Issue #37134986) - Added compatibility with
jarsigner
for non-ASCII passwords. (Issue #37135737)
Build Tools, Revision 25.0.2 (December 2016)
Bug fixes.
Build Tools, Revision 25.0.1 (November 2016)
This release includes bug fixes and the following improvements to
apksigner
:- Support for APKs with obfuscated JAR entry names.
--print-certs
switch now also dumps MD5 fingerprints.
Build Tools, Revision 25.0.0 (October 2016)
Bug fixes for the Jack toolchain:
- Fixed issue with Jack supporting non-ASCII source files. (Issue #218892)
- Fixed issue that causes an
AssertionError
during some compilations. (Issue #208414)
Build Tools, Revision 24.0.3 (September 2016)
- Added
apksigner
, an APK signing tool to replacejarsigner
. By default,apksigner
signs APKs using the conventional JAR signing scheme (used byjarsigner
) and the APK Signature Scheme v2 introduced in Android 7.0 (API level 24). Any modification to an APK signed with APK Signature Scheme v2 invalidates its signature. Thus, APK post-processing, such aszipalign
, must be performed beforeapksigner
is invoked, not after. Invokingzipalign
beforeapksigner
works fine becauseapksigner
preserves APK alignment and compression (unlikejarsigner
).
Build Tools, Revision 23.0.3 (March 2016)
- Fix issues in the RenderScript Support Library on arm64 devices.
- Fix issues in the RenderScript Support Library on certain Jelly Bean devices.
- Support
renderscriptTargetAPI 21+
when using Android Plugin for Gradle, Revision 2.1.0 and above .
Build Tools, Revision 23.0.2 (November 2015)
- Improved the merging performance of the
dx
tool. - Fixed issues in the RenderScript compiler for Windows.
Build Tools, Revision 23.0.1 (October 2015)
Fixed issues in the RenderScript tools.
Build Tools, Revision 23.0.0 (August 2015)
Added support for the Android 6.0 (API level 23) release.
Build Tools, Revision 22.0.1 (March 2015)
Fixed compatibility issues with RenderScript kernels on Android 4.4 (API level 19) to Android 4.1 (API level 16) devices.
Build Tools, Revision 22.0.0 (March 2015)
Added support for Android 5.1 (API level 22). Ex libris 9 0 1 – a library database pdf.
Build Tools, Revision 21.1.2 (February 2015)
Fixed problem with building data layouts in 32-bit mode.
Build Tools, Revision 21.1.1 (November 2014)
Fixed multidex script issues.
Build Tools, Revision 21.1 (October 2014)
Added multidex file support for APKs and Jack support to address the 64K method reference limit.
Build Tools, Revision 21.0.2 (October 2014)
Complete updates for Eclipse ADT to solve instability issues on Windows platforms.
Build Tools, Revision 21.0.1 (October 2014)
Initial updates for Eclipse ADT on Windows. Please use Revision 21.0.2.
Build Tools, Revision 21.0.0 (October 2014)
- Added support for Android 5.0 (API level 21).
- RenderScript now supports seamless 32/64-bit operation for API level 21 and higher.
- Fixed issue with the Gradle build system when using the JaCoCo plugin. (Issue 69174)
- Added an input-list option for use with long command lines on Windows.
Build Tools, Revision 20.0.0 (June 2014)
- Added support for Android Wear.
Build Tools, Revision 19.1.0 (May 2014)
- Added
zipalign
to the Build Tools. - Modified
aapt
to ignore XML files that fail to compile.
Build Tools, Revision 19.0.3 (March 2014)
Fixed an issue with RenderScript support.
Build Tools, Revision 19.0.2 (February 2014)
- Fixed a problem with RenderScript bitcode encoding. (Issue 64775)
- Fixed a problem with RenderScript missing math symbols (Issue 64110)
Build Tools, Revision 19.0.1 (December 2013)
- Fixed support for compiling RenderScript in NDK mode with Gradle.
- Fixed
BufferOverflowException
problem in the dx build. (Issue 61710)
Build Tools, Revision 19 (October 2013)
Added support for Android 4.4 (API level 19) build targets.
Build Tools, Revision 18.1.1 (September 2013)
Fixed several minor build issues.
Build Tools, Revision 18.1.0 (September 2013)
Fixed issue with RenderScript support mode.
Build Tools, Revision 18.0.1 (July 2013)
Added support for Android 4.3 (API level 18) build targets.
Build Tools, Revision 17 (May 2013) Djay pro 2 mac download.
Initial release.
- Included support for Android 4.2 (API level 17) build targets.
- Decoupled the build-specific components of the Android SDK from the platform-tools component, so that the build tools can be updated independently of the integrated development environment (IDE) components.
- Contents
Objective
In this section, you will about the testing and debugging tools provided as part of the Xcode environment.
Contents
The iOS SDK provides various tools that are useful for debugging native apps. May of them can also be used for your Titanium application development. In this section, we'll take a look at how to view log output within Xcode, view device logs, and view crash logs. We'll introduce, but not dig too deep into the Instruments tool. We'll cover it in more depth in another section.
View log output in Console
You can use the Console application to view log output from an iOS simulator. You can either open the Console application from the iOS simulator or through the
Applications
folder.To open Console from the iOS simulator, from the menu bar, select Debug > Open System Log ...
To open Console from the
Applications
folder:- Click Applications.
- Select Utilities > Console.app.
- On the left bar, expand iOS Simulator, then expand the version of the simulator you are using.
- Click system.log item to view the simulator's log output.
View log output in Xcode
You can view log output within Xcode. This includes the same information output to the Studio console. Viewing the Xcode (gdb) console is useful if you build your Titanium app from within Xcode to set project-specific parameters, build options, and so forth. (Keep in mind that you lose Titanium's i18n string handling if you build via Xcode.) It would also be useful when debugging a native iOS module for Titanium.
To view log output in Xcode:
- Build your project via Studio, then close the simulator.
- Open
yourproject/build/iphone/yourproject.xcodeproj
(e.g.KitchenSink.xcodeproj
) in Xcode. - Build and run the project within Xcode. Log output is shown in the Console output panel.
View log output on a connected device
A more useful technique is to view the logging messages that are generated by an app running on a connected iOS device. You can do this via the Console view in the Xcode Organizer or using the macOS system Console. The console displays Titanium logging messages, plus iOS system messages that might provide additional useful information.
To view the console output of a connected device:
- Connect your device.
- Build and deploy the app to the device using either the CLI (
appc run -p ios -T device
) or Studio. - Sync the application to the device using the iPhone Configuration Utility (if you are not building directly to device).
- Launch Xcode.
- Open the Devices window. From the menu, select Window > Devices and Simulators.
- Select your device from the left bar.
- Click the Open Device button to show the console.
View crash logs on a device
You can view crash logs generated when an app running on your device crashes. That data is not hugely useful for debugging Titanium apps because it will include native object related logging messages, not Titanium logging output. That crash data will be tied to the Titanium module (object) that was involved with running your code rather than your JavaScript. This sort of logging information would be most useful when debugging a native iOS module for Titanium.
To view the crash log of a connected device:
- Connect your device.
- Launch Xcode.
- Open the Devices window. From the menu, select Window > Devices and Simulator.
- Select your device from the left bar.
- Click the View Device Logs button.
- In the list of available log files, select your app. There might be more than one file for your app, one for each time it has crashed.
Instruments
Instruments is a tool for memory monitoring and profiling. It can be a very useful tool for profiling your app to determine if there are memory leaks and perhaps to discover the causes of poor performance. We'll cover this tool in depth in the Managing Memory and Finding Leaks section.
Simulate cellular network conditions with the Network Link Conditioner
You should test your app under less-than-ideal conditions so that you know how it will react as users go into roaming mode, operate over low-speed data networks, and so forth. If they run your app in such a state, your app should react appropriately rather than crashing. You can simulate slow, noisy, and lossy networks by using the Network Link Conditioner preferences tool included with macOS.
Network Link Conditioner might not be installed by default. To install it:
- Click the Spotlight (magnifying glass) icon and enter Network Link Conditioner.
- When prompted, select Install for all users of this computer and click Install. Enter your password.
- Select the profile that represents the network conditions you'd like to simulate.
- Click the lock and enter your password.
- Turn the link conditioner on.
Once installed, you can access the Network Link Conditioner via the System Preferences application.
Once you turn on link conditioning, your network speed will throttled to the level defined by the profile you selected. At this point, you can test your app in the Simulator under conditions that more realistically reflect the real world.
Because the network throttling applies to your entire system, any macOS tasks you have running that use the network will also be throttled. This might include your email application, web browser, or streaming music player. Incidentally, this means you can use the Network Link Conditioner to test Android apps running in the emulator; it too will see network access throttled as you specified.
If the default network condition profiles don't meet your needs, you can create a custom network profile. You might use a custom profile to specify certain conditions, such as packet loss, upload or download delays, and so forth.
References
![Windows Windows](https://is4-ssl.mzstatic.com/image/thumb/Purple118/v4/3c/03/94/3c039466-1f85-d733-034e-c45ce6b5320a/source/800x500bb.jpg)
- Apple Developer docs: Viewing Console Output and Device Logs
- Simulating slow network connections with
ifpw
for macOS.
Summary
Iconkit 2 0 2 – Ios Developer Tools Download
In this section, you learned that how to view log messages on a connected device, how to view crash logs, and how to view logging messages within Xcode. Of these, viewing log messages from a device is the technique most applicable to debugging Titanium JavaScript issues. The other techniques are better suited to module development.