Skip to content

41 ‐ Test the builds

Jump to bottom
Pierre-Yves Lapersonne edited this page Dec 5, 2024 · 3 revisions

You can test some specific builds.

TestFlight builds

The alpha (i.e. on-demand manually-triggered builds), beta (i.e. automated nightly builds) and production (i.e. manually-triggered builds) are available on TestFlight.

You need to be added in the TestFlight dedicated group to get the builds you want (alpha-team, beta-team or public-access).

Only development team can trigger and manage such builds.

Of course, you will need an Apple device like an iPhone or an iPad, with TestFlight installed on it.

Contact Pierre-Yves Lapersonne or Ludovic Pinel to get access or to ask alpha builds on a specific GitHub branch.

Local builds

On simulator

You can also build locally on simulators. You will have to use a macOS–powered computer supporting at least Xcode 16 (i.e. macOS Sonoma 14.5 or later). Then the suitable version of Xcode must be downloaded (see the which one in the README) with all the needed SDK (we support iOS 15 at least). After that, download the source code of the project using GitHub (clone or direct download if you want). Open the Showcase.xcworkspace file using Xcode (located in Showcase folder), then build on a simulator.

On device

If you want to build on your own devices, you have two solutions.

Use the current setup

  1. Create your Apple developer account if you don't have one
  2. Ask one of the Apple team admin to add you (see below)
  3. Register your device in the team ([to be listed there}(https://developer.apple.com/account/resources/devices/list))

You will be then able to build in debug mode on your device.

Use your setup

  1. Create your Apple developer account if you don't have one
  2. Have an Apple team
  3. Assign your team as the Team section for the signing and capabilities section in Xcode project
  4. Use your own bundle identifier
  5. Enjoy the certificates process to have the mobile provisoning profiles
flowchart TD
%% Nodes
    A("Go to Apple Developer website (developer.apple.com)")
    B("Create if needed your developer account")
    C("Register your devices in your Team")
    D("If you don't have one, create an Apple Development certificate for you.
    You may need to ask for a Certificate Signing Request associated to your certificate creation request.
    You will then get the public key only file (.pub) or the file with public and private keys (.p12)")
    E("Download and install in your keychain your certificate")
    F("Create a new App ID with the good Apple team and the bundle identifier you want.
    No need to choose capabilities today for OUDS iOS")
    G("Create a new provisioning profile for iOS App Development using the App ID, your development certificate and the registered devices")
    H("Download and install in your keychain the provisioning profile")

%% Edge connections between nodes
    A --> B --> C --> D --> E --> F --> G --> H

%% Individual node styling.
    %% Purple
    style C color:#FFFFFF, fill:#AA00FF, stroke:#AA00FF

    %% Blue
    style D color:#FFFFFF, stroke:#2962FF, fill:#2962FF

    %% Green
    style F color:#FFFFFF, stroke:#00C853, fill:#00C853
    
    %% Red
    style G color:#FFFFFF, stroke:#FF1600, fill:#FF1600
Loading

You can create any bundle identifiers you need and any developers certificates. The bundler identifier and the certificates will be used to forge the mobile provisioning profiles. You can use wildcards (*) if you are sure no capabilities or entitlements will be used but that's not the case for OUDS.

If you wan't to put things in production beware, Apple limits you with three certifcates only for production.

For debug mode, automatic signing can suit your needs overall if you are several developers. Otherwis you can create the provisioning profile with the App ID (category iOS App Development) and the develoment certificate.

For release mode, you will need profiles with distribution certificate and the App ID (category App Store Connect).

Current setup details

The current build setup is this one:

  • Automatic signing for debug builds but not for release builds
  • Bundle identifier com.orange.ouds.demoapp-debug for debug and com.orange.ouds.demoapp for release builds
  • France Telecom (MG2LSJNJB6) Apple team (which is not the official Orange team for information)

There are several Apple team admins, and some of them are OUDS iOS maintainers. Contact them using their Orange email address.

  • Pierre-Yves Lapersonne
  • Ludovic Pinel
Clone this wiki locally