SPB Git

Repository Public

RELEASE.md 2.7 KB

# Release

# macOS (Developer ID, outside the App Store)

bash
scripts/archive-macos.sh      # Release archive, universal, signed with the Developer ID identity found in the keychain → dist/SP Lecture Studio.app
scripts/notarize-macos.sh     # notarytool (keychain profile MacLustr-Notarize) → staple app → DMG → sign → notarize → staple

State on 2026-11-18: version 1.0.0 (1), universal (arm64 + x86_64), sandbox + hardened runtime, notarized and stapled (spctl: accepted, source = Notarized Developer ID; re-archived and re-notarized after the final fixes). Artifacts: dist/SP Lecture Studio.app, dist/SPLectureStudio-1.0.0.dmg (+ .sha256). Not installed in /Applications, not published anywhere.

# iOS / iPadOS (App Store Connect)

iOS apps are code-signed and distributed through App Store Connect / TestFlight; notarization is a macOS concept and does not apply.

bash
scripts/archive-ios.sh all        # archive with automatic signing + export of the IPA → dist/ios-export/
scripts/archive-ios.sh validate   # altool --validate-app
scripts/archive-ios.sh upload     # altool --upload-app (TestFlight)

The API key ids come from ~/.config/splecturestudio/asc.env (ASC_KEY_ID, ASC_ISSUER_ID, ASC_KEY_PATH), outside the repository. Increase CURRENT_PROJECT_VERSION in Apps/LectureStudio/project.yml before each upload.

State on 2026-11-18:

  • App record 6836594820 "SP Lecture Studio", bundle ai.spboucher.splecturestudio.ios, SKU splecturestudio-ios-001, primary language fr-CA, created from the owner's signed-in Safari session at his request.
  • Filled in: categories Education / Productivity; name, subtitle, description, keywords, promotional text, support and marketing URLs in fr-CA and en-CA; copyright; TestFlight test notes and feedback address.
  • Build 1.0.0 (1): validated ("VERIFY SUCCEEDED"), uploaded ("UPLOAD SUCCEEDED") and processed by Apple (state VALID). It was archived before the last macOS-side fixes (thumbnails, canvas hit-testing), which do not change iOS behaviour.
  • Left to the owner: add the build to an internal TestFlight group and install it on a real iPhone / iPad; screenshots, age rating, privacy policy URL and App Privacy answers (required only for App Store review); confirm the export-compliance answer. Nothing was submitted for review.

# Checklist before a public release

  1. scripts/build-all.sh && scripts/test-all.sh --long --ui, and scripts/test-ui.sh mac with the screen unlocked.
  2. The hardware checks listed in docs/QA.md ("Never verified").
  3. Bump versions, archive both platforms, notarize, upload.
Files main
Menu

Theme