Sample, our own app. This report is written against Gridmark, an app Tempore LLC builds and sells. It is not a customer report and shows no customer's data. We wrote it on 20 November 2026 from Gridmark's source code, its 1.3.0 (9) release archives and the full archive logs of the releases either side, without building anything. Items that need App Store Connect or Xcode Organizer are marked "Checked during an engagement"; a customer's report answers them with the read-only access that comes with the work.
Health check: Gridmark: MGRS Navigation
1. Summary
Status: current for every upload rule we could check from the code and the archives. Two App Store Connect items (age-rating answers, crash reports) are checked during an engagement; the EU trader status was checked in App Store Connect on 20 November 2026.
Gridmark is built with Xcode 27.0 on the iOS 27, watchOS 27 and macOS 27 SDKs, in Swift 6 language mode, and targets iOS, watchOS and macOS 26. It already meets Apple's April 2027 upload rule. Apple accepted the 1.3.0 (9) uploads on 20 November 2026 with no warnings. The app and the Watch app declare the required-reason APIs their code uses. The two widget extensions have no privacy manifest, and their code uses none of those APIs, so nothing is wrong today (L1). It has no package-manager dependencies; one open-source C++ library is copied into the source. The full build logs either side of 1.3.0 show no deprecation warnings. The EU trader status, recorded as "non-trader" before Tempore became a company, was checked in App Store Connect and already reads "trader". No Make it current work is needed.
| Severity | Count |
|---|---|
| Blocker | 0 |
| High | 0 |
| Medium | 0 |
| Low | 2 (L1, L2) |
2. Standard checks
The same checks run for every app, each tied to the Apple rule and date it comes from. File references are to Gridmark's repository.
Build toolchain
Xcode 26 or later on the iOS 26 SDK (since 28 April 2026); iOS 27 SDK from April 2027.
Meets both
The archived iOS app's Info.plist: DTXcode 2700, DTXcodeBuild 27A266a (Xcode 27.0), DTSDKName iphoneos27.0. Watch app and Watch widget: watchos27.0. Mac app: macosx27.0. Swift 6.0 language mode (project.yml line 16; FieldCore/Package.swift line 1). Upload accepted: the archive records "Uploaded to Apple" with no warnings, at 03:45 UTC (iOS) and 03:46 UTC (Mac) on 20 November 2026.
Deployment target
iOS 13 or later (since 9 September 2026); iOS 15 or later from April 2027.
Meets both
project.yml line 5 (iOS 26.0), lines 114 and 136 (watchOS 26.0). Archived MinimumOSVersion 26.0 for the iOS app, the iOS widget, the Watch app and the Watch widget; Mac LSMinimumSystemVersion 26.0. The shared package FieldCore declares lower minimums (iOS 18, macOS 15, watchOS 11), but the app targets decide the shipped minimum, so this has no effect.
Privacy manifest
Required-reason APIs declared (since 1 May 2024).
Meets for the app and the Watch app. The widgets have none and use none (L1).
App/PrivacyInfo.xcprivacy: File timestamp (DDA9.1, C617.1, 3B52.1), Disk space (E174.1, 85F4.1), User defaults (CA92.1). WatchApp/PrivacyInfo.xcprivacy: User defaults (CA92.1), File timestamp (C617.1), Disk space (E174.1). Both are inside the archive. The app binary imports NSUserDefaults, NSURLContentModificationDateKey, NSURLVolumeAvailableCapacityKey and NSFileSystemFreeSize, matching the declared categories; no system boot time or active keyboard symbols in the iOS, Watch or Mac binaries (nm -u).
Deprecated APIs
The build log is the test.
None found
The archive logs of 1.2.0 (8) (iOS 22 warning lines, Mac 15) and 1.4.0 (10) (iOS 25, Mac 22) contain no deprecation warnings; every "deprecat" match in them is the -Wdeprecated-declarations compiler flag. A text search of the shipped code for UIScreen.main, NavigationView, UIApplication.shared.windows, keyWindow, UIWebView, CLLocationManager.authorizationStatus(), UIGraphicsBeginImageContext, statusBarFrame and appStoreReceiptURL found no matches. 1.3.0's own archive log wasn't kept, so this check rests on the logs either side of it.
Third-party libraries and CocoaPods
CocoaPods' central repository stops accepting new library versions on 2 December 2026 (CocoaPods blog).
No package-manager dependencies; not affected
No Podfile, Cartfile or Package.resolved. The Xcode project has no remote package references and one local one, FieldCore. Copied-in source: GeographicLib 2.7, MIT licence. Google Maps SDK 11.2.0 is an opt-in build option and is not in 1.3.0: the archive has no frameworks and no Google Maps symbols.
Age-rating declarations
Required for updates since 16 November 2026; for all apps by 12 January 2027.
Checked during an engagement Probably answered; the answers aren't recorded in the repository.
Age rating 4+ was set on 15 October (docs/release-checklist.md line 18). 1.3.0 was submitted on 19 November, three days after Apple began requiring the new declarations for updates, which suggests App Store Connect accepted answers. Gridmark shares plans with other people and can share a position readout, so the new "Shared Location" answer is worth a careful look in App Store Connect.
Mac: Apple silicon
Intel-only apps stop running on Macs with Apple silicon after macOS 27.
Native
lipo -archs on the archived Mac binary: x86_64 arm64. No com.apple.quarantine attribute on the archived Mac app (xattr -r).
EU trader status
Required to submit updates for apps sold in the EU (since 16 October 2024).
current Declared as trader.
App Store Connect, App Compliance → Digital Services Act, checked 20 November 2026: "This developer has identified itself as a trader for this app." An older checklist note (docs/release-checklist.md line 36) said "non-trader" from before the move to Tempore LLC; it was out of date and has been corrected.
Crashes
Apps that crash on launch are removed from the App Store immediately.
Checked during an engagement
Crash reports live in Xcode Organizer and App Store Connect. The repository's own evidence: the sandboxed Mac archive launched with no crash report (docs/release-1.3.0.md line 50), and the full UI test suites ran on iPhone and iPad simulators (lines 45–49).
In-app purchases and receipts
SHA-256 receipt validation, or AppTransaction and Transaction (since 24 January 2025).
Not applicable
No purchase or receipt code. StoreKit is imported in App/FieldNavigationApp.swift only to ask for a rating. No push notifications, so Apple's push certificate change doesn't apply either: no aps-environment entitlement, and notifications are local only.
App Review risks
Apple's current App Review Guidelines.
None found in the code Full review during an engagement
Location is the only permission asked for, "when in use", with purpose strings in both apps. Background location is used only while recording a track and is explained to App Review. Export compliance is declared exempt. The Google Maps key ships empty in the archived Info.plist, so no key is exposed.
3. Findings
L1: Widget extensions have no privacy manifest (confirmed; no effect today)
lowWidgets/ · WatchWidgets/
Evidence
In the 1.3.0 (9) archive, FieldNavigationWidgets.appex and FieldNavigationWatchWidgets.appex contain no PrivacyInfo.xcprivacy; the app and the Watch app do. The widgets don't need one today:
- Their source imports only ActivityKit, SwiftUI and WidgetKit, plus one shared file. A text search finds no
UserDefaults, file dates, free disk space, system uptime or keyboard APIs. - Their compiled binaries import 79 and 74 symbols, none of them a required-reason API (
nm -u). The same check on the app binary finds the expected ones, so the method works. - The extensions share no storage with the app (no App Group).
Effect
None now. If a later change gives a widget a shared settings store or file dates, a future upload could be refused until a manifest is added.
Fix
Add a minimal manifest to each widget extension, or add one when a widget first uses such an API. No quote needed for our own app.
L2: Small compiler warnings, none about deprecated APIs
lowFieldCore
Evidence
The 1.2.0 (8) and 1.4.0 (10) archive logs repeat the same kinds of warning: an unused value (Plans.swift line 343, PhotoAnnotation.swift line 23), an unneeded nonisolated(unsafe) (ReadoutPreferences.swift line 161), and a narrowing conversion inside the copied GeographicLib code (UTMUPS.cpp line 217). The 1.4.0 log adds two unneeded try markers in a screen that is new in 1.4.0.
Effect
None on users or uploads. They make new, important warnings harder to spot.
Fix
Remove the unused values and the extra annotation; leave the copied library file as its authors ship it. No quote needed for our own app.
4. Guarantee risks
None found in the code. The app's App Review history is checked during an engagement. In a customer report, this section names anything that would fall outside the Make it current guarantee, before you pay.
5. What we did not check
- Gridmark's map, elevation and trail services, and Apple's iCloud.
- Security. A health check is not a security audit.
- Features that need real hardware: GPS accuracy, the compass, background location and the paired Apple Watch.
- Xcode's privacy report for the archive, crash reports and App Store Connect settings. Read-only access to these comes with an engagement.
6. Fixed quote: Make it current
Not needed. Every upload rule checked is already met.
In a customer report, this section lists each item with the findings it covers, a fixed total from $2,500, the delivery date, the 50% deposit, the refund guarantee and the 30-day warranty.
7. Out of scope
Not applicable to this sample.
8. After the update
For an app in this state, we would recommend App care: checks against each iOS and macOS beta and release, so the next Apple change is handled before it blocks an upload.
9. Next step
This is a sample. To get a report like this for your app, email support@tempore.net with the subject "App care" and your App Store link.
Reginald Mathieu
Tempore LLC · support@tempore.net