Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -88,14 +88,14 @@ If you use the installation step in the builder, keep the following in mind:

For iOS packaging, install or prepare the following:

* Xcode or Xcode Command Line Tools to bundle and sign the iOS app on macOS
* Xcode or Xcode Command Line Tools to bundle and sign the iOS app on macOS, unless you use the experimental **Build without a Mac** option
* Apple signing assets, including a `.p12` certificate and a `.mobileprovision` profile, if you want to build for a physical device or distribute the app
* A bundle identifier that matches the Apple signing configuration, if you want to build for a physical device or distribute the app

Install full Xcode if you want to use the iOS simulator for testing.

{{% alert color="warning" %}}
iOS packaging for a final signed device build requires macOS. On Windows, you can prepare the portable signing package, but you still need a Mac to generate the final signed IPA.
To generate a signed IPA on Windows, use the experimental **Build without a Mac** option. Without this option, PWA Wrapper on Windows prepares a portable signing package, and you need a Mac to generate the final signed IPA.
{{% /alert %}}

### Steps for iOS on macOS{#steps-on-mac}
Expand Down Expand Up @@ -131,9 +131,19 @@ To generate a signed iOS package on macOS, do the following:

### Steps for iOS on Windows

On Windows, PWA Wrapper can prepare the iOS bundle but not complete the final signing step. The builder produces a portable signing package that can be moved to a Mac.
On Windows, you can sign the iOS app directly with the experimental **Build without a Mac** option. Without this option, the builder produces a portable signing package that you must move to a Mac for the final signing step.

On Windows, use the same steps 1 through 7 as in [Steps for iOS on macOS](#steps-on-mac), then continue as follows:
To generate a signed IPA on Windows without a Mac, use the same steps 1 through 4 as in [Steps for iOS on macOS](#steps-on-mac), then continue as follows:

1. Go to the signing step and create or select an iOS signing configuration.
1. Select **Build without a Mac (experimental)**, then click **OK** in the **Experimental Feature** dialog.
1. Click **Build**.
1. Wait for the build to complete.
1. Open the output directory and retrieve the signed `.ipa`.

For more information, see [Build a Signed IPA Without a Mac](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#build-without-a-mac) in *Sign PWA Wrapper Apps*.

To use the portable signing package instead, use the same steps 1 through 7 as in [Steps for iOS on macOS](#steps-on-mac), then continue as follows:

1. Open the output folder and locate the portable signing ZIP.
1. Copy the portable signing ZIP to a Mac.
Expand All @@ -147,7 +157,7 @@ Keep the following limitations in mind:
* The builder installation step for iOS is available only on macOS hosts
* Copying packaged web resources is currently not supported on iOS, so the wrapped app must load its frontend resources from the deployed Mendix runtime

For platform-specific details about the signing step inside this build flow, see [Sign iOS Apps on macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos) in *Sign PWA Wrapper Apps* for macOS builds and [Prepare iOS Apps on Windows](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows) in *Sign PWA Wrapper Apps* for Windows builds.
For platform-specific details about the signing step inside this build flow, see [Sign iOS Apps on macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos) in *Sign PWA Wrapper Apps* for macOS builds and [Sign iOS Apps on Windows](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows) in *Sign PWA Wrapper Apps* for Windows builds.

## Choosing Permissions and Packaging Options

Expand Down Expand Up @@ -201,6 +211,6 @@ If your app depends on device hardware, validate the final packaged app on repre

After building the wrapper app, continue with the appropriate distribution process for your target platform.

If you still need platform-specific details for the signing step in the build flow, see [Sign Android Apps on Windows and macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos), [Sign iOS Apps on macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos), or [Prepare iOS Apps on Windows](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows).
If you still need platform-specific details for the signing step in the build flow, see [Sign Android Apps on Windows and macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-android-apps-on-windows-and-macos), [Sign iOS Apps on macOS](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#sign-ios-apps-on-macos), or [Sign iOS Apps on Windows](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/sign-pwa-wrapper-apps/#prepare-ios-apps-on-windows).

To understand which capabilities you can use from your Mendix app, see [PWA Wrapper Capabilities](/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/).
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ For an overview of the supported capabilities, see [PWA Wrapper Capabilities](/r

Keep the following build and installation constraints in mind:

* Final iOS signing requires macOS
* Final iOS signing requires macOS, unless you use the experimental **Build without a Mac** option on Windows
* Copying packaged web resources is currently not supported on iOS, so the wrapped iOS app must load frontend resources from the deployed Mendix runtime
* Real-device installation requires signed packages
* If an incompatible or newer build of the app is already installed on a device, it may need to be uninstalled before your current build can be installed
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ To avoid this download in air-gapped environments, pre-populate the Gradle wrapp

## Bundled Binaries Executed Locally

In addition to the runtime downloads above, PWA Wrapper ships the following binaries inside its own extension package. These are not downloaded at build time—they are included in the extension at install time and are invoked as local subprocesses during Android and HarmonyOS build, signing, and packaging steps. They run with the same operating-system privileges as the Studio Pro process.
In addition to the runtime downloads above, PWA Wrapper ships the following binaries inside its own extension package. These are not downloaded at build time—they are included in the extension at install time and are invoked as local subprocesses during Android, HarmonyOS, and iOS build, signing, and packaging steps. They run with the same operating-system privileges as the Studio Pro process.

| Binary | Purpose | Platform |
| --- | --- | --- |
Expand All @@ -44,6 +44,9 @@ In addition to the runtime downloads above, PWA Wrapper ships the following bina
| `aapt2` / `aapt2.exe` | Android Asset Packaging Tool | Android |
| `apksigner.jar` | APK signing | Android |
| `android.jar` | Android SDK stub library used during compilation | Android |
| `adb.exe`, `AdbWinApi.dll`, `AdbWinUsbApi.dll` | Android Debug Bridge, used to install the app on connected devices and emulators | Android (Windows hosts) |
| `zsign.exe` | iOS code signing when **Build without a Mac** is selected | iOS (Windows hosts) |
| `zsign` | iOS code signing when **Build without a Mac** is selected | iOS (macOS hosts) |

These binaries are third-party open-source tools redistributed with the extension. They are not fetched from the network at runtime.

Expand All @@ -53,7 +56,7 @@ When the builder opens, PWA Wrapper inspects the local machine to auto-detect ex

### JDK Discovery

PWA Wrapper needs a Java runtime to execute the build tools listed above. It searches for an installed JDK in the following order and uses the first usable result it finds.
PWA Wrapper needs a Java runtime to execute the Java-based build tools listed above. It searches for an installed JDK in the following order and uses the first usable result it finds.

### macOS Method

Expand Down Expand Up @@ -85,7 +88,8 @@ Consult the following summary for information at a glance:
| Category | What happens | When | Data leaves machine? |
| --- | --- | --- | --- |
| Gradle distribution download | Downloads `gradle-8.9-bin.zip` from `services.gradle.org` | First Android build only | No (download only; no data sent) |
| Bundled binary execution | Runs `apktool.jar`, `bundletool.jar`, `aapt2`, `apksigner.jar`, `android.jar` locally | Every applicable build | No |
| Bundled binary execution | Runs `apktool.jar`, `bundletool.jar`, `aapt2`, `apksigner.jar`, `android.jar`, and `adb.exe` (Windows) locally | Every applicable build | No |
| iOS signing without a Mac | Runs the bundled `zsign` or `zsign.exe` locally; may run a locally installed `openssl` to re-encode a temporary copy of the `.p12` file | Every iOS build with **Build without a Mac** selected | No |
| JDK filesystem scan | Reads `JAVA_HOME`, `/Library/Java/JavaVirtualMachines/`, version manager directories, or Windows Studio Pro settings | When the builder opens | No |
| Studio Pro filesystem scan | Scans `/Applications/` and `~/Applications/` for Studio Pro app bundles (macOS only) | When the builder opens | No |

Expand Down
Loading
Loading