Troubleshooting on iOS
This page presents a few tips to debug and test your ads.
Table of contents
Debug mode
You can activate the SDK logging through SASConfiguration , using the 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.
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 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:) initializer (check the SASAdPlacementTest enum for an exhaustive list of the formats you can get using test placements).
// 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: