Contact person: Business Client

Phone:Show

Email:Show

Location: Glasgow, United Kingdom

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Title

Finish iOS Wrapper + TestFlight Release for Existing PWA (Xcode / Capacitor) + Optional CI

Overview

I have a working PWA and part of the iOS setup is already done. I need an experienced iOS/Capacitor engineer to finish the iOS wrapper, fix code signing/provisioning, produce a TestFlight build, and hand over clear docs. (Optional: set up a simple GitHub Actions pipeline once the manual flow is stable.)

This is hands-on execution, not just advice.

Current State
• Web app (PWA) is built and ready.
• iOS project scaffolding exists (Capacitor / CocoaPods) and some build steps already run.
• Stuck on Apple code signing (.p12 password / provisioning profile mismatches) and CI reliability.
• App Store Connect API key is available.

What I Need You To Do
1. Complete the iOS wrapper
• Open/repair the existing Capacitor iOS project (icons, splash, plist, URL schemes, any required entitlements).
• Ensure the PWA is packaged and loads correctly in WKWebView (offline/cache behavior as appropriate).
• Verify deep links/universal links if needed (I’ll confirm if required).
2. Signing & Provisioning (clean setup)
• Generate a fresh CSR/private key pair and create a new Apple Distribution certificate.
• Export a working .p12 (verified locally with openssl) and the correct App Store provisioning profile for the Bundle ID.
• Align the Xcode project to use the correct Team ID, Bundle ID, and manual signing settings.
3. Build & Release
• Produce a Release .xcarchive and .ipa locally.
• Upload to TestFlight (Transporter, altool, or Fastlane—your choice).
• Confirm at least one build is available to testers.
4. Documentation (must-have)
• Step-by-step: how you created the certs/profiles, exported .p12 (with a known-good password), base64’d it for secrets, and configured Xcode signing.
• How to make a new build locally.
• Common error fixes (e.g., “MAC verification failed” for PKCS#12).
5. (Optional) CI with GitHub Actions
• After a successful manual release, add a lightweight CI job for TestFlight.
• Separate workflow for unit tests with signing disabled (CODE_SIGNING_ALLOWED=NO, etc.).

Deliverables
• Working iOS app wrapper for the existing PWA.
• Verified TestFlight build visible in App Store Connect.
• .p12, provisioning profile, and clear docs on how to recreate/rotate them.
• (Optional) Minimal GitHub Actions CI pipeline using repository secrets.

I Will Provide
• GitHub repo access.
• Apple Developer & App Store Connect access (with API key).
• Bundle ID, Team ID, and any existing assets (app name, icon, splash, capabilities).
• Notes/screenshots of current build/signing errors.

Please Include In Your Proposal
• Short summary of Capacitor + iOS experience and App Store releases you’ve shipped.
• 1–3 similar projects (PWA → iOS wrapper is a plus).
• Your preferred approach (manual first, then CI).
• Fixed price or hourly, and estimated effort.

Success Criteria
• I can build locally (archive + export) without signing errors.
• TestFlight build is uploaded and ready for testers.
• Documentation lets me repeat the process and rotate certs without breaking things.

Security
• Use a temporary keychain on CI.
• Store secrets in GitHub Secrets only.
• Use App Store Connect API key (no shared Apple passwords)." (client-provided description)