# iOS > Troubleshooting

Source: https://help-display-sdk.equativ.com/ios/troubleshooting.html

This page presents a few tips to debug and test your ads.

---

## Debug mode

You can activate the _SDK logging_ through [`SASConfiguration`](https://help-display-sdk.equativ.com/ios/API/Classes/SASConfiguration.html), using the [`loggingEnabled`](https://help-display-sdk.equativ.com/ios/API/Classes/SASConfiguration.html#/c:objc(cs)SASConfiguration(py)loggingEnabled) property.

Info, warning & error messages will be sent to the _Xcode Console_ When the _SDK logging_ is enabled. Note that error messages
will always be sent to the console even if the logging is disabled.

``` swift
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
  // ...

  // Enabling SDK logging
  SASConfiguration.shared.loggingEnabled = true

  // ...
}
```

Do not forget to turn off the _SDK logging_ by setting [`loggingEnabled`](https://help-display-sdk.equativ.com/ios/API/Classes/SASConfiguration.html#/c:objc(cs)SASConfiguration(py)loggingEnabled) to `false` before submitting your app to the _App Store_!

## Test placements

For testing purposes, it is possible to use predefined test placements that will always deliver an ad from a particular type.

This is done by using the [`SASAdPlacement(testAd:)`](https://help-display-sdk.equativ.com/ios/API/Classes/SASAdPlacement.html#/c:objc(cs)SASAdPlacement(im)initWithTestAd:) initializer (check the [`SASAdPlacementTest`](https://help-display-sdk.equativ.com/ios/API/Enums/SASAdPlacementTest.html)
 _enum_ for an exhaustive
list of the formats you can get using test placements).

``` swift
// This placement will always deliver an HTML ad
let testPlacement = SASAdPlacement(testAd: .bannerHTML)
```

Do not forget to remove all test placements before releasing your app!

## Obfuscated crash reports

If your app experiences crashes because of our SDK, you might end up with obfuscated method names for all our classes in your stacktraces.

You will need to use the **Equativ Display SDK** debug symbol (dSYM) files in order to get deobfuscated crash reports. These _dSYM_ files
can be used in _Xcode_ or can often be uploaded in third-party tools like _Firebase Crashlytics_.

Here is the complete list of available _dSYM_ files:

<ul>

        <li>[SASDisplayKit-8.6.1.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.6.1.dSYM.zip)</li>

        <li>[SASDisplayKit-8.6.0.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.6.0.dSYM.zip)</li>

        <li>[SASDisplayKit-8.5.1.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.5.1.dSYM.zip)</li>

        <li>[SASDisplayKit-8.5.0.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.5.0.dSYM.zip)</li>

        <li>[SASDisplayKit-8.4.0.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.4.0.dSYM.zip)</li>

        <li>[SASDisplayKit-8.3.1.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.3.1.dSYM.zip)</li>

        <li>[SASDisplayKit-8.3.0.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.3.0.dSYM.zip)</li>

        <li>[SASDisplayKit-8.2.3.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.2.3.dSYM.zip)</li>

        <li>[SASDisplayKit-8.2.2.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.2.2.dSYM.zip)</li>

        <li>[SASDisplayKit-8.2.1.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.2.1.dSYM.zip)</li>

        <li>[SASDisplayKit-8.2.0.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.2.0.dSYM.zip)</li>

        <li>[SASDisplayKit-8.1.0.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.1.0.dSYM.zip)</li>

        <li>[SASDisplayKit-8.0.0.dSYM.zip](https://sdk.sascdn.com/mobile/displaysdk/ios/SASDisplayKit-8.0.0.dSYM.zip)</li>

</ul>
