I’m excited to share a set of mobile apps I’ve recently completed and published on both the Google Play Store and the Apple App Store. These apps are designed with a simple goal in mind: to make meaningful, structured content more accessible, whether you’re studying theology or improving your English vocabulary. 📱 Now Available on Both Platforms All apps are live and available for download: Google Play Developer Page: https://play.google.com/store/apps/dev?id=5835943159853189043 Apple App Store Developer Page: https://apps.apple.com/ca/developer/q-z-l-corp/id1888794100 📖 Theology & Confession Study Apps For those interested in Reformed theology and classical Christian teachings, I’ve developed a series of apps that present foundational texts in a clean, focused reading format: The Belgic Confession Canons of Dort Heidelberg Catechism Westminster Shorter Catechism Each app is designed to provide a distraction-free experience, making it easier to read, reflect, and revisit these im...
解决 React Native iOS 缺少 iPad 图标错误(152x152 / 167x167 验证失败)
- Get link
- X
- Other Apps
By
Errong Leng
-
解决 React Native iOS 缺少 iPad 图标错误(152x152 / 167x167)
在提交 React Native iOS 应用到 App Store 时,如果你遇到类似错误:
Missing required icon file. The bundle does not contain an app icon for iPad of exactly '152x152' pixels The bundle does not contain an app icon for iPad Pro of exactly '167x167' pixels
这个问题看起来很奇怪,因为你的 Xcode 项目中已经显示支持 iPad。
🔍 现象
你可能已经看到:
- Deployment Info 中有 iPad 配置
- iPad Orientation 已启用
但是打开 Assets.xcassets → AppIcon 时:
- ❌ 没有 iPad 图标槽位
最终导致 App Store 校验失败。
🧠 根本原因
这是因为配置不一致导致的:
- 项目设置支持 iPad ✅
- AppIcon 资源仍然是 iPhone-only ❌
在很多 React Native 项目中,默认生成的 AppIcon 并不包含 iPad 图标槽位。
✅ 解决方案(最简单有效)
重新创建 AppIcon:
- 打开
Assets.xcassets - 删除当前的
AppIcon - 右键 → New App Icon
- 命名为
AppIcon
新的 AppIcon 会自动包含:
- iPad 图标(152x152)
- iPad Pro 图标(167x167)
🖼️ 必须提供的图标
你至少需要提供:
- 152 × 152(iPad)
- 167 × 167(iPad Pro)
将对应 PNG 图片拖入即可。
⚠️ 重要检查
确保项目确实支持 iPad:
Build Settings → Targeted Device Family = 1,2
含义:
- 1 = iPhone
- 2 = iPad
🚀 如果你不打算支持 iPad
可以直接关闭 iPad 支持:
Targeted Device Family = 1
并在 Info.plist 中:
<key>UIDeviceFamily</key> <array> <integer>1</integer> </array>
这样就不会再要求 iPad 图标。
💡 为什么 React Native 容易踩这个坑
React Native 的模板有时没有及时跟上 Xcode 的更新,导致资源配置(Asset Catalog)与项目设置不一致,从而在提交 App Store 时出现校验错误。
✅ 结果
完成上述修改后:
- ✅ 校验通过
- ✅ 可以正常上传 App Store
一个 2 分钟的修复,可能帮你省下 2 小时的排查时间。
❤️ Support This Blog
If this post helped you, you can support my writing with a small donation. Thank you for reading.
Popular Posts
Cross compile tensorflow for armv7l targets via bazel
By
三好Daddy
-
2026 Begins: Choosing to Stay on the Path as a Blogger
By
Errong Leng
-
Today is January 1st, 2026 . Before rushing into new goals, I spent some time looking back at the past 12 months of data for this blog — the quiet numbers that tell a very honest story. Looking Back at the Numbers Over the past year: 📈 Total views: ~44,600 👀 Daily average visits: ~200 💬 Comments: 19 💰 AdSense income: about $0.01 per month At first glance, these numbers may look small — especially the income. But when I zoom out, I see something more meaningful. This blog has been quietly read every single day . No viral posts. No aggressive promotion. No paid traffic. Just consistent readers arriving through search, bookmarks, and curiosity. That consistency matters. What the Traffic Graph Tells Me The graph over the last 12 months shows something important: Early months were quiet and uneven Mid-year brought steady growth Toward the end of the year, traffic became more stable , with clear spikes when certain posts resonated This tell...
Health Checks and Scaling Strategies for Next.js in Kubernetes
By
Errong Leng
-
Health Checks and Scaling Strategies for Next.js in Kubernetes This is Part 6 and the final post of the series: Self-Hosting Next.js in Kubernetes (Without Vercel) . At this point, your Next.js standalone app: Builds cleanly Runs in a minimal Docker image Deploys correctly on Kubernetes / OpenShift Serves static assets properly Uses runtime configuration and secrets Now let’s make it resilient and scalable . Why Health Checks Matter Kubernetes relies on health checks to: Know when a pod is ready to receive traffic Restart unhealthy containers Safely roll out new versions Without proper probes, traffic can be sent to a pod that isn’t ready yet. Readiness Probe A readiness probe tells Kubernetes: “This pod can accept traffic.” For most Next.js apps, the root path works well: readinessProbe: httpGet: path: / port: 3000 initialDelaySeconds: 10 periodSeconds: 5 If your app depends on downstream services (APIs, d...
Comments
Post a Comment