◉RORK LABJP
●DEADLINE — From August 31, 2026, Google Play requires target API level 36 (Android 16) or higher for both new apps and updates to existing ones. Twelve days left●EXTENSION — If you cannot make the date, the deadline extension form in Play Console buys you until November 1. The extension is not automatic, so the request itself has to land before August 31●TARGET SDK — Even for the Expo and React Native apps Rork produces, the targetSdkVersion is yours to verify. A template pinned to an older SDK will not meet the requirement on its own●RORK MAX — Where the original Rork emits React Native and Expo, Rork Max generates native Swift, covering iPhone, iPad, Apple Watch, Apple TV, Vision Pro, and iMessage●FUNDING — A $15M seed round led by Left Lane Capital was announced on April 9, alongside the acquisition of app builder Paperline to bring in engineering talent●iOS — Developer beta 6 of iOS 27 arrived on August 17 with the autumn release drawing closer. If you ship native Swift output, the new OS timeline feeds straight into your release plan●DEADLINE — From August 31, 2026, Google Play requires target API level 36 (Android 16) or higher for both new apps and updates to existing ones. Twelve days left●EXTENSION — If you cannot make the date, the deadline extension form in Play Console buys you until November 1. The extension is not automatic, so the request itself has to land before August 31●TARGET SDK — Even for the Expo and React Native apps Rork produces, the targetSdkVersion is yours to verify. A template pinned to an older SDK will not meet the requirement on its own●RORK MAX — Where the original Rork emits React Native and Expo, Rork Max generates native Swift, covering iPhone, iPad, Apple Watch, Apple TV, Vision Pro, and iMessage●FUNDING — A $15M seed round led by Left Lane Capital was announced on April 9, alongside the acquisition of app builder Paperline to bring in engineering talent●iOS — Developer beta 6 of iOS 27 arrived on August 17 with the autumn release drawing closer. If you ship native Swift output, the new OS timeline feeds straight into your release plan
TAG

App Store Review

10 articles
← Back to all tags
Related:
Rork6Privacy Manifest3Required Reason API3Rork Max3Expo3ITMS-910532indie developer2Sign in with Apple2Authentication2EAS Build1Release Automation1HealthKit1
⬡ Rork Dev/2026-06-19Advanced

Make ITMS-91053 Stop Catching Your Rork Max App — A Release-Proof Privacy Manifest Workflow

Fixing ITMS-91053 once doesn't keep it away — every new dependency can bring it back. Here's a field-tested workflow to audit your dependency tree, generate declarations, and catch the rejection locally before you upload.

⬡ Rork Dev/2026-06-14Advanced

Reading Steps and Sleep into Your Rork Max Native App — HealthKit for Calm, Number-Light Wellness Apps

A walkthrough of adding HealthKit to the native Swift app Rork Max generates: reading steps, sleep, and heart rate, writing mindful sessions, and handling background delivery — including the App Store review wording and the production-only 'permission granted but zero data' trap.

⬡ Rork Dev/2026-06-14Intermediate

When Your Rork App Gets ITMS-91053 — A Practical Guide to Privacy Manifests and Required Reason APIs

Submitting a Rork-generated Expo app to the App Store can trigger Privacy Manifest warnings even when you never wrote the offending code. Here is how to clear both Required Reason API and SDK manifest issues before you submit.

⬡ Rork Dev/2026-05-23Advanced

Auditing Privacy Manifests for Rork-Generated Expo Apps — A One-Day Pre-Submission Workflow for Indie Developers

A pre-submission workflow for indie developers shipping Rork-generated Expo apps. Walks through how to enumerate every dependency, detect missing PrivacyInfo.xcprivacy files, and ship without ITMS-91053 rejections — based on twelve years of personal app development.

⬡ Rork Dev/2026-05-04Intermediate

Why Your Rork App Gets Rejected for Broken Restore Purchases — Fixing App Store Guideline 3.1.1

If your Rork-built subscription app is getting rejected for Guideline 3.1.1, the Restore Purchases button is almost always the cause. Learn how to wire it up correctly with expo-in-app-purchases or react-native-iap and pass review on the next try.

◇ App Dev/2026-05-04Intermediate

Designing Subscription Apps with Rork — From Revenue Model to App Store Approval

How to add a subscription revenue model to apps built with Rork — covering pricing design, StoreKit integration, and the specific issues that cause App Store rejections.

⬡ Rork Dev/2026-05-04Advanced

Shipping a Kids App with Rork Max — Kids Category Review, COPPA, and Parental Gates

A complete guide to developing and publishing kids apps with Rork Max. Covers App Store Kids category requirements, COPPA-compliant implementation patterns, parental gate code examples, and Ask to Buy integration for indie developers.

⬡ Rork Dev/2026-05-03Advanced

Sign in with Apple in Rork: Server-Side Verification, Account Linking, and the Mandatory Deletion Flow

Dropping a Sign in with Apple button into your Rork app and shipping it is the fastest path to a rejection. This guide walks through the full picture: nonce hashing, server-side ID token verification with Apple's JWKs, the mandatory account deletion flow, and the often-forgotten revoke_token call back to Apple.

⬡ Rork Dev/2026-04-30Intermediate

Implementing App Tracking Transparency in Rork: How to Pass App Store Review

How to implement App Tracking Transparency (ATT) in Rork-built iOS apps so they pass App Store review on the first try, with the right Info.plist copy, prompt timing, and graceful fallback when users deny tracking.

⬡ Rork Dev/2026-04-24Intermediate

Adding Sign in with Apple to Your Rork App — What Review Actually Requires and Where People Get Stuck

A practical walkthrough for adding Sign in with Apple to an existing Rork app. Covers the exact Guideline 4.8 requirements that reject Google/Facebook-only apps, the non-obvious parts of expo-apple-authentication, backend token verification with identityToken, and the account deletion requirement most tutorials skip.