# SP Drive iOS 2.0 — delivery checklist
Nothing below was done: no archive, no upload, no object created in the developer portal or in App Store Connect.
# 1. Developer portal (team 3YM54G49SN)
| # |
Item |
State today |
Needed |
| 1 |
App ID ai.spboucher.spdrive.ios |
exists (1.0) |
unchanged — associated domains, app group, keychain group as in 1.0 |
| 2 |
App ID ai.spboucher.spdrive.ios.fileprovider |
exists |
unchanged |
| 3 |
App ID ai.spboucher.spdrive.ios.share |
exists |
unchanged |
| 4 |
App ID ai.spboucher.spdrive.ios.widgets |
does not exist |
create (explicit), capability App Groups with group.ai.spboucher.spdrive.ios; no other capability |
| 5 |
App group group.ai.spboucher.spdrive.ios |
exists |
assign to the new App ID |
| 6 |
Provisioning profiles for …ios.widgets (development + App Store) |
do not exist |
created by Xcode on the first signed build if automatic signing is used (-allowProvisioningUpdates, as Scripts/release.sh does); otherwise by hand |
| 7 |
Profiles of the three existing App IDs |
valid |
nothing to regenerate: their entitlements did not change |
Not needed: push notifications, iCloud, Siri / App Intents, new background modes, any capability for PencilKit, Vision, VisionKit,
WidgetKit deep links (spdrive://), Swift Charts, CoreImage QR codes or the linked package (Foundation only).
# 2. App Store Connect (record 6836524538)
| # |
Item |
| 1 |
New version 2.0.0; the build number must be greater than 1 (project.yml says 2) |
| 2 |
English store metadata only if English is announced — the app's English is partial (see PHASE2-iOS.md §5) |
| 3 |
Privacy answers: unchanged (no new data type; the AI screens send questions to the account's own SP Drive server, which is the service itself). If external AI providers are ever enabled on the production server, the privacy text must say that retrieved passages go to that provider when the user allowed it |
| 4 |
Review notes: widget; spdrive:// links only open places inside the app; the AI feature is absent unless the server has a provider configured |
| 5 |
Export compliance: unchanged (ITSAppUsesNonExemptEncryption false) |
# 3. Before archiving
| # |
Check |
How |
| 1 |
Production backend is 2.0 (or the app will simply present itself as 1.0) |
curl https://drive.spboucher.ai/api/v1/meta |
| 2 |
apple-app-site-association of production still lists the app (passkeys) |
unchanged from 1.0 |
| 3 |
The sibling repository ../SPDrive is checked out on the commit whose SPDriveNext was tested |
git -C ../SPDrive rev-parse HEAD — built and tested with c6c11d2 (branch next). The archive depends on a local path package: the sibling checkout must be present and at that commit on the machine that archives |
| 4 |
Version and build |
xcodebuild -project SPDrive.xcodeproj -scheme SPDrive -showBuildSettings | grep -E "MARKETING_VERSION|CURRENT_PROJECT_VERSION" → 2.0.0 / 2 |
| 5 |
Release build has no debug switch |
Scripts/release.sh already checks the Info.plists; the SPDRIVE_* environment switches are compiled out of Release (#if DEBUG) |
| 6 |
Real device pass (never done): passkey sign-in, document camera, Apple Pencil, widgets on a home screen, share sheet from Safari / Mail, cellular with « Wi-Fi seulement », Low Power Mode, a background upload across a lock |
by hand |
| 7 |
Merge next into main only after the device pass |
— |
# 4. What a tester should know
- Against a 1.0 server every 2.0 control is absent by design.
- SP Drive AI has only ever answered through a fake endpoint in tests. Its first real answer will be on the real server.
- Shared folders (« Partagés avec moi ») are browsed online; they are not kept offline and do not appear in the Files app.