Info.plist Keys

The Dingi Maps SDK for iOS supports custom Info.plist keys in your application in order to configure various settings.


Set the DingiMap access token to be used by all instances of DingiMapView in the current application.

Dingi-hosted vector tiles and styles require an API access token, which you can obtain from the DingiMap account page. Access tokens associate requests to Mapbox’s vector tile and style APIs with your DingiMap account. They also deter other developers from using your styles without your permission.

As an alternative, you can use DingiAccountManager.accessToken to set a token in code. See our guide for some tips on keeping access tokens in open source code private.


The name of the font family to use for client-side text rendering of CJK ideographs. Set this to the name of a font family which will be available at run time, e.g. PingFang TC (iOS 9+), Heiti TC (iOS 8+), another appropriate built-in font, or a font provided by your application. Note that if a non-existent font is specified, iOS will fall back to using Helvetica which is likely not to include support for the glyphs needed to render maps in your application.


If this key is set to YES (true), collision detection is performed only between symbol style layers based on the same source, as in versions 2.0–3.7 of the Mapbox Maps SDK for iOS. In other words, symbols in an DingiSymbolStyleLayer based on one source (for example, an DingiShapeSource) may overlap with symbols in another layer that is based on a different source (such as the Mapbox Streets source). This is the case regardless of the DingiSymbolStyleLayer.iconAllowsOverlap, DingiSymbolStyleLayer.iconIgnoresPlacement, DingiSymbolStyleLayer.textAllowsOverlap, and DingiSymbolStyleLayer.textIgnoresPlacement properties.

Beginning in version 4.0, the SDK also performs collision detection between style layers based on different sources by default. For the default behavior, omit the DingiCollisionBehaviorPre4_0 key or set it to NO (false).