Erstellen einer neuen App-Version für die MemberPress-App

App build generation creates installable iOS and Android application files using cloud-based compilation. The build system compiles site settings, menus, branding, and GitHub customizations into app packages. This document explains how to prepare for builds, register test devices, request build generation, and access completed builds.

Understanding the Build Process

Build generation compiles WordPress configuration into platform-specific application packages. Cloud-based build servers handle compilation without local development environment requirements. Build types serve different purposes in development and distribution workflows.

Configuration compilation incorporates site settings, menus, and branding into app code. Build generation captures the current WordPress configuration at the time of request.

GitHub integration includes custom code from connected repositories. Custom modifications compile alongside standard app functionality.

Test Build purpose enables internal quality assurance and stakeholder review. Test Builds install directly on registered devices without app store distribution.

Release Build purpose prepares production-ready packages for app store submission. Release Builds meet Apple and Google distribution requirements for public availability.

Build timing typically completes within 15-30 minutes of request submission. Complex configurations or server load may extend completion time.

Connecting App to WordPress

1. Navigieren Sie zu Dashboard > MP App > Configure > Connect.
2. Enter connection credentials in the provided fields.
3. Klicken Sie auf Verbinden Sie to establish the site connection.
4. Verify that the connection success confirmation displays.

App connection enables the build system to access WordPress configuration and content.

Registering iOS Test Devices

iOS device registration enables Test Build installation on specific devices.

1. Navigieren Sie zu Dashboard > MP App > Configure > iOS Devices.
2. Klicken Sie auf die Add New Device Taste.

3. Enter a descriptive name in the Device Name Feld.

4. Klicken Sie auf Weiter to proceed to UDID registration.
5. Open the Camera app on iPhone.
6. Scan the displayed UDID QR code with the iPhone camera.
7. Tap the notification or link appearing after scanning.
8. Follow on-screen prompts to complete device registration.
9. Return to the WordPress browser window.
10. Verify the device appears in the registered devices list.

Anmerkung: iOS devices must be registered before Test Build installation. Android testing does not require device registration.

Requesting Build Generation

Build request initiates compilation process for selected platforms and build types.

1. Navigieren Sie zu Dashboard > MP App > Build.
   
2. Klicken Sie auf die Request Build Taste.

3. Select platform options:
   • iOS for iPhone and iPad apps;
   • Android for Android device apps;
   • Beide for simultaneous iOS and Android builds.

4. Select build type:
   • Test for sideloading and internal testing;
   • Freigabe for app store submission.

5. Klicken Sie auf Weiter to proceed to configuration review.
6. Review all build settings displayed on the confirmation screen.
7. Verify platform and build type selections are correct.
8. Klicken Sie auf Send Build Request to submit the build generation request.
9. Wait 15-30 minutes for build completion.
10. Klicken Sie auf Recheck Status Now to refresh the build progress display.

Build requests initiate the cloud compilation process, creating platform-specific application packages.

Understanding Build Types

Build types serve different purposes in development and distribution workflows.

Test Build Characteristics

Test Builds enable internal testing without app store submission.

Sideloading installation allows direct device installation via QR code. Test Builds bypass app store distribution for rapid testing.

Device registration requirement applies to iOS Test Builds only. Registered devices receive provisioning enabling Test Build installation.

Simulated purchases use placeholder pricing for in-app purchase testing. Test environment validates purchase flows without real transactions.

Rapid iteration supports frequent updates during development. Test Builds generate quickly, enabling continuous testing cycles.

Release Build Characteristics

Release Builds prepare production packages for app store distribution.

App store submission requires Release Build files meeting platform requirements. Release Builds include proper signing and provisioning for distribution.

Real pricing display shows actual in-app purchase costs and terms. Release Builds connect to production billing systems.

TestFlight distribution enables controlled beta testing before public launch. Release Builds can be distributed through TestFlight for iOS.

Production quality includes optimizations and final configurations. Release Builds represent the final product for public distribution.

• Test Builds: Install directly using the Install Test App Taste.
  
• Release Builds: Download the .ipa or .aab or use the Publishing Tool to submit to app stores.
  

Anmerkung: You can create up to 20 builds per month. If you need more, contact support.

Understanding Build Limits

Build generation follows specific quantity limitations per account.

Monthly build limit allows up to 20 builds per month. Limit includes both Test and Release Builds across all platforms.

Limit calculation counts each platform separately for multi-platform requests. Requesting iOS and Android together consumes two build credits.

Additional builds require contacting support for limit increases. Extended development projects may need higher monthly allocations.Limit reset occurs at the beginning of each calendar month. Build count resets to zero on the first day of the month.