@maccesar/titools 2.10.1 → 3.1.0

package/skills/ti-guides/SKILL.md

@@ -1,75 +0,0 @@
----
-name: ti-guides
-description: "Titanium SDK official fundamentals and configuration guide. Use when working with, reviewing, analyzing, or examining Titanium projects, Hyperloop native access, app distribution (App Store/Google Play), tiapp.xml configuration, CLI commands, memory management, bridge optimization, CommonJS modules, SQLite transactions, or coding standards. AUTO-DETECT: If tiapp.xml exists, invoke this skill for any project configuration, build, or deployment question. Covers SDK versions, platform compatibility, and tiapp.xml settings that are unique to Titanium."
-argument-hint: "[topic]"
-allowed-tools: Read, Grep, Glob, Edit, Write, Bash(node *)
----
-
-# Titanium SDK guide expert
-
-Use this skill to keep Titanium projects aligned with TiDev standards for stability, performance, and cross-platform behavior.
-
-## Project detection
-
-> **️ℹ️ Auto-detects Titanium projects**
-> This skill auto-detects Titanium projects. No manual command is needed.
->
-> Titanium project indicator:
-> - `tiapp.xml` file (definitive indicator)
->
-> Applies to both:
-> - Alloy projects (`app/` folder)
-> - Classic projects (`Resources/` folder)
->
-> Behavior:
-> - If a Titanium project is detected, provide official Titanium SDK guidance, memory management best practices, and app distribution help.
-> - If not detected, say this skill is only for Titanium projects.
-
-## Core workflow
-
-1. Validate the project follows a modular pattern (CommonJS or Alloy).
-2. Ensure global listeners are removed and heavy objects are nulled during cleanup.
-3. Cache frequently accessed native properties to reduce bridge crossings.
-4. Use Hyperloop for specialized native functionality and handle casting and threading correctly.
-5. Use transactions for database work and manage image memory footprints.
-
-## Procedural rules
-
-- Always remove `Ti.App` and `Ti.Geolocation` listeners during controller cleanup.
-- Do not access `Ti.Platform` or `Ti.DisplayCaps` inside loops. Store values in local variables.
-- Concatenate Hyperloop selectors accurately (for example, `addAttribute:value:range:` -> `addAttributeValueRange`).
-- Close resultsets and database handles after every transaction block.
-
-## Reference guides
-
-- Hello World (references/hello-world.md): project creation, structure, and getting started with Alloy or Classic Titanium.
-- JavaScript Primer (references/javascript-primer.md): JavaScript fundamentals, learning resources, best practices, and ES6+ features.
-- Application Frameworks (references/application-frameworks.md): Alloy vs Classic Titanium, architectural patterns, and framework selection.
-- Coding Best Practices (references/coding-best-practices.md): memory leaks, bridge efficiency, event naming, security, and lazy loading.
-- CommonJS Advanced (references/commonjs-advanced.md): stateful modules, caching, ES6+ support, and antipatterns.
-- Advanced Data & Images (references/advanced-data-and-images.md): SQLite transactions and image memory optimization.
-- Hyperloop Native Access (references/hyperloop-native-access.md): Objective-C/Swift/Java syntax, casting, debugging, XIB/Storyboards.
-- Style & Conventions (references/style-and-conventions.md): naming standards and formatting rules.
-- Reserved Words (references/reserved-words.md): ECMAScript, iOS, and Alloy reserved keywords to avoid.
-- Android Manifest (references/android-manifest.md): custom AndroidManifest.xml, permissions, and manifest merge.
-- App Distribution (references/app-distribution.md): Google Play (APK/AAB), App Store (IPA), certificates, provisioning, and deployment.
-- tiapp.xml Configuration (references/tiapp-config.md): complete reference for tiapp.xml and timodule.xml, including all elements, properties, and platform-specific settings.
-- CLI Reference (references/cli-reference.md): Titanium CLI commands, options, tasks, configuration, and build processes.
-- Resources (references/resources.md): community support, modules, sample code, Slack, and learning materials.
-
-## Related skills
-
-For tasks beyond SDK fundamentals, use these complementary skills:
-
-| Task | Use this skill |
-| --- | --- |
-| Project architecture, services, patterns | `ti-expert` |
-| Native features (location, push, media) | `ti-howtos` |
-| Alloy CLI, configuration, debugging | `alloy-howtos` |
-| UI layouts, ListViews, gestures | `ti-ui` |
-
-## Response format
-
-1. Technical recommendation: cite the specific TiDev best practice.
-2. Optimized implementation: provide modern ES6+ code without semicolons.
-3. Rationale: briefly explain the performance or memory impact.

package/skills/ti-guides/references/advanced-data-and-images.md

@@ -1,155 +0,0 @@
-# Advanced database and image best practices
-
-## 1. SQLite optimization
-
-- Close result sets and the database after each operation to avoid locks and memory growth. SQLite allows one writer at a time, and leaving a connection open after `INSERT` or `UPDATE` can trigger `DatabaseObjectNotClosed` on the next write.
-- Use transactions for batch inserts. If any statement fails, SQLite rolls back the entire batch.
-  ```javascript
-  const db = Ti.Database.open('myDatabase');
-  db.execute('BEGIN');
-  for (const item of playlist) {
-    db.execute('INSERT INTO albums (disc, artist, rating) VALUES (?, ?, ?)', item.disc, item.artist, item.rating);
-  }
-  db.execute('COMMIT');
-  db.close();
-  ```
-- Do not ship large pre-populated databases. Ship a small skeleton and download data on first boot to reduce IPA/APK size. The `Resources` directory is read-only, so installing a database copies it to `applicationDataDirectory`, which creates two copies on the device.
-  - Android note: in Android 2.2 and earlier, the installer could not uncompress assets over 1 MB. One workaround was to rename the file with a `.mp3` extension to prevent `aapt` compression.
-  - Pattern for downloading a replacement database on first boot:
-  ```javascript
-  const updateDatabase = (newData) => {
-    // delete existing content and rehydrate from downloaded JSON
-  }
-  downloadButton.addEventListener('click', () => {
-    const client = Ti.Network.createHTTPClient({
-      timeout: 10000,
-      onload() {
-        updateDatabase(this.responseData)
-        Ti.UI.createAlertDialog({ title: 'Info', message: 'Database installed' }).show()
-      },
-      onerror(e) {
-        Ti.UI.createAlertDialog({ title: 'Error', message: e.error }).show()
-      }
-    })
-    client.open('GET', 'https://example.com/data.json')
-    client.send()
-  })
-  ```
-
-### Database version management
-
-Store a version number in your database so you can detect upgrades and run migrations. If you do not have a version table, use `PRAGMA TABLE_INFO` to detect column presence:
-
-```javascript
-const addColumn = (dbname, tblName, newFieldName, colSpec) => {
-  const db = Ti.Database.open(dbname);
-  let fieldExists = false;
-  const resultSet = db.execute(`PRAGMA TABLE_INFO(${tblName})`);
-  while (resultSet.isValidRow()) {
-    if (resultSet.field(1) === newFieldName) {
-      fieldExists = true;
-    }
-    resultSet.next();
-  }
-  resultSet.close();
-  if (!fieldExists) {
-    db.execute(`ALTER TABLE ${tblName} ADD COLUMN ${newFieldName} ${colSpec}`);
-  }
-  db.close();
-};
-```
-
----
-
-## 2. Image format selection
-
-Choose the right format for each use case:
-
-| Format | Compression           | Best for                       | Avoid for                                                          |
-| ------ | --------------------- | ------------------------------ | ------------------------------------------------------------------ |
-| PNG    | Lossless              | Icons, text, line art, buttons | Photos (large files)                                               |
-| JPG    | Lossy                 | Photographs                    | Text, icons, line drawings (artifacts)                             |
-| GIF    | Lossless (256 colors) | Rare cases                     | Most cases (limited colors, animated GIF not supported everywhere) |
-
-For flip-book animations, use `ImageView.images` with an array of PNG or optimized JPG files instead of animated GIFs.
-
----
-
-## 3. Image memory management
-
-- A JPG is small on disk but expands to `width * height * 3 bytes` in RAM. Each pixel uses 24 bits (8 bits per R/G/B channel).
-  - Example: `(640 × 480 × 3) / 1024 = 900 KB` in memory for a single image
-  - Device RAM available to your app can be as low as 12 MB, shared with your code and the Titanium framework
-- Unloading:
-  - `view.remove(imageView)` removes it from the view hierarchy and lets the OS free memory
-  - `imageView = null` releases the native proxy object
-- Resizing: resize images to their display dimensions using `imageAsResized` or `imageAsCropped` (both on `Ti.Blob`) before setting the `image` property. Do not display a 1024×768 image on a 640×480 screen.
-- Placeholder: set `defaultImage` on ImageView to show a local placeholder while a remote image downloads:
-  ```javascript
-  const imageView = Ti.UI.createImageView({
-    image: 'https://example.com/photo.jpg',
-    defaultImage: '/images/placeholder.png',
-    width: 300,
-    height: 200
-  });
-  ```
-
----
-
-## 4. Image optimization tools
-
-Resize and compress images before including them in your app to reduce IPA/APK size and network usage.
-
-| Platform            | File types    | Tool        |
-| ------------------- | ------------- | ----------- |
-| Mac                 | PNG, JPG, GIF | ImageOptim  |
-| Mac, Windows, Linux | PNG, JPG, GIF | ImageMagick |
-| Windows/DOS         | PNG           | PNGCrush    |
-| Windows             | JPG           | Nikkho      |
-
----
-
-## 5. Caching remote images
-
-Remote images are cached automatically on iOS, Android, and Windows.
-
-Platform differences:
-- Android: cache limited to 25 MB, persists for the lifetime of the app (while installed)
-- iOS: cache size not fixed, cleared by iOS when the device needs storage
-
-To manually clean the cache, delete files in `applicationCacheDirectory`.
-
-Android 6+ requirement: call `Ti.Filesystem.requestStoragePermissions()` before loading remote images.
-
-### Manual caching utility
-
-For critical assets, cache manually in `applicationDataDirectory` for more predictable behavior:
-
-```javascript
-const CacheUtils = {
-  getExtension: (fn) => {
-    const match = /(?:\.([^.]+))?$/.exec(fn);
-    return match[1] || '';
-  },
-
-  createCachedImageView: (options) => {
-    const md5 = Ti.Utils.md5HexDigest(options.image) + CacheUtils.getExtension(options.image);
-    const savedFile = Ti.Filesystem.getFile(Ti.Filesystem.applicationDataDirectory, md5);
-
-    if (savedFile.exists()) {
-      options.image = savedFile;
-      return Ti.UI.createImageView(options);
-    }
-
-    const imageView = Ti.UI.createImageView(options);
-    const saveImage = () => {
-      imageView.removeEventListener('load', saveImage);
-      savedFile.write(
-        Ti.UI.createImageView({ image: imageView.image, width: Ti.UI.FILL, height: Ti.UI.FILL }).toImage()
-      );
-    };
-    imageView.addEventListener('load', saveImage);
-    return imageView;
-  }
-};
-```

package/skills/ti-guides/references/android-manifest.md

@@ -1,97 +0,0 @@
-# Custom AndroidManifest.xml
-
-For most Android manifest settings, use `tiapp.xml`. Only create a custom manifest when you really need it.
-
-## Preferred method: tiapp.xml
-
-Add manifest entries in `tiapp.xml` inside the `<android>` section:
-
-```xml
-<android xmlns:android="http://schemas.android.com/apk/res/android">
-    <manifest>
-        <!-- SDK version -->
-        <uses-sdk android:minSdkVersion="21" android:targetSdkVersion="34" />
-
-        <!-- Screen support -->
-        <supports-screens
-            android:smallScreens="false"
-            android:normalScreens="true"
-            android:largeScreens="true"
-            android:xlargeScreens="true"
-        />
-
-        <!-- Permissions -->
-        <uses-permission android:name="android.permission.CAMERA" />
-        <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
-
-        <!-- Application attributes (merged, not replaced) -->
-        <application android:debuggable="true" />
-    </manifest>
-</android>
-```
-
-## How merging works
-
-- Most elements are replaced by your entry.
-- The `<application>` element is merged additively by attribute.
-- Activities and services are added to existing ones.
-
-## Custom manifest (rare cases)
-
-If you need full control, create `platform/android/AndroidManifest.xml`:
-
-```
-MyApp/
-├── app/
-├── platform/
-│   └── android/
-│       └── AndroidManifest.xml  # Custom manifest
-└── tiapp.xml
-```
-
-Warning: you must maintain this file manually through SDK updates.
-
-## Common use cases
-
-### Camera permission
-```xml
-<uses-permission android:name="android.permission.CAMERA" />
-```
-
-### Hardware requirements
-```xml
-<uses-feature android:name="android.hardware.camera" android:required="false" />
-```
-
-### Launch mode
-```xml
-<application android:launchMode="singleTask" />
-```
-
-### Deep links
-```xml
-<intent-filter>
-    <action android:name="android.intent.action.VIEW" />
-    <category android:name="android.intent.category.DEFAULT" />
-    <category android:name="android.intent.category.BROWSABLE" />
-    <data android:scheme="myapp" android:host="path" />
-</intent-filter>
-```
-
-## Debugging
-
-To see the generated manifest:
-```bash
-ti build -p android
-# Check: build/android/AndroidManifest.xml.gen
-```
-
-## Enable manifest merge (CLI 7.0+)
-
-If you use a custom manifest, enable merge in `tiapp.xml`:
-
-```bash
-ti config android.mergeCustomAndroidManifest true
-```
-
-This merges your custom manifest with the generated one instead of replacing it.

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

@@ -1,373 +0,0 @@
-# App distribution guide
-
-Guide for distributing Titanium apps to Google Play (Android) and the App Store (iOS).
-
-## Android distribution
-
-### 1. Generate keystore and certificate
-
-Create a keystore for signing your app:
-
-```bash
-keytool -genkeypair -v -keystore android.keystore -alias helloworld -keyalg RSA -sigalg SHA1withRSA -validity 10000
-```
-
-Requirements:
-- `keyalg`: RSA (required by Google Play)
-- `sigalg`: SHA1withRSA (Android 4.3-) or SHA256withRSA (Android 4.4+)
-- `validity`: 10000 days minimum (~25 years)
-
-Save your keystore password securely. If it is lost, you cannot release updates.
-
-### 2. Verify keystore
-
-```bash
-keytool -list -v -keystore android.keystore
-```
-
-### 3. Build for Google Play
-
-CLI command:
-```bash
-ti build -p android -T dist-playstore [-K <KEYSTORE_FILE> -P <KEYSTORE_PASSWORD> -L <KEYSTORE_ALIAS> -O <OUTPUT_DIRECTORY>]
-```
-
-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. After upload, Google Play generates device-specific APKs split by CPU architecture and image density.
-
-### 4. Verify APK signing
-
-```bash
-jarsigner -verify -verbose path/yourapp.apk
-```
-
-### 5. Deploy to device for testing
-
-Using CLI:
-```bash
-ti build -p android -T device --device-id "<DEVICE_ID>"
-```
-
-Using adb:
-```bash
-adb install -r your_project/build/android/bin/app.apk
-adb uninstall com.your.appid
-```
-
-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
-
-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`:
-```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 and increment for each update. No floating point values.
-- `versionName`: string in any format you choose
-
-### 7. SD card installation
-
-```xml
-<android xmlns:android="http://schemas.android.com/apk/res/android">
-   <manifest android:installLocation="preferExternal"/>
-</android>
-```
-
-Values: `preferExternal`, `auto`, `internalOnly`
-
----
-
-## iOS distribution
-
-### 1. Distribution types
-
-- 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
-
-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 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
-
-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 is the portal for app distribution management.
-
-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)
-   - Bundle ID (must match App ID from Developer Portal)
-4. Configure:
-   - Availability date
-   - Price tier
-   - Version number
-   - Description (4000 chars max)
-   - Category, keywords (100 chars max)
-   - Copyright
-   - Support URL
-   - Rating info
-   - High-res icon: 1024x1024, 72 DPI, RGB, flat artwork
-   - Screenshots:
-     - 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. Build and package
-
-CLI command - Ad Hoc:
-```bash
-ti build -p ios -T dist-adhoc [-R <DISTRIBUTION_CERTIFICATE_NAME> -P <PROVISIONING_PROFILE_UUID> -O <OUTPUT_DIRECTORY>]
-```
-
-Example:
-```bash
-ti build -p ios -T dist-adhoc -R "Pseudo, Inc." -P "FFFFFFFF-EEEE-DDDD-CCCC-BBBBBBBBBBBB" -O ./dist/
-```
-
-CLI command - App Store:
-```bash
-ti build -p ios -T dist-appstore [-R <DISTRIBUTION_CERTIFICATE_NAME> -P <PROVISIONING_PROFILE_UUID>]
-```
-
-Example:
-```bash
-ti build -p ios -T dist-appstore -R "Pseudo, Inc." -P "AAAAAAAA-0000-9999-8888-777777777777"
-```
-
-The CLI installs the package to Xcode's Organizer.
-
-### 6. Upload to App Store Connect
-
-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
-
-Testers need:
-- The `.mobileprovision` file installed on their device
-- The `.ipa` package file
-
-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.
-
----
-
-## Mac Catalyst distribution (Mac App Store)
-
-Mac Catalyst allows you to run your iPad app on macOS. Titanium SDK 13.1.1.GA and later supports building for Mac Catalyst.
-
-### 1. Enable Mac Catalyst for your App ID
-
-1. Go to [Apple Developer → Identifiers](https://developer.apple.com/account/resources/identifiers/list)
-2. Select your App ID or create a new one
-3. Enable **Mac Catalyst** capability
-4. Save the changes
-
-### 2. Create Mac App Store Distribution Certificate
-
-1. Go to [Apple Developer → Certificates](https://developer.apple.com/account/resources/certificates/list)
-2. Click **+** to create a new certificate
-3. Select **Mac App Store Distribution**
-4. Upload your CSR (Certificate Signing Request)
-5. Download and install the certificate
-
-### 3. Mac Catalyst build targets
-
-Titanium provides two targets for Mac Catalyst:
-
-| Target | Description | Configuration |
-|--------|-------------|---------------|
-| `macos` | Development builds for testing on Mac | Debug-maccatalyst |
-| `dist-macappstore` | Production builds for Mac App Store | Release-maccatalyst |
-
-### 4. Build for Mac Catalyst (Development)
-
-```bash
-ti build -p ios -T macos
-```
-
-The `.app` bundle will be created at:
-```
-build/iphone/build/Products/Debug-maccatalyst/AppName.app
-```
-
-For a production-ready build:
-```bash
-ti build -p ios -T macos --deploy-type production
-```
-
-The `.app` bundle will be at:
-```
-build/iphone/build/Products/Release-maccatalyst/AppName.app
-```
-
-### 5. Build for Mac App Store (Distribution)
-
-```bash
-ti build -p ios -T dist-macappstore [-R <CERTIFICATE_NAME>]
-```
-
-Example:
-```bash
-ti build -p ios -T dist-macappstore -R "Apple Distribution: Your Team Name (TEAM_ID)"
-```
-
-If you omit the `-R` flag, Titanium will prompt you to select a certificate.
-
-**What happens during the build:**
-- Uses `Release-maccatalyst` configuration
-- Sets code signing to Manual with identity `-`
-- Creates a `.xcarchive` for Mac App Store
-- Installs the archive in Xcode's Organizer
-- Destination: `generic/platform=macOS`
-
-### 6. Upload to Mac App Store Connect
-
-1. Open Xcode → Window → Organizer
-2. Select your Mac Catalyst archive
-3. Click **Validate App** to check for issues
-4. Click **Distribute App**
-5. Select **Mac App Store**
-6. Follow the prompts to upload
-
-### 7. Create app listing in App Store Connect
-
-1. Go to [App Store Connect](https://appstoreconnect.apple.com)
-2. **My Apps → + → New App**
-3. Select **Mac** as platform
-4. Enter app details:
-   - Name
-   - Primary Language
-   - Bundle ID (must match your App ID with Mac Catalyst enabled)
-   - SKU
-5. Complete required metadata:
-   - Description
-   - Keywords
-   - Screenshots (Mac-specific sizes)
-   - Category
-   - Age rating
-
-### 8. Mac Catalyst entitlements
-
-Add Mac-specific entitlements in `tiapp.xml`:
-
-```xml
-<ios>
-  <entitlements>
-    <dict>
-      <!-- File access for saving to Downloads -->
-      <key>com.apple.security.files.user-selected.read-write</key>
-      <true/>
-      <key>com.apple.security.files.downloads.read-write</key>
-      <true/>
-
-      <!-- App sandbox (required for Mac App Store) -->
-      <key>com.apple.security.app-sandbox</key>
-      <true/>
-
-      <!-- Network access -->
-      <key>com.apple.security.network.client</key>
-      <true/>
-
-      <!-- Additional entitlements as needed -->
-      <key>com.apple.security.print</key>
-      <true/>
-    </dict>
-  </entitlements>
-</ios>
-```
-
-### 9. Common issues
-
-**Issue**: "No suitable signing certificate found"
-- Ensure you have a **Mac App Store Distribution Certificate** (not iOS Distribution)
-- The certificate must be installed in your Keychain
-
-**Issue**: Build fails with code signing errors
-- Verify your App ID has Mac Catalyst enabled
-- Check that the certificate matches the App ID
-- Try cleaning the build: `ti clean -p ios`
-
-**Issue**: App crashes on launch
-- Verify entitlements are correctly configured
-- Check Console.app for crash logs
-- Ensure all required capabilities are enabled
-
-### 10. Versioning
-
-Update version numbers in `tiapp.xml`:
-
-```xml
-<ti:app xmlns:ti="http://ti.tidev.io">
-  <id>com.yourcompany.yourapp</id>
-  <name>Your App Name</name>
-  <version>1.0.0</version>
-  <publisher>Your Company</publisher>
-  ...
-</ti:app>
-```
-
-- `version`: Display version (e.g., "1.0.0")
-- For iOS, use `pv-version-code` in `<ios>` section for build number
-- For Mac, the build number can be set in Xcode or via `CFBundleVersion`
-
-### 11. Testing on Mac
-
-Before submitting to Mac App Store:
-
-1. Build with `macos` target for testing
-2. Run the app on different Mac architectures (Intel and Apple Silicon)
-3. Test all features that use file system, network, and other sandboxed resources
-4. Verify entitlements are working correctly
-5. Test on macOS versions you plan to support
-
----