Key takeaway:
Department’s new Integration Validator for iOS mechanically checks your setup and catches points earlier than launch.
Department’s iOS software program improvement equipment (SDK) allows intensive performance on your app, making it necessary to totally take a look at the combination earlier than launch. To streamline this course of, Department has revamped its Integration Validator instrument to automate testing.
New performance contains:
- Automated configuration testing for Department keys, Bundle ID, Staff ID, and domains
- A popup modal displaying take a look at outcomes
- Visibility exhibiting which model of the Department SDK you might be utilizing and which key (reside or take a look at) your app is at the moment pointing to
- Single-click log exporting
- Affirmation addressing whether or not or not the Identifier for Advertisers (IDFA) is accessible
This submit explains how you can use the brand new testing and validation options to make sure your Department integration is ready up appropriately.
How you can validate your Department SDK integration
Earlier than utilizing Department SDK options, confirm your setup with the next steps:
1. Add the next line of code to the underside of the didFinishLaunchingWithOptions operate in your app: Department.getInstance().validateSDKIntegration()
2. Run your app on a tool or simulator. The Department Integration Validator modal will seem and present the next info:
- SDK Model: Affirm you might be utilizing the newest model. Examine the Department iOS SDK Model Historical past.
- App Key: Reveals whether or not your app is pointing to the reside or take a look at setting.
- Validation exams: Every line merchandise represents an integration verify, together with a verify icon if the take a look at handed or an “x” if it failed. Let’s evaluate what every take a look at means.
- Default Domains: Checks that the app.hyperlink and test-app.hyperlink domains out of your Department Dashboard have been added to the Data.plist and that the values match.
- Alternate Domains: Checks that the -alternate.app.hyperlink and -alternate.test-app.hyperlink domains out of your Department Dashboard have been added to the Data.plist and that the values match.
- URI Scheme: Ensures that the URI scheme you added to the Data.plist matches the URI scheme entered in your Department Dashboard. That is necessary as a result of Department hyperlinks will fall again to utilizing URI schemes to open the app if Common Hyperlinks fail.
- App Bundle ID: Confirms that the Bundle ID used to signal the construct matches the dashboard entry. Common Linking requires this.
- Staff ID: Confirms the Staff ID used to signal the construct matches the Staff ID enter on the dashboard. Common Linking requires this match.
- IDFA Accessibility: Whether or not or not the IDFA is accessible within the app
If a take a look at fails, a pink ‘X’ icon will clearly point out the wrong configuration:
The XCode logs can even include some further particulars in regards to the exams:
Click on ‘What ought to I alter?’ for an inventory of required edits, together with explanations of what every lacking configuration controls.
Use the ‘Export Logs’ button to repeat or share logs. That is particularly useful if you could contact [email protected] for help.
Utilizing Department’s Integration Validator spots and fixes configuration points earlier than releasing your app. To get began with Department, request a demo.
Further sources:
For troubleshooting help, attain out to your account group.
