This page details the Player settings specific to iOS. For a description of the general Player settings, see Player settings.
Note: Unity iOS requires iOS 7.0 or higher. Unity does not support iOS 6.0 or earlier versions.
You can find documentation for the properties in the following sections:
Use the Icon settings to customize the branding for your app on the Apple Store.
Note: If any icon textures are omitted, the icon texture with the nearest size is scaled accordingly (with a preference towards larger resolution textures).
|Application icons||Assign the custom icon that you would like to appear on your app for each iOS device.|
|Spotlight icons||Assign the custom icon that you would like to appear in the Spotlight search results for your game for each iOS device.|
|Settings icons||Assign the custom icon that you would like to appear on the phone’s main Settings page for each iOS device.|
|Notification icons||Assign the custom icon that you would like to appear when sending notifications from your game for each iOS device.|
|Marketing icons||Assign the custom icon that you would like to appear for your game in the App Store for each iOS device.|
Use the Resolution and Presentation section to customize aspects of the screen’s appearance:
The Resolution Scaling Mode allows you to set the scaling to be equal to or below the native screen resolution:
|FixedDPI||Allows you to scale the device’s screen resolution below its native resolution and show the Target DPI property. Use this to optimize performance and battery life or target a specific DPI setting.|
|Disabled||Ensures that scaling is not applied and the game renders to its native screen resolution.|
Set the Target DPI of the game screen. Unity downscales the game screen to match this setting if the device’s native screen DPI is higher than this value. The scale is calculated as
min(Target DPI * Factor / Screen DPI, 1). The Factor is controlled by the Resolution Scaling Fixed DPI Factor on the Quality settings.
Note: This option only appears when the Resolution Scaling Mode is set to Fixed DPI.
Choose the game’s screen orientation from the Default Orientation drop-down menu:
|Portrait||Home button appears at the bottom.|
|Portrait Upside Down||Home button appears at the top.|
|Landscape Left||Home button appears on the right side.|
|Landscape Right||Home button appears on the left side.|
|Auto Rotation||Screen orientation changes with device orientation. This is the default.|
Note: This setting is shared between iOS and Android devices.
When you set the orientation to Auto Rotation, the Allowed Orientations for Auto Rotation section appears.
Enable the Use Animated Autorotation setting if you want orientation changes to animate the screen rotation rather than just switch. This is only visible when Default Orientation is set to Auto Rotation.
This section is only visible when Default Orientation is set to Auto Rotation.
Because Auto Rotation changes screen orientation to match the device, you may want to limit the screen orientations allowed (for example, locking a device to landscape).
Enable each orientation you want to allow by checking its box in this section:
|Portrait||Permite la orientación portrait|
|Portrait Upside Down||Permita la orientación vertical hacia abajo.|
|Landscape Right||Permita la orientación horizontal del paisaje (botón de inicio en el lado izquierdo).|
|Landscape Left||Permite la orientación landscape izquierda (botón de inicio está en el lado derecho).|
Enable the Requires Fullscreen option if your game needs to run in Fullscreen mode.
|Status Bar Hidden||Enable this option to hide the status bar when the application launches.|
|Status Bar Style||Defina el estilo de la barra de estado cuando se inicia la aplicación. Las opciones son Default, Black Translucent y Black Opaque.|
|Disable Depth and Stencil||Enable this option to disable the depth and stencil buffers.|
|Show Loading Indicator||Select how the loading indicator should appear. The options are Don’t Show, White Large, White, and Gray.|
Above the common Splash Screen settings, the Player settings allow you to specify splash images for the iOS platform.
Use the Virtual Reality Splash Image property to select a custom splash image to be displayed in Virtual Reality displays.
Below the common Splash Screen settings, you can enable the Use Storyboard for Launch to show the Custom Storyboard button.
Click the button to select a storyboard to show when your game starts up on the device. For your storyboard to appear here, you first need to create the storyboard in Xcode and copy it to your Project.
A Launch Screen is an XIB file from which iOS creates a splash screen dynamically on the device. However, there are some limitations:
You can’t display different content depending on iPad device orientation.
All iPhones support landscape Launch Screens; however, due to a bug in iOS, Landscape Left is shown instead of Landscape Right on certain iOS versions.
Each the iPhone Launch Screen and iPad Launch Screen sections allow you to select the launch screen type from the Launch Screen type drop-down menu:
|Default||A launch screen that is very much like a launch image. One image is selected for portrait and landscape. The selection order: iPhone 6+ launch images, shared mobile launch image, default Unity launch image for iPhone 6+. The images are displayed using aspect-fill mode.|
|None||El comportamiento es como si sólo se utilizan imágenes de inicio.|
|Image and background (relative size)||Displays a center-aligned image, with the rest of area filled with solid color. The image size is user-specified percentage of the screen size, computed in the smaller dimension (vertical on landscape, horizontal in portrait orientations). User also specifies background color and images for portrait and landscape orientations. Image selection order: the user-specified image, shared mobile launch image, default Unity launch image for iPhone 6+. The images are displayed using aspect-fill mode.|
|Image and background (constant size)||Igual que la opción de tamaño relativo excepto que el tamaño de la imagen se define por el número de puntos especificado por el usuario.|
|Custom XIB||A user-specified XIB file from any location.|
Note: With a Unity Personal subscription the Unity Splash Screen displays as soon as engine initializes, in addition to your chosen splash screen.
Launch Images are static splash screen images that occupy the entire screen. You can define them in an Asset catalog (
Images.xcassets/LaunchImage). Always add a Launch Screen for each supported size and orientation combination:
|Mobile Splash Screen||Specifies texture which should be used for iOS Splash Screen. Standard Splash Screen size is 320x480.(This is shared between Android and iOS.)|
|iPhone 3.5"/Retina||Specifies texture which should be used for iOS 3.5" Retina Splash Screen. Splash Screen size is 640x960.|
|iPhone 4"/Retina||Specifies texture which should be used for iOS 4" Retina Splash Screen. Splash Screen size is 640x1136.|
|iPhone 4.7"/Retina||Specifies texture which should be used for iOS 4.7" Retina Splash Screen. Splash Screen size is 750x1334.|
|iPhone 5.5"/Retina||Specifies texture which should be used for iOS 5.5" Retina Splash Screen. Splash Screen size is 1242x2208.|
|iPhone 5.5" Landscape/Retina||Specifies texture which should be used for iOS 5.5" Landscape/Retina Splash Screen. Splash Screen size is 2208x1242.|
|iPhone X\Retina||Specifies texture which should be used for iPhone X Retina Splash Screen. Splash Screen size is 1125x2436.|
|iPhone X Landscape\Retina||Specifies texture which should be used for iPhone X Landscape/Retina Splash Screen. Splash Screen size is 2436x1125.|
|iPad Portrait||Specifies texture which should be used as iPad Portrait orientation Splash Screen. Standard Splash Screen size is 768x1024.|
|iPad Landscape||Specifies texture which should be used as iPad Landscape orientation Splash Screen. Standard Splash Screen size is 1024x768.|
|iPad Portrait/Retina||Especifica la textura que debe utilizarse como la pantalla de bienvenida de Retina de la orientación del iPad. El tamaño de pantalla estándar de Splash es 1536x2048.|
|iPad Landscape/Retina||Especifica la textura que debe utilizarse como la pantalla de bienvenida del iPad Retina Orientación horizontal. El tamaño de la pantalla de bienvenida estándar es 2048x1536.|
Only iPhone 6+ supports landscape orientation; other iPhones can only use portrait.
Launch Images are selected in the following order:
Necesita configurar todas las Launch Images para su construcción.
|Enable Internal Profiler (Deprecated)||Habilita un perfilador interno que recopila datos de rendimiento de la aplicación e imprime un informe en la consola. El informe contiene el número de milisegundos que se tardó en ejecutar cada subsistema de Unity en cada trama. Los datos se promedian en 30 frames.|
|On .Net UnhandledException||The action taken on .NET unhandled exception. The options are Crash (the application crashes hardly and forces iOS to generate a crash report that can be submitted to iTunes by app users and inspected by developers), Silent Exit (the application exits gracefully).|
|Log Obj-C Uncaught Exceptions||Enables a custom Objective-C Uncaught Exception handler, which prints exception information to console.|
|Enable Crash Report API||Enables a custom crash reporter to capture crashes. Crash logs are available to scripts via CrashReport API.|
This section allows you to customize a range of options organized into the following groups:
Use these settings to customize how Unity renders your game for the iOS platform.
|Color Space||Choose which color space should be used for rendering: Gamma or Linear.
See the Linear rendering overview for an explanation of the difference between the two.
|Auto Graphics API||Disable this option to manually pick and reorder the graphics APIs. By default this option is enabled, and Unity includes Metal, and GLES2 as a fallback for devices where Metal is not supported.|
|Color Gamut||You can add or remove color gamuts for the iOS platform to use for rendering. Click the plus (+) icon to see a list of available gamuts. A color gamut defines a possible range of colors available for a given device (such as a monitor or screen). The sRGB gamut is the default (and required) gamut.
When targeting recent iOS devices with wide color gamut displays, use DisplayP3 to utilize full display capabilities. Use Metal Editor Support as a fallback for older devices.
|Metal Editor Support||Enable this option to use the Metal API in the Unity Editor and unlock faster Shader iteration for targeting the Metal API.|
|Metal API Validation||Enable this option when you need to debug Shader issues.
Note: Validation increases CPU usage, so use it only for debugging.
|Metal Write-Only Backbuffer||Allow improved performance in non-default device orientation. This sets the frameBufferOnly flag on the back buffer, which prevents readback from the back buffer but enables some driver optimization.|
|Force hard shadows on Metal||Enable this option to force Unity to use point sampling for shadows on Metal. This reduces shadow quality, which should give better performance.|
|Memoryless Depth||Choose when to use memoryless render textures. Memoryless render textures are temporarily stored in the on-tile memory when rendered, not in CPU or GPU memory. This reduces memory usage of your app but you cannot read or write to these render textures.
Note: Memoryless render textures are only supported on iOS, tvOS 10.0+ Metal and Vulkan. Render textures are read/write protected and stored in CPU or GPU memory on other platforms.
|Unused||Never use memoryless framebuffer depth.|
|Forced||Always use memoryless framebuffer depth.|
|Automatic||Let Unity decide when to use memoryless framebuffer depth.|
|Multithreaded Rendering||Enable this option to use multithreaded rendering. This is only supported on Metal.|
|Static Batching||Enable this option to use Static batching.|
|Dynamic Batching||Enable this option to use Dynamic Batching on your build (enabled by default).
Note: Dynamic batching has no effect when a Scriptable Render Pipeline is active, so this setting is only visible when nothing is set in the Scriptable Render Pipeline Asset Graphics setting.
|Compute Skinning||Enable this option to use DX11/ES3 GPU compute skinning, which frees up CPU resources. To learn more about GPU compute skinning, see the Wikipedia page on skeletal animation.|
|Graphics Jobs (Experimental)||Enable this option to instruct Unity to offload graphics tasks (render loops) to worker threads running on other CPU cores. This is intended to reduce the time spent in
Note: This feature is experimental. It may not deliver a performance improvement for your project, and may introduce instability.
Unity currently only supports Graphics Jobs when using Vulkan and this setting has no effect when using OpenGL ES.
|Lightmap Encoding||Choose Normal Quality or High Quality to set the lightmap encoding. This setting affects the encoding scheme and compression format of the lightmaps.|
|Lightmap Streaming Enabled||Enable this option to load only the lightmap mipmaps as needed to render the current game Cameras. This value applies to the lightmap textures as they are generated.
Note: To use this setting, you must enable the Texture Streaming Quality setting.
|Streaming Priority||Set the lightmap mipmap streaming priority to resolve resource conflicts. As these values generate, Unity applies them to the light map textures.
Positive numbers give higher priority. Valid values range from –128 to 127.
|Enable Frame Timing Stats||Enable this option to gather CPU/GPU frame timing statistics.|
|Bundle Identifier||Enter the provisioning profile of the game or product you are building. The basic structure of the identifier is com.CompanyName.ProductName. This structure may vary internationally based on where you live, so always default to the string provided to you by Apple for your Developer Account. Your ProductName is set up in your provisioning certificates.
This value appears as
Note: This is shared between iOS, tvOS and Android.
|Version||Enter the release-version-number string for the bundle (for example, 4.3.6). This appears as
See the Apple developer documentation on CFBundleShortVersionString to learn more.
|Build||Enter the build number for this version of your app. This appears as
See the Apple developer documentation on CFBundleVersion to learn more.
|Signing Team ID||Enter your Apple Developer Team ID. You can find this on the Apple Developer website under Xcode Help. This sets the Team ID for the generated Xcode project, allowing developers to use the Build and Run functionality. An Apple Developer Team ID must be set here for automatic signing of your app. For more information, see Creating Your Team Provisioning Profile.|
|Automatically Sign||Enable this option to allow Xcode to automatically sign your build.|
|Scripting Runtime Version||Choose which .NET runtime to use in your project. For more details, see Microsoft’s .NET documentation.|
|.NET 3.5 Equivalent (Deprecated)||A .NET runtime which implements the .NET 3.5 API. This functionality is deprecated, and should no longer be used. Please use .NET 4.|
|.NET 4.x Equivalent||A .NET runtime which implements the .NET 4 API. This API is newer than .NET 3.5, and as such, it offers access to more APIs, is compatible with more external libraries, and supports C# 6. This is the default scripting runtime.|
|Scripting Backend||The scripting backend determines how Unity compiles and executes C# code in your Project. This setting is not enabled for iOS.|
|Mono||To use incremental builds, choose the Append option after selecting Build from the Build Settings dialog. The Replace option will perform a clean build.Compiles C# code into .NET Common Intermediate Language (CIL) and executes that CIL using a Common Language Runtime.
Warning: Mono builds are no longer accepted in the Apple App store and Mono is not supported by iOS 11 and above. Mono can only be selected when using the deprecated .NET 3.5 runtime.
|IL2CPP||Compiles C# code into CIL, converts the CIL to C++ and then compiles that C++ into native machine code, which executes directly at run time. See IL2CPP for more information.
Tip: The C++ code generated by the IL2CPP scripting backend can be updated incrementally, allowing incremental C++ build systems to compile only the changes source files. This can significantly lower iteration times.
|API Compatibility Level||The compatibility level determines which .NET APIs you can use in your Project. This setting can affect compatibility with 3rd-party libraries.
Tip: If you are having problems with a third-party assembly, you can try the suggestion in the API Compatibility Level section below.
|.Net 2.0||Maximum .net compatibility, biggest file sizes. Part of the deprecated .NET 3.5 runtime.|
|.Net 2.0 Subset||Subset of full .net compatibility, smaller file sizes. Part of the deprecated .NET 3.5 runtime.|
|.Net Standard 2.0||Compatible with .NET Standard 2.0. Produces smaller builds and has full cross-platform support.|
|.Net 4.x||Choose this option when using libraries that access APIs not included in .NET Standard 2.0. Compatible with the .NET Framework 4 (which includes everything in the .NET Standard 2.0 profile as well as additional APIs).
Produces larger builds and any additional APIs available are not necessarily supported on all platforms. See Referencing additional class library assemblies for more information.
|C++ Compiler Configuration||Choose the C++ compiler configuration used when compiling IL2CPP generated code. This setting is not enabled for iOS.|
|Use incremental GC||Use the incremental garbage collector, which spreads garbage collection over several frames to reduce gc-related spikes in frame duration.|
You can choose your mono API compatibility level for all targets. Sometimes a 3rd-party .NET library uses functionality that is outside of your .NET compatibility level. In order to understand what is going on in such cases, and how to best fix it, try following these suggestions:
|Use on Demand Resource||Enable this option to use on-demand resources.
When enabled, the Variant map for app slicing section appears.
|Accelerometer Frequency||Define how often to sample the accelerometer. If you choose Disabled, then no samples are taken. Otherwise, you can choose from 15Hz, 30Hz, 60Hz and 100Hz frequencies.|
|Camera Usage Description||Enter the reason for accessing the camera on the iOS device.|
|Location Usage Description||Enter the reason for accessing the location of the iOS device.|
|Microphone Usage Description||Enter the reason for accessing the microphone on the iOS device.|
|Mute Other Audio Sources||Enable this option if you want your Unity application to stop Audio from applications running in the background. Otherise, Audio from background applications continues to play alongside your Unity application.|
|Prepare iOS for Recording||Enable this option to initialize the microphone recording APIs. This makes recording latency lower, though on iPhones it re-routes audio output via earphones only.|
|Force iOS Speakers when Recording||Enable this option to send the phone output through the internal speakers, even when headphones are plugged in and recording.|
|Requires Persistent WiFi||Enable this option to require a Wi-Fi connection. iOS maintains the active Wi-Fi connection while the application is running.|
|Allow downloads over HTTP (nonsecure)||Enable this option to allow downloading content over HTTP. Default and recommended is HTTPS.|
|Supported URL schemes||A list of supported URL schemes.
To add new schemes, increase the value of the Size property and then set a reference to the Asset to load in the new Element box that appears.
|Disable HW Statistics||Enable this option to instruct the application not to send information about the hardware to Unity. For more details, see Unity Hardware Statistics.|
|Target Device||Select which devices the game targets. The choices are iPhone Only, iPad Only, and iPhone + iPad.|
Target SDK_ ||Select which SDK the game targets. The choices are Device SDK and Simulator SDK.
Note: Be sure to select the correct SDK. For example, if you select the Device SDK but then target the Simulator in Xcode then the build will fail with a lot of error messages. | |Target minimum iOS Version__
|Defines the minimum version of iOS that the game works on.|
|Enable ProMotion Support||Enable this option to allow high frequency refresh rates (120 Hz) on ProMotion displays. Enabling this setting might affect battery life.|
|Requires ARKit support||Enable this option to restrict the app to iPhone 6s/iOS 11 or newer devices when publishing to the App Store.|
|Defer system gestures on edges||Enable which edges that users must swipe twice to enact system gestures: Top Edge, Left Edge, Bottom Edge, and Right Edge|
|Hide home button on iPhone X||Enable this option to hide the home button on iPhone X devices when the app is running.|
|Render Extra Frame on Pause||Enable this option to issue an additional frame after the frame when the app is paused. This allows your app to show graphics that indicate the paused state when the app is going into the background.|
|Behavior in Background||Choose what the application should do when the user presses the home button.|
|Custom||You can implement your own behaviour with background processing. For an example, see the BackgroundFetch Bitbucket project.|
|Suspend||Suspend the app but don’t quit. This is the default behavior.|
|Exit||Instead of suspending, let the app quit when the user presses the home button.|
Expand the Variant map for app slicing section to see the list of variant names configured in scripting. For more information on variants, see App slicing.
Note: If you don’t see the section, make sure the Use on Demand Resource property is enabled.
You can add and remove new variants with the plus (+) and minus (-) icons. You can also select a variant from the list and see or modify its settings under Variant settings:
|Variant name||Displays the name of the variant from the loading script. For any of these settings, if you choose Custom value, an additional property appears underneath where you can enter your own value to use.|
|Device||Choose which device this variant targets. Options include Any (the default), iPhone, iPad, iWatch, and Custom value.|
|Memory||Choose the minimum memory required for this variant. Options include Any (the default), 1GB, 2GB, 3GB, 4GB, and Custom value.|
|Graphics||Choose the Metal framework to use. Options include Any (the default), Metal1v2, Metal2v2, Metal2v3, Metal3v1, Metal3v2, Metal4v1, and Custom value.|
|Display color space||Choose the color gamut to use. Options include Any (the default), sRGB, DisplayP3, and Custom value.|
You can also add your own setting. Click the Add custom entry button and a new pair of text boxes appear. Enter the name of the setting in the box displaying <key> and the value you want to use in the box displaying <value>.
|Architecture||Choose which architecture to target.|
|Universal||Support all architectures. This is the recommended option.|
|Armv7||Support only the older 32-bit ARM architecture.|
|Arm64||Support only the newer 64-bit ARM architecture. You might want to consider selecting this option if your app is only for high-end devices.|
|x86_64||Support the x86_64 Intel architecture. This is the only architecture available for Simulator SDK.|
|Scripting Define Symbols||Set custom compilation flags. For more details, see Platform dependent compilation.|
|Allow ‘unsafe’ Code||Enable support for compiling ‘unsafe’ C# code in a pre-defined assembly (for example,
For Assembly Definition Files (
|Active Input Handling||Choose how you want to handle input from users.|
|Input Manager||Use the traditional Input settings.|
|Input System (Preview)||Use the Input system. The Input System is provided as a preview package for this release. To try a preview of the Input System, install the InputSystem package.|
|Both||Use both systems side by side.|
|Prebake Collision Meshes||Enable this option to add collision data to Meshes at build time.|
|Keep Loaded Shaders Alive||Enable this option to prevent shaders from being unloaded.|
|Preloaded Assets||Set an array of Assets for the player to load on startup.
To add new Assets, increase the value of the Size property and then set a reference to the Asset to load in the new Element box that appears.
|Opciones adicionales de compilación AOT.||Additional options for Ahead of Time (AOT) compilation. This helps optimize the size of the built iOS player.|
|Strip Engine Code||Enable this tool if you want the Unity Linker tool to remove code for Unity Engine features that your Project does not use. This setting is only available with the IL2CPP Scripting Backend.
Most games don’t use all necessary DLLs. With the Strip Engine Code option enabled, you can strip out unused parts to reduce the size of the built player on iOS devices. If your game is using classes that would normally be stripped out by the option you currently have selected, you’ll be presented with a Debug message when you make a build.
|Managed Stripping Level||Choose how aggressively Unity strips unused managed (C#) code.
When Unity builds your game or application, the Unity Linker process can strip unused code from the managed dynamically linked libraries used in the Project. Stripping code can make the resulting executable significantly smaller, but can sometimes mistakenly remove code that is actually used. This setting allows you to choose how aggressively Unity should remove unused code.
|Normal||Remove unreachable managed code to reduce build size and .NET/IL2CPP build times.|
|Aggressive||Remove code more aggressively than under the normal option. Code size is further reduced, but this additional reduction may have side effects. For example, some methods may no longer be visible in the debugger and code accessed through reflection can be stripped. You can create a custom
|Script Call Optimization||Choose how to optionally disable exception handling for a speed boost at runtime. See iOS Optimization for details.|
|Slow and Safe||Use full exception handling (with some performance impact on the device when using the Mono scripting backend).|
|Fast but no Exceptions||No data provided for exceptions on the device (the game runs faster when using the Mono scripting backend).
Note: Using this option with the IL2CPP Scripting Backend does not impact performance; however, using it can avoid undefined behavior on release builds.
|Vertex Compression||Set vertex compression per channel. For example, you can enable compression for everything except positions and lightmap UVs. Whole Mesh compression set per imported object overrides where vertex compression is set on objects. Everything else obeys these vertex compression settings.|
|Optimize Mesh Data||Enable this option to remove any data from Meshes that is not required by the Material applied to them (such as tangents, normals, colors, and UVs).|
Select what type of logging to allow in specific contexts.
Check one box that corresponds to each Log Type (Error, Assert, Warning, Log, and Exception) when running scripts (ScriptOnly) , all the time (Full), or never (None).
Enable the Clamp BlendShapes (Deprecated) option to clamp the range of blend shape weights in SkinnedMeshRenderers.
|Virtual Reality Supported||Enable this if your application is a virtual reality application, then add the required VR SDKs to the list.|
|Virtual Reality SDKs||Add and remove Virtual Reality SDKs from the list. This list is only available when the Virtual Reality Supported is enabled.
To add an SDK to the list, click the plus (+) button.
To remove an SDK from the list, select it and then click the minus (-) button.
Some of the SDKs provide extra settings that appear here. For details, see XR SDKs.
|Stereo Rendering Mode||Choose how you want to render for a virtual reality device.|
|Multi Pass||This is the normal rendering mode. Unity renders the Scene twice: first to render the left-eye image; and then again for the right-eye image.|
|Single Pass||Render both eye images at the same time into one packed Render Texture. This means that the whole Scene is only rendered once, which significantly reduces CPU processing time.|
|Vuforia Augmented Reality Supported||Enable this option to use Vuforia Augmented Reality SDK, which is required when using the Vuforia Virtual Reality SDK.|
You can click the Vuforia Augmented Reality link to enable the Vuforia Software Development Kit. You must have a Vuforia Software License and agree to the terms of that license before the Vuforia Augmented Reality Supported property is enabled.
2018–11–29 Page amended with editorial review
Mute Other Audio Sources added in 5.5
iOS Player Settings documentation updated in Unity 2018.1
Allow ‘unsafe’ Code checkbox added in Unity 2018.1
.NET 4.x runtime added in 2018.1
.Net 3.5 scripting runtime deprecated in Unity 2018.3 NewIn20183
Minimum iOS version increased to 9 in Unity 2018.3 NewIn20183
Input System preview added in Unity 2019.1 NewIn20191
GPU Skinning renamed to Compute Skinning in Unity 2019.3NewIn20193