การเผยแพร่ผ่าน App Store และสำหรับองค์กร

Welcome to the final stage of app development: distribution! This lesson will guide you through the essential components and processes for getting your Objective-C app into the hands of users, whether through the official App Store or within an enterprise.

Understanding how to properly sign and provision your application is crucial for successful deployment.

Before your app can run on an iOS device or be submitted to the App Store, it needs a digital signature. This signature verifies that the app comes from a trusted developer (you!)

• Developer Certificate: Used for signing apps during development and testing on your registered devices.
• Distribution Certificate: Used for signing apps for public release (App Store) or in-house enterprise distribution.

These certificates are issued by Apple and reside on your Mac.

Every iOS application needs a unique identifier known as an App ID (or Bundle ID). This is typically in a reverse domain name format, like com.yourcompany.yourappname.

The App ID tells Apple and the operating system exactly which app is which. It's also used to enable specific app capabilities (called entitlements) like Push Notifications, iCloud, or In-App Purchases.

A provisioning profile acts as a bridge, linking your digital identity (certificate), your app's unique identifier (App ID), and the devices or distribution methods allowed for your app.

Think of it as a security policy that Xcode embeds into your app. It defines:

• Which certificate can sign the app.
• Which App ID the app uses.
• Which devices (for development/testing) or distribution method (App Store/Enterprise) are authorized.

There are different types of provisioning profiles, each serving a specific purpose:

• Development Profile: Used during the development phase. It allows your app to run on specific, registered test devices. It links your Developer Certificate, App ID, and a list of device IDs.
• Ad Hoc Profile: Used for distributing beta versions of your app to a limited number of test users (up to 100 devices). It uses your Distribution Certificate and a list of specific device IDs.

Both are crucial for testing before a wider release.

When your app is ready for the public, you'll use an App Store Distribution Profile. This profile is specifically designed for submitting your app to Apple for review and eventual release on the App Store.

Key characteristics:

• Uses your Distribution Certificate.
• Tied to your App ID.
• Does NOT specify individual devices, as it's for global public distribution.

This profile ensures your app is correctly signed for Apple's submission process.

Distributing via the App Store involves several steps:

1. Archive: In Xcode, select 'Product' > 'Archive' to create an app archive.
2. Upload: Use Xcode's Organizer or Transporter app to upload the archive to App Store Connect.
3. Metadata: Log into App Store Connect to add screenshots, descriptions, pricing, and other details.
4. Submit for Review: Once everything is set, submit your app to Apple's review team.
5. Release: After approval, you can manually release or set it for automatic release.

TestFlight is often used here for beta testing with external testers before full public release.

For companies that want to deploy apps internally to their employees without going through the public App Store, Enterprise Distribution Profiles are used.

This profile:

• Requires enrollment in the Apple Developer Enterprise Program.
• Uses a specific Enterprise Distribution Certificate.
• Allows distribution of the app to any device within the organization.

These apps are often referred to as 'in-house' apps and are not subject to App Store review.

Enterprise distribution bypasses the App Store. Here's how it generally works:

1. Enrollment: Your organization must be part of the Apple Developer Enterprise Program.
2. Sign with Enterprise Profile: Build your app using an Enterprise Distribution Profile.
3. Distribution: Apps can be distributed via:
   • Mobile Device Management (MDM) solutions.
   • A secure internal website with a manifest file.

Users can install these apps directly from your internal channels, provided they trust your organization's certificate.

Test your understanding of provisioning profiles and their uses.

You've successfully navigated the world of iOS app distribution! We covered:

• The role of Developer and Distribution Certificates in code signing.
• The importance of unique App IDs.
• How Provisioning Profiles (Development, Ad Hoc, App Store, Enterprise) link certificates, App IDs, and distribution methods.
• The processes for App Store Connect submission and Enterprise (in-house) distribution.

With this knowledge, you're ready to confidently deliver your Objective-C applications!