Help

1 min read

Airship

The PoqAirship integration wraps the Airship SDK allowing it to be plugged into the PoqSDK to enable remote notifications driven by Airship. This also includes the Airship Inbox and Preference Center, which work with the Account badges, and are styled to match the rest of the app.

Set Up

The Airship integration requires AirshipConfig plists for production and developer mode.

Notifications

Airship can be set up as a single 'Live' project or with an additional 'Test' project. When the app is being run via Xcode it will connect to the 'Test' project. When the app is archived for any type of distribution, Xcode switches the app to connect to the 'Live' project.

A developer will need to make sure the Airship projects are set up with your Apple Account APNs Key. Use the existing key; there should only be 1 APNs key that should be shared by all apps in that account.

Developer Mode

Airship switches to use the AirshipConfig-Development.plist config when in development mode, if it exists. If this config does not exist then Airship uses the live config instead (in developer mode). Whilst it's less of an issue for Airship, this does means that any fake purchase revenue from development environments will be sent to Airship as if it was live revenue.

Environment

On iOS an Environment:{id} tag is added to segment the audience by 'AppConfig' where {id} is replaced with the config identifier.

History

  • v24: Reworked analytics for SDK changes.
  • v23: Added iOS environment-based tags and Airship Automation for In-App messages.