Integration Guide QdsInappWrapperLib for iOS

The integration of QdsInappWrapperLib takes place in the same way as IOLib (see Integration Guide iOS)

The following notes are to be additionally followed for integration:

The QdsInappWrapperLib comes as a "framework" together with a shell script for the build process. The "QdsInappWrapperLib" needs to be copied into the root directory of you project. Drag the "QdsInappWrapperLib.framework" from the file system to your Xcode project.

Check "Copy items if needed" in the dialogue box that appears. Also check "Create groups". If the framework hasn't appeared in the "Linked Frameworks and Libraries" section of your Xcode project, please add it manually by dragging it from the Xcode project explorer on the left to the "Linked Frameworks and Libraries" section.

Furthermore Xcode should have added the path to the framework to the "Framework Search Paths" in the "Build Settings" tab. If the path is missing, add the path to the framework directory accordingly.

Now  you just need to include the shell script in the "Build Phases". Switch  over to the "Build Phases" tab and create a new "Run Script"  configuration via the "New Run Script Phase" action. If you copied the  "QdsInappWrapperLib" directory to the root directory of the Xcode  project, you may include the script within the newly created "Run  Script" phase as follows:


"SystemConfiguration.framework" and "AdSupport.framework" must be integrated as additional "Linked Frameworks and Libraries" (see IOLib).

To obtain access to all required interfaces, the corresponding source file must import the required header file as follows:

#import <QdsInappWrapperLib/QdsInappWrapperLib.h>


The QdsInappWrapperLib is represented by the class QdsInappWrapper. A concrete instance of this class is created with:

[[QdsInappWrapper alloc] init];

The QdsInappWrapperLib must be initialized when calling the app. This takes place by way of the above-mentioned call.
To enable display of a survey invitation, call the method


The offerIdentifier and country code (with "at") must be passed on in this context.
The parameter offerIdentifier is the unique identifier of the offer for the respective app.
The offerIdentifier is assigned by ÖWA for each app and each operating system.

Any initial loading processes should be completed at the start of a session, since a poll invitation
may be displayed immediately after calling startSession.

[[[QdsInappWrapper alloc] init] startSession:@"offerIdentifier"

If loading dialogues are shown when starting the app, startSession should only be called subsequently,
since the invitation dialogue is displayed prematurely otherwise. Generally, calling startSession means
that a dialogue with a survey invitation may be displayed after calling of the method. startSession should
be called once the app is ready to display a questionnaire if needed. Generally, startSession can be called


After successful integration of QdsInappWrapperLib, the survey invitation should be displayed immediately after the initial launch of the app, and every time it is switched to the foreground. If this is not possible for technical reasons, a suitable alternative entry point is to be selected by the developer. The important factor is that the user must get the opportunity to interact with the potential survey dialogue.

The opt-out function is controlled by QdsInappWrapperLib via the survey invitation, so no further action is necessary for this. Survey and data protection information on the ÖWA study are optionally shown to the survey participant within the survey.

Test - Display dialogue window:

Please use the INFOnline SZM checker to mark the device as a test device. The documentation for the INFOnline ÖWA-Checker is available at

Please check correct display of the survey invitation, clickability of all buttons, and opening of the questionnaire by clicking on the participate button.

The customer is responsible for installation of QdsInappWrapperLib in accordance with the valid guidelines of ÖWA. The customer is responsible for ensuring that the implementation of the library is correct even if the app is changed.