Mobile Surveys

Important: 

In order for your apps to receive and display mobile surveys please integrate with the latest mobile sdks (released late June 2016). Survey support starts on versions 3.7.0 (both iOS and Android). Once you’ve updated you’re ready to start using Mobile Surveys!

Surveys are set up via the web panel and presented to a participant while they’re using your app.

Setting up a survey

survey1

In the left hand menu click on “Surveys” and then on “Create survey”

survey2

You can set the survey Title and Introduction message. These are displayed at the top of the survey.

surveytitle

Plus the prompt that will ask the participant to take the survey.

surveysprompt

Now add some questions

survey3

You can choose from three options:

Single selection – participants can choose one of several options.

survey4

The participant will the following:

surveyssingle

Multiple choice – participants can choose more than one option.

survey5

The participant will see something like:

surveymultiplechoices

Free form – participants can give textual feedback based on the question.

survey7

Mandatory Questions

By checking the “Mandatory” check box it is possible to ensure that participants answer that specific question.

Targeting Groups

If “All participants” is selected then all participant added to your application will be prompted to take the survey.

survey-targetgroups

Alternatively it is possible to narrow down the participants by group (see above)

survey-groups

Triggers

It’s possible that to add a trigger delay based on current session time (session starts when the participant logs in to the Applause SDK).

surveys-trigger

In the coming months we will be adding more and more sophisticated triggers.

Publishing

Finally clicking on ‘Publish Survey’ will open up the survey to your participants!

surveypublish

What can I change after publishing?

It is possible to change anything that might break the logic of the survey.

  • Triggers (currently session time)
  • Targeted groups

You cannot edit question or choice texts. As you might imagine changing the question text in the middle of a survey from “Do you like cats?” to “Do you like dogs?” would invalidate the survey results.

Closing your survey

In the “Publish” tab you can close the survey by clicking on “Close Survey”. Once a survey has been closed no more results will be accepted or presented to participants.

Applause Android SDK Installation Guide for ANT

STEP 1 – INTEGRATE THE APPLAUSE ANDROID SDK

Please see: our download page to get the latest Android SDK

STEP 2 – RUN THE SDK

Each time your app launches, you should start a new Applause SDK session. The only action to take is to invoke the Applause.startNewSession() method in the onCreate event of your application class.

First, make sure you import the Applause SDK

import com.applause.android.Applause;

Then launch the Applause SDK

public class MyApplication extends Application {
    @Override
    public void onCreate() {
        super.onCreate();
        Applause.startNewSession(this, "Your-Application-Key-Goes-Here");
    }
}

STEP 3 – MODIFY THE ANDOIRD MANIFEST FILE

Make sure to declare Applause SDK activities in the <application> section. The result should look as follows

<application>
  <activity android:name="com.applause.android.ui.ProblemActivity" />
  <activity android:name="com.applause.android.ui.FeedbackActivity" />
  <activity android:name="com.applause.android.ui.ScreenshotEditorActivity" />
</application>

STEP 4 – PERMISSIONS

Appluase SDK requires the android.permission.INTERNET permission to work. Please add following line inside <manifest> tags

<uses-permission android:name="android.permission.INTERNET"/>

Appluase SDK is capable of gathering device state like Bluetooth or Networking. Please check detailed instruction in this section.

For more info

For more information like setting the API key go to the main help page

Exporting Bugs and Feedback and Crashes to Jira and other Bug Tracking Systems

Exporting Bug, Feedback and Crash items to Jira and other BTS’s is possible through the web panel.

As well as the bug, feedback or crash data you’ll also export screenshots and session data.

Step 1: Set up the BTS Integration via the right menu item ‘Integrations

integrations1

Step 2: Select which BTS you wish to integrate with :

You can choose from: JIRA, TFS, GITHUB, BUGZILLA, FOGBUGZ, MANTIS, RALLY, ASANA, REDMINE, PIVOTAL and EMAIL

 

integrations

In JIRA you must enter the host url, JIRA username, password, Issue Type and Project Key.

URL: the url where you JIRA is hosted. Please note that this has to be accessible to MBM and not blocked by a firewall. See here for more details about firewalls.

Username: this is usually not an email address but the first part of an email address before the ‘@’ sign. Please consult your JIRA admin if you don’t know your username.

Issue Type: is the default issue type in JIRA that you want creating after the export. E.g. in the above example all crashes, bugs and feedback will be reported as a ‘Bug’ once exported.

Project Key: Is the project identifier in JIRA

Once you click ‘Update Integration‘ you will be asked to define some BTS field mappings for mandatory components.

Step 3: Define mappings

integrations2

The mappings will differ for each JIRA project depending on how you have configured your project.

Clicking ‘Save’ will confirm the mappings and the BTS export is in place.

Step 4 Exporting Issues  

You can export Bugs, Feedback or Crashes either from the Dashboard, Reports or the details section.

integrations3 integrations4

 

 

 

 

 

 

 

 

You can either export issues individually or via a bulk export.

Once reported a link will be provided to the issue created in the BTS.

integrations5

Pro-actively survey your beta participants for Contextual Feedback

Since the mobile SDKs 3.2.0 it’s now possible to proactively seek feedback from your user base.

For example, if you are testing a new feature you can set up a ‘trip wire’ in the flow to prompt the user for feedback about the new feature. (They don’t need to shake!)

How it works

You can customize the following attributes of the Feedback UI:

– TITLE
– HINT
– TAGS
– RATING_TITLE

The application starts to listen after a successful Applause SDK login. So please make sure any trip wires are laid after you start your Applause session.

The context is expressed in the TAGS parameter, here you can tag your feedback with a context so that in the web panel you know from where in your application the feedback came.

 

Android Example 

Intent intent = new Intent(context.getPackageName() + "/feedback");
intent.putExtra("TITLE", "Custom Title");
intent.putExtra("HINT", "My custom hint");
intent.putExtra("RATING_TITLE", "Custom Rating title");
String tags[] = new String[]{ "dashboard", "premium_user"};
intent.putExtra("TAGS", tags);
context.sendBroadcast(intent);

contextualfeedbackdroidui

iOS Example

NSDictionary *feedbackSettings = @{

@"TITLE": @"Custom title",
@"RATING_TITLE": @"Custom rating title",
@"HINT": @"My custom hint",
@"TAGS": @[@"tag1", @"tag2", @"tag3"]}; 
[[NSNotificationCenter defaultCenter] postNotificationName:@"APLShowContextualFeedbackNotification" object:nil userInfo:feedbackSettings];
 
contextualfeedbackiosui


Applause SDK: Android Installation Guide

EXAMPLE APPLICATION

Want to see the Mobile SDK up and running in a demo project right now? Take a look at our Android Hello World application – available in Github.

https://github.com/ApplauseAQI/AH-Android-Int

STEP 1 – INTEGRATE THE MOBILE SDK

First visit the download page to get the latest Applause Android SDK

If you’re not using gradle please see:

STEP 2 – RUN THE SDK

Each time your app launches, you should start a new Applause SDK session. The only action to take is to invoke the Applause.startNewSession() method in the onCreate event of your application class.

Please note the ‘withUTestEnabled‘ flag. If you’re using beta.applause.com then this has to be set to false. But if you’re using our uTest testing services it should be true.

First, make sure you import the Applause SDK

import com.applause.android.Applause;
import com.applause.android.config.Configuration;

Then launch the Applause SDK

public class MyApplication extends Application {
    @Override
    public void onCreate() {
        super.onCreate();
        Configuration configuration = new Configuration.Builder(this)
            .withAPIKey("Your-API-Key-Goes-Here")
            .withUTestEnabled(false)
            .build();
        Applause.startNewSession(this, configuration);
    }
}


APP Key

Note in order for your application logs, bugs and crashes to be reported to your application you have to add the API key within the confiuration.

Go to beta.applause.com and in the dashboard or settings of your application you’ll see your app key.

APPkeySettings

STEP 3 – PERMISSIONS

By default the SDK adds the android.permission.INTERNET permission. This is required for SDK to contact the sessions server.

Applause SDK is capable of gathering device state like Bluetooth or Networking. Please check the detailed instructions in this section.

Additional Information

Applause SDK for Android Changelog

3.9.4

  • Hot fix for duplicated Report Dialog

March 1st, 2017

3.9.3

  • Fix for Auto-Instrumentation

February 3rd, 2017

3.9.2

  • Fix for Auto-Instrumentation

September 22nd, 2016

3.9.0

  • Support for Android Nougat
  • Added Portuguese localization
  • When app is sending message to server basic bootstrap info is refreshed
  • Deprecate Market Mode, Contextual Feedback and Quick Login – planned to be removed in next version

September 9th, 2016

3.8.0

  • Unified bug and feedback report attachments
  • Added SDK/application version in settings

July 25th, 2016

3.7.2

  • Surveys

July 7th, 2016

3.6.4

  • Update for AIS: fail gracefully if Android version is not supported

May 30th, 2016

3.6.2

  • Fixed various bugs for offline sessions

April 28th, 2016

3.6.0

  • Import video attachments to bug report from System Gallery

April 18th, 2016

3.5.4

  • Minor fixes in spanish translations
  • New feature: track NFC state
  • New feature: track Audio state
  • Fixes to Bug reporting UI

April 11th, 2016

3.5.2

  • NFC service support
  • less sensitive shake detection

Mar 23rd, 2016

 3.5.0 – March 15th 2016

Updates:

  • Improved  handling of offline sessions
  • Korean, German, Spanish, and French l10n
  • Less verbose logging of the SDK internals
  • Better bug and feedback attachments handling

3.4.9 – March 7th 2016

Updates:

Improve screenshot taking for OpenGL views

3.4.8 – March 2nd 2016

Updates:

  • Data persistence improvements
  • several  small UI fixes
3.4.6 – Feb 23rd  2016  
Updates:
  • Data persistence improvements
  • small UI fixes
  • fixed crash for some clients
  • Updated mechanism of importing Images to a report
3.4.4 – Feb 15th  2016  
Updates:
  • DB small refactor
  • Improved startup procedure
  • Bug steps UI improvement (back end only)
3.4.2 – Feb 7th  2016  
Updates:
  • bug fixes
  • Network optimisations
3.4.0 – January  25th  2016
Updates:
  • Rebranding of User Interface
3.3.2 – November 25th  2015
Updates:
  • Bugs fixes for UI issue with capturing screenshots
3.3.0  – November  13th  2015
Updates:
  • UI update removes the need for the ‘android.permission.SYSTEM_ALERT_WINDOW‘ permission in manifest.
3.2.2 – October  13th  2015
Updates:
  • Screenshots for Contextual Feedback Added
3.2.0 – September 30th  2015
Updates:
  • Contextual Feedback Added
3.1.5 –  September  2015
Updates:
  • Optional Tutorial Dialog
3.1.2 –  September  2015
Updates:
  • Installation counter bug fixed.
3.1.0  –  August  2015
Updates:
  • Switch for uploading files only via WiFi
  • Lots of bug fixes and stability improvements
NOTE:
This version is the last one support Android 2.2 and 2.3. Next version will support 4.+ devices.
3.0.0  –  July 2015
Updates:
  • Screen recording for Android 5+. Create bug reports with video attachments.
2.9.2 –  June 2015
Updates:
  • Various bug fixes
2.9.1 –  June 2015
Updates:
  • Import attachments from system gallery
  • Import attachments from camera
  • SDK Tutorial
2.8.3 – May 2015
Updates:
  • hot fix for dialogs
2.8.2 – May 2015
Updates:
  • removed passcode from BETA login page
  • stability fixes for notifications and shake to report
  • decreased number of required characters to 1 in report screen
  • anonymous user is shown as Anonymous Tester instead of the e-mail address
2.8.1 – April 2015
Updates:
  • new bug report view, now you can also provide: title, problem description, steps to reproduce and severity
  • new configuration flag available ‘notificationsEnabled’, setting it to false will hide login and report notification
  • feedback view is enabled by default
  • stability improvements and bug fixes
2.7.4
Updates:
  • Support for Android 5.1
2.7.2
Updates:
  • various UI updates and bug fixes
2.7.1
Updates:
  • login as anonymous is saved in SDK preferences
    setting setDefaultUser(“anonymous@apphance.com“) trigger login action automatically
  • Feedback view performance fix
  • bug fixes
2.7.0
Updates:
  • Beta tutorial
  • misc. bug fixes.
2.6.3
Updates:
  • Beta login dialog better experience
  • Disabled anonymous login for uTest enabled builds
  • Bluetooth, Networking, Telephony reported conditions update. They are more verbose.
2.6.2
Updates:
  • Added passcode rest (for Mobile Beta Management only)
  • Condition watcher fixes (e.g. battery state, bluetooth state, etc.)
  • Additional bug fixes
2.6.1
Updates:
  • WithDefaultUser()  automatically chooses user from quick auth
  • Enhanced  user experience during quick auth login
  • Bug fixes
2.6.0
Updates:
  • Mobile Beta Management compatibility
2.5.3: Pre-Production & Production Release
Updates:
  • Fixed bug with installation count
  • Fixed problem with reporting issues in airplane mode
  • Tapping on notifcation shows same dialog as shake action
  • Fixed problem with logs filtering
2.5.0: Pre-Production & Production Release
Updates:
  • New UI for Report Dialog
  • Improved screenshot performance
  • Created fallback actions for ANT projects with incorrectly configured AndroidManifest
  • Android dialogs, Toast and Action Bars  can  now be captured in screenshots

Features:

  • Silent Login: Users are automatically authenticated if store credentials are valid
2.4.0: Pre-Production & Production Release
Updates:
  • Library renamed from ‘applause-sdk-preprod’ to ‘applause-sdk’
  • Crash stack trace contains optional cause
  • Cleaned up notification behavior
  • Sending screenshots with overlays bug fixed
  • Improved quick login list performance
  • Screen density is shown as mdpi/hdpi instead of integer value
New Features:
  • Production environment support re-introduced
2.3.0: Pre-Production Release Only
Updates:
  • Sped up screenshot workflow, users no longer have to wait to see report view
  • Updates to disabled build user notifications
  • UI update for test cycle dialog
  • Fixed bugged Applause dialog closing behavior
2.2.0: Pre-Production Release Only
Updates:
  • Improved shake detection on a wider range of mobile devices
  • Added landscape support for in-app bug report dialog
  • Added landscape support for in-app feedback dialog
  • Screenshot editor adapts to display orientation
  • Added UI support tablets
  • Updated  UI font
  • Resolved issues with screenshots on Android 4.0
  • Resolved issue with remembering  username and password (if selected)
  • Resolved a number of crashing issues
2.1.0: Pre-Production Release Only
Updates:
  • Improved feedback to user regarding login (via Toast messages)
  • Feedback crash fixed
  • Screenshot issue affecting Android 4.1 fixed
  • Report Problem Activity activated on shake, even if app is in background
  • Notification bar spamming issue fixed
2.0.0: Pre-Production Release Only
Updates:
  • ‘Apphance’ brand has been retired and replaced with ‘Applause SDK’
  • All classes and configurations have been revised.  â€˜apphance’ instances have been replaced by  â€˜applause’
  • Integration with Applause SDK is as easy as possible. Developer has to call only Applause.startNewSession() method. The should not be using: Apphance.onStart() or Apphance.onStop() any more.
  • Additional integration refinements
  • Names in imports have been changed to reflect Apphance to Applause SDK rebrand
  • Session and Crash reporting integration with Applause 360 degree dashboard

New Features:

  • For Maven users: Can merge manifest if <mergeManifests> flag in configuration is set to: true
  • Changes and additions to required and optional permissions
  • startNewSession no longer needs to be an Activity and can be launched from anywhere the context is available

Download >>

————————————————————————————————–
1.9.13: Pre-Production + Production Release
March 16, 2014
  • Minor fixes
1.9.6 – Pre-Production Release Only
October 8, 2013

Fixes:

  • Fixed issue with PNG resource (it was a JPG) when using aar.
1.9.5: Pre-Production Release Only
September 12, 2013

Fixes:

  • Fixed issue where notifications were not visible in SILENT mode
  • Fixed crash when integration with uTest was on but no test cycle was available
  • Fixed bug where typing an incorrect password froze the app (typing in a wrong password prevented the user from retrying)
  • Version number sent correctly as 1905 (instead of 195)
1.9.3: Pre-Production Release Only
August 12, 2013

New Features:

  • Introduced an experimental NativeLog util class which can be useful with native code for sending logs and crashes. Details are in the javadoc for the NativeLog class.

Fixes:

  • Eliminated possible deadlock when connection was re-established during logging process
  • Fixed app crash when returing back from certain external Activities (like Camera, GMail, Preferences etc) (NullPointerException in Apphance.java:799 and Apphance.java:811)
  • Improved escaping for invalid JSON characters. For example, in previous versions, logs with certain special characters like “r” prevented the log from being sent to the server (due to malformed JSON)
  • Corrected issue where Apphance forces the login dialog to be in portrait mode. Now users can login using landscape mode as well.

Refactor:

  • The Apphance.startNewSessionNow() method is now deprecated, and users should use startNewSession instead. The behavior is exactly the same. Note that we have not supported or documented startNewSessionNow() in over a year, so most current users should already be using the correct method. This should only impact long-standing Apphance users.
1.9: Pre-Production + Production Release
July 18, 2013

New Features:

Pre-Production Only:

  • New integration approach that replaces instrumentation in the manifest.xml file
  • New onStart and onStop methods for tracking activities (used for capturing screenshots for bug reporting)
  • Spray feature for hiding sensitive information on bug report screenshots
  • Dialogs have replaced activities – e.g. Login is now a dialog displayed on top of the source activity instead of a new activity
  • The bug report editor can be run in a separate process to increase available memory for taking screenshots

Production Only:

  • New onStart and onStop dummy methods for compatibility with the pre-production library

Fixes:

Pre-Production Only:

  • Apphance runs smoothly with the Eclipse debugger

Production Only:

  • Minor bug fixes and improvements
1.8.3: Pre-Production Release Only
February 20, 2013

Fixes:

  • Fixed a crash issue when uTest integration was enabled on the device side but not on the server side.
  • Fixed a crash issue when the Android device does not expose the fdisk linux tool (used for collecting device info at startup).
  • Fixed an issue where the app froze with improperly implemented splash screens.
1.8.2: Pre-Production + Production Release
January 24, 2013

Fixes:

  • Minor bug fixes
1.8.1: Pre-Production Release Only
December 6, 2012

Fixes:

  • Fixed issue with using the killswitch feature while the library is in silent mode.
1.8: Pre-Production + Production Release
November 30, 2012

New Features:

Pre-Production Only:

  • Added kill-switch feature to the pre-production SDK
  • CPU + Memory optimization of the login screen activity – the quick login window might have loaded user avatar images multiple times.

Production Only:

  • Added feedback feature to the production SDK
1.7.2: Pre-Production Release Only
October 30, 2012

Fixes:

  • Stability Improvements
1.7.1: Pre-Production + Production Release
October 17, 2012

Fixes:

  • Apphance no longer crashes the app on the GT-P6810 device
  • No race condition while gathering device info: Concurrent modification exception
  • Apphance does not cause a java.lang.ArrayIndexOutOfBoundsException -> length=12; index=-1 exception when the user locks the screen on the problem reporting screen
  • Apphance should no longer detach itself from the app (user could no longer send a problem report)

Improvments:

  • Major login activity optimizations
1.7: Pre-Production + Production Release
September 12, 2012

Fixes:

  • Apphance works correctly when an application receives system intents (sending an SMS, etc.)
  • Lots of stability fixes
1.0: Pre-Production + Production Release
August 15, 2012

Initial version of the Android pre-production library.

How to get the Applause Android SDK

The Applause Android SDK works in both production and pre-production is now at version 3.9.2

We offer three methods of integration

Gradle (recommended integration method)

Add the following dependency in your application’s build.gradle file

compile 'com.applause:applause-sdk:3.9.2@aar'

Maven

In order to use Applause SDK in projects using Android Maven Plugin, you will need to modify your application’s pom.xml file.

<dependency>
      <groupId>com.applause</groupId>
      <artifactId>applause-sdk</artifactId>
      <version>3.9.2</version>
      <type>aar</type>
</dependency>

Ant

In order to use Applause SDK in projects using Ant you need to download the latest zip file.

Unpack the archive. It contains standalone Eclipse project based on Ant build system. We advice to add this line in your application’s project.properties file

android.library.reference.1={path_to_upacked_archive}

This will tell both command line interface and Eclipse builder that you application depends on Applause SDK.

Note: If your application has already other dependencies please replace ‘1’ number with the next continuous integer.

 

Changelog

You can review  our changelog to see what’s updates we’ve been rolling out.

Tagging Issues

It’s now possible to add tags to your bugs and feedback. Tagging helps you keep track of important issues and organise them in a way that makes sense for your project.

Please Note: This feature is currently only available to Admin users.

You can add / edit tags from either the list view.

 

Or from the details view.

You can then search for the tags.

  

What kinds of data are collected by the Mobile Beta Management platform?

Note:  At no time does Applause collect or store personally identifiable information.  To learn more about  the Applause privacy policies:  Click Here

The Mobile Beta Management platform collects as wide assortment of technical data as well as user feedback. This provides beta managers and their internal teams with a comprehensive view of their beta app and their users’ experience.

Sessions: Offers a real-time view of beta  sessions as they occur. This feature  provides information on app installation, app usage, device type and state, user geo-location, and more. “Sessions” begin when a user starts or wakes an application, and they typically end when the application crashes, when the device announces that a new session has started, or after 48 hours have passed with no new activity.

Crashes:  Provides diagnostic information including timestamp of the crash, stack trace, logs, device conditions and system information.

What is  never collected by the MBM platform includes:

  • Unhashed Device IDs
  • Device Name
  • Exact Location
  • MAC address, SSID, or other identifying network info

 

 

Applause SDK for iOS Changelog

Applause SDK for iOS Changelog

3.11.0:

April 14, 2017

  • removed build setting which informed that embedded content contains Swift
  • removed Logger.swift — to avoid Swift compatiblity issues

Download

3.10.2:

November 17th, 2016

  • support for swift 3.0.1

3.10.1:

October 11, 2016

  • fixes crash on iOS 8 on Simulator when logs from simulator were disabled
  • fixes crashes related to location reporting when session was not started
  • improved documentation in code
  • added view controller’s title to custom condition

Download

3.10.0-swift2.3:

October 3, 2016

  • compiled with iOS SDK 10 and Swift 2.3, (if you use Swift 3, please use plain 3.10.0 version)
  • special version of 3.10.0 to support Swift 2.3 apps

Download

3.10.0:

September 29, 2016

  • compiled with iOS SDK 10 and Swift 3, (3.9.0 is the last version which supports Swift 2.2)
  • deprecated contextual feedback
  • deprecated option to enable Mach Exceptions
  • deprecated Objective-C category APLSwiftLoggingSupport

Download

 

3.9.0:

September 9, 2016

  • added Portuguese localization
  • support for first version of Applause watchOS SDK
  • marked SKD Mode as deprecated – planned to be removed in next version
  • when app is coming from background basic bootstrap info is refreshed
  • bug fixes and stability improvements

Download

3.8.0:

June 1, 2016

  • unified bug and feedback report
  • added SDK/application version in settings
  •  bug fixes and stability improvements

Download

3.7.0:

July 4, 2016

  • added in-app surveys
  • updated database model to V6

Download

3.6.0:

April 18, 2016

  • dropped support for iOS 7
  • updated framework from static library framework to dynamically linked embedded framework
  • added Swift Logger class
  • inform user about server maintenance
  • numerous refactors and clean ups
  • bug fixes

Download

March 31st, 2016

3.5.1:

  • Partial Xamarin implemenation to support future capabilities when productized.

Download

February 29, 2016

3.5.0:

  • localised strings consolidation with Android SDK
  • added localisation for: German, French, Spanish and Korean
  • added support for boostrap quality parameters (video and images)
  • UX improvements for login and bug report screens
  • improved UI for BETA login screen
  • numerous bug fixes and stability improvements
  • refactored screen recorder – added tests for it
  • Updated database model to V5

Download

3.4.1:

Feb 22nd, 2016

  • UI bug fixes

Download

3.4.0:

Feb 15th, 2016

  • numerous bug fixes and stability improvements
  • enabled MBM for MQA
  • minor UI adjustments
  • resolve issue with build warnings on Xcode 7
  • Updated database model to V4

Download

Jan 22, 2016

3.3.0:

  • Updated database model to V3
  • dropped support for iOS 6 (last SDK supporting iOS 6 is 3.2.5)
  • new SDK Peregrine UI
  • extracted CoreSDK
  • strings localization for Spanish – Hola! Que Tal!
  • data which was synced is removed from local data base
  • enabled MBM for MQA (with a support for both QA and Market modes)
  • numerous bug fixes and stability improvements

Download

December 8, 2015

3.2.5:

  • fixes crash related to CoreData when packet was saved

Download

November 24, 2015

3.2.4:

  • fixes issue with double login page

Download

October 22, 2015

3.2.3:

  • added Screen Recording feature for MQA library

Download

October 22, 2015

3.2.2:

  • changes default value of “Upload attachments only via WiFi” setting

Download

October 8, 2015

3.2.1:

  • fixes issue with dylib – session logs were not sent after AIS
  • fixes bug with production feedback on MQA
  • fixes crash with contextual feedback
  • resolves minor UI glitches

Download

September 16, 2015

3.2.0:

WARNING: This version has breaking bug which prevents from sedning messages when app was auto-instrumented.

  • adjustments for iOS SDK 9 (toast, interface rotations)
  • library supports Bitcode
  • this version requires Xcode 7 to compile due to the bitcode support
  • user can now pick videos when adding attachments
  • improved handling of not sufficient permission to access photo library and camera

Download

September 7, 2015

3.1.0:

  • added option to disable tutorial
  • added tappable version label on login screen (toggles between app and SDK version)
  • contextual feedback, triggered by notification
  • introduced database migration mechanism
  • support for upload API V1
  • bug fixes and stability improvements

Download

September 2, 2015

3.0.1:

  • fixes issue when serverURL was not set, no messages were pushed to backend server

Download

August 26, 2015

3.0.0:

  • added Screen Recording feature
  • reworked from ground up the internals of how SDK is storing data, for persistence we now use CoreData framework based on SQLite, rather than text files
  • dropped support for iOS 5

Download

2.4.1:

June 18, 2015

  • added support for Cordova Plugin
  • enabled tutorial for MQA
  • enabled structured bug report for MQA
  • adjusted color scheme for bug and feedback screens for both MQA and Applause SDK
  • removed 10 character limit for bug and feedback description
  • improved wording in error toast in bug report

Download

2.4.0:

May 12, 2015

  • removed passcode from BETA login page
  • fixes bug with two initial screenshot attachments in bug report
  • fixes bug with missing option to open tutorial screen from report type choser

Download

2.3.0:

May 7, 2015

  • new structured bug report
  • improvements to the splash screen message view
  • fixed bug with disappearing report screen presented quickly after auto-login
  • fixed bug that forget passcode screen can be accessed from tutorial
  • making sure that only one session can be started during app lifetime
  • improvements around failed login requests

Download

2.2.3:

April 30, 2015

  • fixed issue that reported bugs are not going to test cycle

Download

2.2.2:

March 18, 2015

  • fixed bug with screenshots of tiled views
  • fixed bug with broken support of reportOnShakeEnabled flag
  • migrated Applause data from Documents directory
  • fixes for BETA tutorial
  • minor cleanups of the SDK code
  • MQALogger has old and un-deprecated production feedback methods

Download

2.2.1: Welcom Screen & Tutorial

March 6, 2015

  • introduced rich text for Welcome message
  • added tutorial for BETA
  • bug fixes and stability improvements

Download

2.2.0:

February 18, 2015

  • merged pre-prod and production sdk’s into a single sdk (to rule them all)

Download

2.1.4: Pre-Production and Production Release

January 14,2015

New Features:

  • Improved “forgot password” flow

Updates:

  • When device is offline, error message will return “Connection failed” instead of “No connection”.
  • Fixed popup issue on iPad 2s running iOS 8.1.2
  • Fixed failing test issue in APLUsersIdentifyServiceSpec
  • Fixed crash when CLLocationManagerDelegate is destroyed in callback
  • Will no longer display ‘Forgot passcode’ when endpoint to reset is not provided

Download

2.1.3: Pre-Production and Production Release

January 7, 2015

Updates:

  • Assorted bug and crashing fixes
  • Fixed Feedback layout on 3.5″ screens under iOS 6
  • Fixed keyboard display overlap issue on iPhone 4 running iOS 6.1.3
  • Uploaded .zip frameworks on S3 are now defined as public artifacts.

Download

2.1.2: Pre-Production and Production Release

December 8, 2014

New Features:

  • Introduced Product environment support

Updates:

  • Improved in-app bug and feedback reporting workflow
  • Fixed horizontal display orientation issue
  • Fixed in-app splash page layout issue

Download

2.0.2: Pre-Production Release Only

April 28, 2014

Updates:

  • Release candidate for Apphance -> Applause SDK

Download

1.9.0: Pre-Production + Production Release

November 19, 2013

New Features:

  • New support for 64 bit ARMv8 architectures

Updates:

  • New PLCrashReporter

Pre-Prod Only:

  • Improved screenshot mechanism

Misc:

  • Included features for upcoming merge of pre-production and production libraries

Download

1.8.20: Pre-Production + Production Release

October 30, 2013 Fixes:

Pre-Prod Only:

  • Fixed issue reporting screenshots in certain cases

Prod Only:

  • Minor bug fixes

Download

1.8.18: Pre-Production + Production Release

October 8, 2013 Fixes:

Pre-Prod Only:

  • Fixed freeze during test cycle selection

Prod Only:

  • Minor bug fixes

Download

1.8.17: Pre-Production + Production Release

September 23, 2013 New Features:

  • The Apphance pre-production library now requires the AssetLibrary framework Apphance now supports attaching screenshots to bug reports from the user’s photo library. This is useful in cases where Apphance is unable to take a screenshot, but the user can still do so using iOS’s screenshot functionality. See the Stating a Session document for more information.

Download

1.8.12: Production Release Only

September 23, 2013 Fixes:

  • Minor bug fixes

Download

1.8.11: Pre-Production + Production Release

August 2, 2013

Fixes:

  • Minor grammatical bugs and issues

Pre-Production Only:

  • Fix for multi touch problem when double-slide bug reporting is enabled
  • Added showReportScreen method to APHLogger

Production Only:

Minor Updates:

Download

1.8.8: Pre-Production + Production Release

April 11, 2013 Fixes:

Pre-Production Only:

  • Fixed focus issue with dialogs that occurred in rare circumstances

Production Only:

  • Fixed logging issue where some logs were ignored
  • Fixed issue where logs were being recorded for all users instead of with special events, like crashes

New Features:

Pre-Production Only:

  • Added spray feature for covering sensitive data in bug report screenshots
  • Added an alternative way to report bugs without shaking the device (double finger slide)

API Update:

  • Changed the API start session method to be more compatible with the Production library. Older code will still work, but developers should update to the newer syntax.

The previous versions used the following syntax:

[APHLogger startNewSessionWithApplicationKey:@"Your-Apphance-Application-Key-Goes-Here" apphanceMode:kAPHApphanceModeQA withUtest:false];

The new version removes the additional options from startNewSessionWithApplicationKey and separates them into different settings values. Now startNewSessionWithApplicationKey takes your API key as its only option.

More information about thew new syntax can be found on the Starting a Session page.

Download

1.8.2: Pre-Production + Production Release

January 24, 2013

Updates:

  • Removed client side requirement for the CFBundleVersionFormat.

Fixes:

  • Fixed focusing problem with uitextfiels after Apphance returns from the problem reporting screen.

Download

1.8.1: Pre-Production Release Only

December 6, 2012 Fixes:

– Fixed issue with using the killswitch feature while the library is in silent mode.

Download

1.8: Pre-Production + Production Release

November 30, 2012

New Features:

  • Added kill-switch feature to the pre-production SDK
  • More detailed crash reports
  • Extended details for crash reasons. For example: -[__NSCFDictionary setObject:forKey:]: attempt to insert nil value (key: MT-User-Id)
  • Stacktraces for all device threads

Fixes:

  • Resolved namespacing bug for the JSON library

Download

1.7.1: Pre-Production + Production Release

October 15, 2012

New Features:

  • Data sent, Data received device statistics are sent to the server (allows devs to investigate 3G/WiFi data usage).

Fixes:

  • Fixed issue with OpenGL screenshots. In rare cases hybrid views mixing OpenGL and UIView caused invalid screenshots to be made
  • The login with default credentials toast changes the orientation along with the device.

Download

1.7: Pre-Production + Production Release

September 19, 2012

Initial version of the iOS ARMv7 pre-production library.

New Features:

  • Support for non integer CFBundleVersions Fixes:
  • Improves support for iOS6

Download