Mobile Apps - Processing Requests

Android Emulator and Physical Device:

This is regarding capturing all the HTTPS requests of the application and finding issues (slow requests and failing requests) from our AI technology, we need help from the dev team in compiling the application with the appvance certificate and Network security configuration XML file to be added to App's manifest XML File.

Reason for this: (We are bound to follow Android's security policies)

Since the introduction of Nougat (API 24) to Android, a number of changes were introduced to how Android handles trusted certificate authorities (CAs). Before, one only needs to install the self-signed SSL .cer file in the emulator/device Security Settings. Then the app will just simply be able to access your secure endpoints (HTTPS) using the global device settings.

The complete blog is here

There are only 3 steps to follow - For the first one, click here to download the pem file, the dev team should do the next 2 steps and send us the apk file.

IOS Simulator and Real Devices:

For Simulator, .app is required.

For Real Device testing, .ipa is required.

We will need access to TestFlight or other invitations in order to test the builds if the dev team compiles the app and uploads them on TestFlight to get the different app build versions to download and install/test the versions.

For Real Devices testing, the app should comply with the UDID of the device that will be used for testing to listen to all the requests and responses.

For instance, if we need to test on iPhones 8, 10, and 11, the UDIDs of those devices should be registered and complied with for us to download and install on those physical devices.

The reason for that is due to Apple’s policies on app distribution for testing, according to the below

Apple Help Xcode

Developer Apple Xcode

Is it compulsory to have UDIDs registered?

if we want to provide our device UDIDs and trust the client (even though we can’t think of any possible harm)

but we believe that the simplest and easiest way to deal with this (in order to avoid having the client register our iPhone’s UDID) is to use TestFlight

The customer simply provides us the link (hopefully it does not expire) and we can test their app without them having to register our UDIDs.