@maccesar/titools 2.2.4 → 2.2.8

package/skills/ti-guides/references/app-distribution.md

@@ -1,10 +1,10 @@
-# App Distribution Guide
+# App distribution guide
 
-Complete guide for distributing Titanium apps to Google Play (Android) and App Store (iOS).
+Guide for distributing Titanium apps to Google Play (Android) and the App Store (iOS).
 
-## Android Distribution
+## Android distribution
 
-### 1. Generate Keystore and Certificate
+### 1. Generate keystore and certificate
 
 Create a keystore for signing your app:
 
@@ -12,14 +12,14 @@ Create a keystore for signing your app:
 keytool -genkeypair -v -keystore android.keystore -alias helloworld -keyalg RSA -sigalg SHA1withRSA -validity 10000
 ```
 
-**Requirements:**
+Requirements:
 - `keyalg`: RSA (required by Google Play)
 - `sigalg`: SHA1withRSA (Android 4.3-) or SHA256withRSA (Android 4.4+)
 - `validity`: 10000 days minimum (~25 years)
 
-**CRITICAL**: Save your keystore password securely. If lost, you cannot release updates.
+Save your keystore password securely. If it is lost, you cannot release updates.
 
-### 2. Verify Keystore
+### 2. Verify keystore
 
 ```bash
 keytool -list -v -keystore android.keystore
@@ -27,64 +27,64 @@ keytool -list -v -keystore android.keystore
 
 ### 3. Build for Google Play
 
-**CLI command:**
+CLI command:
 ```bash
 ti build -p android -T dist-playstore [-K <KEYSTORE_FILE> -P <KEYSTORE_PASSWORD> -L <KEYSTORE_ALIAS> -O <OUTPUT_DIRECTORY>]
 ```
 
-**Example:**
+Example:
 ```bash
 ti build -p android -T dist-playstore -K ~/android.keystore -P secret -L foo -O ./dist/
 ```
 
-**Output files:**
-- `.apk` - Legacy format (still supported)
-- `.aab` - Android App Bundle (preferred, smaller downloads). Requires Titanium 9.0.0+. An AAB file cannot be installed directly on a device; it is a publishing format for Google Play only. Once uploaded, Google Play generates multiple device-specific APKs split by CPU architecture and image density, allowing smaller downloads.
+Output files:
+- `.apk`: legacy format (still supported)
+- `.aab`: Android App Bundle (preferred, smaller downloads). Requires Titanium 9.0.0+. An AAB file cannot be installed directly on a device. After upload, Google Play generates device-specific APKs split by CPU architecture and image density.
 
-### 4. Verify APK Signing
+### 4. Verify APK signing
 
 ```bash
 jarsigner -verify -verbose path/yourapp.apk
 ```
 
-### 5. Deploy to Device for Testing
+### 5. Deploy to device for testing
 
-**Using CLI:**
+Using CLI:
 ```bash
 ti build -p android -T device --device-id "<DEVICE_ID>"
 ```
 
-**Using adb:**
+Using adb:
 ```bash
 adb install -r your_project/build/android/bin/app.apk
 adb uninstall com.your.appid
 ```
 
-**Remote testing:**
-- Host APK on web/Dropbox and email link
+Remote testing:
+- Host the APK on a web server or Dropbox and email a link
 - Use HockeyKit/HockeyApp for beta distribution
 
-### 6. Google Play Submission Requirements
+### 6. Google Play submission requirements
 
-**Required assets:**
-- Minimum 2 screenshots (320x480, 480x800, or 480x854)
+Required assets:
+- At least 2 screenshots (320x480, 480x800, or 480x854)
 - High-res icon (512x512)
 - Title, description (4000 chars max)
 - Promo text (80 chars max)
 - Category and content rating
 - Contact information
 
-**Versioning in tiapp.xml:**
+Versioning in `tiapp.xml`:
 ```xml
 <android xmlns:android="http://schemas.android.com/apk/res/android">
     <manifest android:versionCode="2" android:versionName="1.0.1"/>
 </android>
 ```
 
-- `versionCode`: Must be a 32-bit integer (whole number), must increment for each update. Cannot be a floating point number.
-- `versionName`: String, any format you prefer
+- `versionCode`: must be a 32-bit integer and increment for each update. No floating point values.
+- `versionName`: string in any format you choose
 
-### 7. SD Card Installation
+### 7. SD card installation
 
 ```xml
 <android xmlns:android="http://schemas.android.com/apk/res/android">
@@ -96,45 +96,45 @@ Values: `preferExternal`, `auto`, `internalOnly`
 
 ---
 
-## iOS Distribution
+## iOS distribution
 
-### 1. Distribution Types
+### 1. Distribution types
 
-- **App Store**: Public distribution via App Store (formerly known as iTunes Connect, now App Store Connect)
-- **Ad Hoc**: Limited testing (max 100 devices per year; devices cannot be removed once registered, so use care when registering)
-- **In House**: Enterprise distribution for employees (Enterprise program only)
+- App Store: public distribution via App Store (formerly iTunes Connect, now App Store Connect)
+- Ad Hoc: limited testing (max 100 devices per year; devices cannot be removed once registered, so use care when registering)
+- In House: enterprise distribution for employees (Enterprise program only)
 
-### 2. Create Distribution Certificate
+### 2. Create distribution certificate
 
-**Certificate types:**
-- **Development certificate**: Each developer on the team can have their own, used for building test versions.
-- **Distribution certificate**: A single certificate for the entire team. Only the Team Agent (the account owner who oversees final distribution) can create it. This ensures developers cannot publish the final app without authorization.
+Certificate types:
+- Development certificate: each developer can have their own, used for test builds.
+- Distribution certificate: a single certificate for the entire team. Only the Team Agent (account owner) can create it.
 
-**Steps:**
-1. Log in to [Apple Developer Member Center](https://developer.apple.com/membercenter/) as Team Agent or Admin
-2. Go to **Certificates, Identifiers & Profiles** > **Certificates**
-3. Click **+** > **App Store and Ad Hoc**
-4. Create a CSR (Certificate Signing Request) in Keychain Access
-5. Upload CSR and generate certificate
-6. Download and install the `.cer` file
-7. **CRITICAL**: Export private key as `.p12` file (File > Export Items)
+Steps:
+1. Log in to Apple Developer Member Center as Team Agent or Admin.
+2. Go to Certificates, Identifiers & Profiles, then Certificates.
+3. Click +, then choose App Store and Ad Hoc.
+4. Create a CSR (Certificate Signing Request) in Keychain Access.
+5. Upload the CSR and generate the certificate.
+6. Download and install the `.cer` file.
+7. Export the private key as a `.p12` file (File > Export Items).
 
-### 3. Create Distribution Provisioning Profile
+### 3. Create distribution provisioning profile
 
-1. In [Member Center](https://developer.apple.com/membercenter/), go to **Provisioning Profiles**
-2. Click **+** > select distribution type
-3. Select App ID
-4. Select distribution certificate
-5. For Ad Hoc: select test devices
-6. Name profile (include "distribution" or "ad hoc")
-7. Download `.mobileprovision` and install (drag to Xcode icon)
+1. In Member Center, go to Provisioning Profiles.
+2. Click + and select the distribution type.
+3. Select an App ID.
+4. Select the distribution certificate.
+5. For Ad Hoc, select test devices.
+6. Name the profile (include "distribution" or "ad hoc").
+7. Download the `.mobileprovision` file and install it (drag to Xcode).
 
 ### 4. Create App ID on App Store Connect
 
-App Store Connect (formerly iTunes Connect) is the app distribution management portal.
+App Store Connect is the portal for app distribution management.
 
-1. Log in to App Store Connect
-2. **Manage Your Apps** > **Add New App**
+1. Log in to App Store Connect.
+2. Go to Manage Your Apps, then Add New App.
 3. Provide:
    - App name
    - SKU number (unique ID)
@@ -153,26 +153,26 @@ App Store Connect (formerly iTunes Connect) is the app distribution management p
      - iPhone (3.5"): 960x640, 960x600, 640x960, or 640x920
      - iPhone (4"): 1136x640, 1136x600, 640x1136, or 640x1096
      - iPad: 1024x768, 1024x748, 768x1024, 768x1004, 2048x1536, 2048x1496, 1536x2048, or 1536x2008
-5. Click **Ready to Upload Binary**
+5. Click Ready to Upload Binary.
 
-### 5. Build and Package
+### 5. Build and package
 
-**CLI command - Ad Hoc:**
+CLI command - Ad Hoc:
 ```bash
 ti build -p ios -T dist-adhoc [-R <DISTRIBUTION_CERTIFICATE_NAME> -P <PROVISIONING_PROFILE_UUID> -O <OUTPUT_DIRECTORY>]
 ```
 
-**Example:**
+Example:
 ```bash
 ti build -p ios -T dist-adhoc -R "Pseudo, Inc." -P "FFFFFFFF-EEEE-DDDD-CCCC-BBBBBBBBBBBB" -O ./dist/
 ```
 
-**CLI command - App Store:**
+CLI command - App Store:
 ```bash
 ti build -p ios -T dist-appstore [-R <DISTRIBUTION_CERTIFICATE_NAME> -P <PROVISIONING_PROFILE_UUID>]
 ```
 
-**Example:**
+Example:
 ```bash
 ti build -p ios -T dist-appstore -R "Pseudo, Inc." -P "AAAAAAAA-0000-9999-8888-777777777777"
 ```
@@ -181,116 +181,20 @@ The CLI installs the package to Xcode's Organizer.
 
 ### 6. Upload to App Store Connect
 
-1. Open Xcode > **Window** > **Organizer**
-2. Select your app archive
-3. Click **Verify** (validates against App Store Connect app definition)
-4. Click **Submit** (uploads app)
-5. Status changes to **Waiting for Review**
+1. Open Xcode, then Window, then Organizer.
+2. Select your app archive.
+3. Click Verify to validate against the App Store Connect app definition.
+4. Click Submit to upload.
+5. Status changes to Waiting for Review.
 
-### 7. Ad Hoc Distribution
+### 7. Ad Hoc distribution
 
 Testers need:
 - The `.mobileprovision` file installed on their device
 - The `.ipa` package file
 
-**Installation method:**
-1. Connect device to Mac
-2. Open Xcode > **Window** > **Devices**
-3. Select device > **Installed Apps** > **+**
-4. Select IPA file
-
-### 8. App Thinning (iOS)
-
-App Thinning optimizes your application by reducing its installed size on devices.
-
-**Slicing (Asset Catalog):**
-- Installs only the assets needed for the specific device (e.g., @2x images for non-Plus iPhones, @3x for Plus/Pro models)
-- When enabled, Titanium automatically adds all PNG and JPEG images to an Asset Catalog
-- Images with matching suffixes (@2x, @3x, etc.) are grouped into one imageset
-- **Important limitation**: When slicing is enabled, you cannot access images from the filesystem using `Ti.Filesystem` or path/URL-based access. Only use image names (without path) in ImageView and similar APIs.
-- Icons and launch images are always added to the Asset Catalog
-
-**Enable slicing in tiapp.xml:**
-```xml
-<ti:app>
-  <ios>
-    <use-app-thinning>true</use-app-thinning>
-  </ios>
-</ti:app>
-```
-
-By default, slicing is disabled.
-
-**Bitcode:**
-- Submits partially compiled code to App Store Connect, which then optimizes and compiles for specific architectures
-- Currently disabled in Titanium because all frameworks (including third-party modules) must have bitcode enabled
-
-**On-Demand Resources:**
-- Resources tagged into groups, stored on Apple servers, downloaded when needed by the app
-- iOS purges on-demand resources when device disk space is low
-- Titanium SDK does not currently provide a way to tag on-demand resources
-
-### 9. App Store Requirements
-
-Apple's guidelines include:
-- Apps must be useful, well-designed, and error-free
-- No downloading/executing code
-- You must own all copyrights and trademarks
-- No hidden features or non-public APIs
-- [Full guidelines](http://developer.apple.com/appstore/resources/approval/guidelines.html)
-
----
-
-## Device Deployment Testing
-
-### Android Device Setup
-
-1. Enable **Developer options** (tap **Build number** 7 times in **About**)
-2. Enable **USB debugging** in **Developer options**
-3. Enable **Unknown sources** in **Security**
-4. Connect via USB (use data cable, not power-only)
-5. Allow USB debugging when prompted
-
-**Windows only**: Install [OEM USB drivers](http://developer.android.com/sdk/oem-usb.html)
-
-### iOS Device Setup
-
-Requires development certificate and provisioning profile. See [Deploying to iOS devices](#ios-distribution).
-
----
-
-## Troubleshooting
-
-### Android: Device Not Recognized
-
-```bash
-adb devices        # Check connected devices
-adb kill-server    # Restart adb
-adb start-server
-adb devices        # Verify
-```
-
-### Android: Check Platform Compatibility
-
-```bash
-ti info -p android
-```
-
-### iOS: Mavericks Permission Issues
-
-Grant CLI access in **System Preferences** > **Security & Privacy** > **Privacy**
-
-### General: Clean Build Folder
-
-```bash
-ti clean [-p <PLATFORM>]
-```
-
----
-
-## References
-
-- [Google Play Developer Policies](http://play.google.com/about/developer-content-policy.html)
-- [Google Play Graphic Assets](http://support.google.com/googleplay/android-developer/bin/answer.py?hl=en&answer=1078870)
-- [iTunes Connect Developer Guide](http://developer.apple.com/library/mac/#documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/)
-- [iOS App Store Review Guidelines](http://developer.apple.com/appstore/resources/approval/guidelines.html)
+Installation method:
+1. Connect the device to a Mac.
+2. Open Xcode, then Window, then Devices.
+3. Select the device, then Installed Apps, then +.
+4. Select the IPA file.