FREQUENTLY ASKED QUESTIONS (FAQ PLATFORM)

The issue is that the testers` iOS devices are not provisioned (according to Apple’s requirement).

In order for any invited member to be able to join the project, their device must be provisioned in advance.

Please log in your account, choose the required build and go to ‘Devices’ section, which is in the left sidebar menu, and make sure that the required devices are provisioned.

• Check that there is enough storage place on your iOS device to download the app;
• Make sure you have stable Internet connection;
• Сheck that your AdHoc distribution provisioning profile is not corrupted as the device can experience the issue with it;
• Make sure the build is signed correctly.
• Reset the device and make sure it is not causing a conflict for OTA distribution;
• Make sure that ‘Build Active Architecture’ is set to ‘off’ when compiling a build file;
• Make sure your device meets the minimum iOS requirements for the app;
• Try alternative mobile browser.

Once the Ubertesters hub installation is complete on your iOS device, you can notice the two Ubertesters icons – the white icon and the black one.

The white icon ico-white-uber is the Ubertesters hub itself, that is used for the OTA distribution of your builds.

The black icon ico-black-uber is just a bookmark to the Ubertesters app installation web page. You can delete it when the hub is installed already, as it will not be required further.

‘Untrusted Enterprise Developer’ is the pop-up which is displayed when you are trying to install any custom enterprise app on your iOS 9 device.

You will be asked to ‘trust’ the Enterprise developer certificate during the first time installation of the Ubertesters hub.

It is possible to ‘trust’ the certificate in the following way:

Go to Settings > General > Profiles or Profiles & Device Management;

Select the developer certificate in the “ENTERPRISE APP” section;

Press “Trust … Apps on this iPhone”;

Select “Trust”.

Ubertesters app uses http requests, but Apple restricts http requests on the devices with iOS 9 and later. To solve the issue with the lock screen, please add the following to your Info.plist file:

<key>NSAppTransportSecurity</key>
<dict>
<key>NSAllowsArbitraryLoads</key><true/>
</dict>


This error sometimes happens for all Android devices if you open the file from ‘Downloads’.

Please access File Manager (you can install ES File Explorer File Manager, for example) open the file from there.

The existing SDK integrated with your App allows you to track and manage the complete mobile beta testing phase during the pre-production phase. When you submit your app to the store (production) you will need to disable or remove our SDK.

Android

Ubertesters SDK is used for beta-testing. When you send your app to GooglePlay, it is required to make sure Ubertesters SDK is disabled. This can be done in two ways:

• Comment the initializer method used for SDK integration if the app size is not important;
• Remove the frameworks used for integration with SDK and all the data added to AndroidManifest.xml file including ‘ubertesters_organization_token’ and permissions if you would like to reduce the app size.

iOS

Ubertesters SDK is used for beta-testing. When you send your app to AppStore, it is required to make sure Ubertesters SDK is disabled. This can be done in two ways:

• Comment the initializer method used for SDK integration if the app size is not important;
• Remove the frameworks used for integration with SDK and all the data added to Info.plist file, including ubertesters_organization_token and initializer method if you would like to reduce the app size.

Ubertesters SDK is created for beta-testing and does not support production mode. It is impossible to use it on production, please delete SDK before submitting the app to AppStore or PlayMarket.

Yes, you can choose the “Shake” option when you integrate your app with our SDK. The button will be removed, but still you will be able to report the bugs and take screenshots simply by shaking your device. In order to implement it simply use our latest SDK and also see the integration instructions in order to fully implement it.

SDK integration is not compulsory. You can upload the build without SDK integration. Please note that in this case the testers will not be able to report issues or crashes from their mobile device.