Skip to content

Commit

Permalink
Network capture ssl disclaimer (#2972)
Browse files Browse the repository at this point in the history
* Added more info regarding network capture and SSL pinning on Android

* Better formatting for readibility

* Added relevant links to Apple and Google docs where applies
  • Loading branch information
diegoperini authored Oct 7, 2024
1 parent 497831e commit e3a7024
Showing 1 changed file with 9 additions and 6 deletions.
15 changes: 9 additions & 6 deletions docs/mobile-apps/features/network-capture.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,10 +55,15 @@ Now you can start your live or automated testing session. Your network logs will

:::note Android Only

For Android applications, a minor modification in the manifest is necessary to disable SSL pinning and accept our own certificate by your application.
In addition, we require the debug version of the application. If your application includes SecureSDK, please ensure the repackaging prevention feature is disabled.
For Android applications, a minor modification in the manifest is necessary to make your app trust our proxy certificate. We'll do this for you automatically when you upload the app to the platform.

We require a debug build ([iOS](https://developer.apple.com/documentation/xcode/customizing-the-build-schemes-for-a-project)/[Android](https://developer.android.com/build/build-variants)) of the application and if your app includes a Secure SDK, please ensure the repackaging prevention feature is disabled.
:::

:::note All platforms

If your app utilizes 3rd party SDKs for networking or Secure SDKs that support network protection, make sure all runtime checks for SSL pinning ([iOS](https://developer.apple.com/news/?id=g9ejcf8y)/[Android](https://developer.android.com/privacy-and-security/security-ssl)) are also disabled otherwise your app will accidentally mark Sauce's proxy as untrustworthy and internet access for HTTPS will be limited.

For tests that run on Android devices, enabling network capture may cause issues in third-party SDKs due to SSL pinning.
:::

### Automated Testing
Expand Down Expand Up @@ -259,9 +264,7 @@ Our network capture feature depends on the fact that these classes are not obfus

#### iOS

- Network capture works if the app uses [NSURLSession](https://developer.apple.com/documentation/foundation/nsurlsession) or a library (like [Alamofire](https://github.com/Alamofire/Alamofire) or [AFNetworking](https://github.com/AFNetworking/AFNetworking)) that uses NSURLSession inside.
- Calls made by [NSURLConnection](https://developer.apple.com/documentation/foundation/nsurlconnection) (deprecated by Apple), will not be captured.

- Network capture works if the app uses [NSURLSession](https://developer.apple.com/documentation/foundation/nsurlsession) or a library (like [Alamofire](https://github.com/Alamofire/Alamofire) or [AFNetworking](https://github.com/AFNetworking/AFNetworking)) that uses NSURLSession internally.

## More Information

Expand Down

0 comments on commit e3a7024

Please sign in to comment.