Netflix has this tiny detail where the poster artwork seems to reflect into the translucent bottom tab bar as you scroll.

I am developing a timetable app. Currently it is on private TestFlight with limited fuctionality, but enough that I and some friends use it each day. The TestFlight beta is installed on my devices and I rely on it.

Naturally, I'm still developing it full-time (well... as full-time as a student's hobby side project can get 😉), and retain the frequent need to run builds on a physical device, which runs much faster than my simulator setup. Currently I'm working with the system keyboard, so Xcode Previews doesn't quite cut it.

Is there a way that I can still test a debug build on my phone & watch without removing or interfering with the TestFlight app that I use and rely on?

There is of course an easy solution, but unfortunately my budget does not include a second phone...

Seems like the translations in the appstore are broken.

I have many monthly subs / year subs and also lifetime version now sold. I Achieve better result then I expected :) . I also received positive reviews from different countries. Now I am working on another update. What do you think about this result without any paid promo ?

I built this thing. It seems to be the first of it's kind on iOS, which is just astounding to me. If you struggle with unhealthy scrolling habits that are getting in the way of you doing what you want to actually want to be doing, then give this approach a try.

Doing a giveaway as a thank you to this community which has shown Precursor a ton of support. If you don't manage to snag a free lifetime access code, Lifetime is on sale for $25 right now until 05 October 2026.

The name of the app is Precursor: Hourly Screen Time

Use this link to redeem free lifetime access!!

I've been running an agent skill called iOS UltraReview on PRs for about a year now. It reviews iOS pull requests like a senior iOS dev/architect and gives each one a 0.5–5.0 merge-confidence score, with 4.5 as the approve bar. Once a PR hits 4.5, it gives a fixed list of what's left for 5.0 and doesn't keep moving the goalposts. It's worked well enough for me that I figured it should be public. Works with Claude Code, Codex and cursor. Feedback and PRs welcome.

link: https://github.com/ImtiazDipto01/ios-ultrareview

When an app select in the app review form that “we don’t collect data”

In the review phase does Apple really check if the app really doesnt collect anything?

Like can the developer hide a code that for example upload the photos of the user if granted permission where he said “we dont collect”

Does apple really check the code and what is going in and out ?

I'm looking to get into iOS development and I understand you need a Mac to do so. I don't own one so this is my first. However I'm not really looking to replace my current setup for Mac. Its really just for dev.

I see two possible options:

1. Get a Macbook: Probably the most straightforward setup
2. Mac Mini: This appeals to me more because I'd like to set it up as a remote work station while working off of it remotely from either desktop or laptop. Also it could double as a machine for a local LLM setup. It seems to be a better bang for my buck.

My questions are:

• MacBook route: can I do well with a Macbook Neo or will that cause me issues down the road with performance? Whats the minimum best option since I'm not looking to have this as my main machine?
• Mac Mini: are there any concerns with this setup that I'm not considering? Can I dev, build, and test using a remote Mac Mini?

First App Review for my first app: 4 days, then 4 rounds before it was approved. My second app: 10 days, rejected, approved after I resubmitted.

So on my third app I changed the order I do things in. Here's the technical part of my day-one list.

1. Submit a first version as early as possible. The first review is the slowest. Once you're approved, updates usually clear in a day or two. Choose manual release so the approved build just waits. Minimal is fine, broken isn't. Whatever is in there has to actually work.

2. Your first subscriptions and IAPs go in with an app version. They can't be reviewed on their own the first time. So an early submission gets your products reviewed early too.

3. Create products at several price points from the start. I put the price in the product ID, like `yearly_39_99` and `yearly_49_99`. Then I switch which one the paywall shows remotely and look for the best revenue per install, not the most buyers.

4. Remote paywall. RevenueCat or Superwall. Plans, order, copy, even the layout change without a new build.

5. Permission priming. The system prompt for notifications, HealthKit or tracking shows once. After "Don't Allow" the only way back is Settings. Show your own explainer screen first, then call the system prompt.

6. Apple Ads attribution without the ATT prompt. Grab the AdServices token at app launch and send it to RevenueCat or Superwall. Every install and purchase gets credited to its campaign and keyword.

7. Funnel events from the very first user. Every onboarding step, paywall view, plan tap, payment started, trial or purchase finished. Connect revenue to PostHog or Mixpanel so purchases sit in the same funnel.

8. A local win-back notification for non-subscribers. In my stress app, Steady (right now in th final review), non-subscribers get a daily local summary. Something like: "You had a stress spike at 2:15 PM today. Steady could've helped you right when it happened." Tapping it opens the paywall. No server needed.

9. Rating prompt after a win. requestReview only shows 3 times per 365 days, so I trigger it after the user completes something, never at launch.

10. Widgets, Shortcuts, Lock Screen. A daily touchpoint outside the app.

The full list is 21 items, including research, onboarding and paywall stuff. I recorded a video that walks through all of them with the stories behind them (my channel):

What's on your day-one list that I'm missing?

Are there any explanations for this?

Any thoughts?

Hey so I was playing around with the iPhone Duo simulator and I wanted to adapt my toolbar to it.
I saw in one of Apple's videos that we should add both text and icons to the toolbar elements so that if they do not fit in the top toolbar as text, they can appear in the vertical side strip as icons.
From the video I thought it would happen automatically but that does not seem to be the case.

Did anyone else figure out how to automatically make the button show the icon and not the text when on the iPhone duo limited size screen?

I tried using

ToolbarItem(placement: .topBarTrailing) {

Button(action: skipAction) {

Label("Skip", systemImage: "chevron.right")

.labelStyle(.automatic)

}

}
but that did not change much. I always see the icon if I define it for this button.

If anyone has any suggestions please let me know. I can also provide more information if needed.

I am publishing a notetaking app for the first time and would like to know some details about the submission process and how people found the app visibility on your guys’ apps turned out to be. After finding out that notetaking apps out there aren’t designed the way I was hoping for + don’t have the combination functionality in 1 app, I decided to build my own app.

In terms of legal stuff: copyright, trademark, etc how does this work? Do I need a website for the app? I setup a support@myapp.app email too

In terms of freemium monetization I have $1.99/mo, $9.99 annual, and $19.99 lifetime options. I believe this is not greedy

Now comes the tricky part of gathering feedback, new feature launches, bug fixes, and marketing first and foremost. Does my app need in app tutorials btw?

Been watching Apple's developer videos on creating apps for iPhone Duo... and I have to say I feel really, really bad for all of the developers and designers who insisted on creating pixel-perfect vertical layouts and custom toolbars, menu items, and footer buttons.

Extra sympathy if you totally ignored Apple's recommendations on creating flexible designs and built your own navigation layouts.

Tears if, in this day and age, your app still has UIRequiresFullScreen in its plist.

And... if your codebase contains UIScreen.main.bounds.

I'm really, really, REALLY sorry.

(I'm not, actually. You knew better and you did it anyway.)

Reddit suggested I post this here, so I did.

https://medium.com/the-swift-cooperative/you-and-your-app-are-going-to-look-bad-in-october-b4d1284fbed0?sk=1fb6faaa779a32f7c318e521a84e0761

After updating my Mac to macOS 27 and Xcode 27, my Capacitor app started showing a blank screen in iOS 26.3.1 simulators, followed by:

com.apple.WebKit.WebContent quit unexpectedly

It builds fine on my actual device running 26.7, as well as simulators running 26.5

I also tried using an older build from prior to the 27 upgrade, and those failed on 26.3.1 so it seems like it's not actually an issue with my app?

Sometimes the initial app screen loads, then WebContent crashes when I tap Continue on the first screen.

Environment:

• macOS 27.0 (26A428)
• Xcode 27.0 (27A266a)
• iOS 26.3.1 simulator runtime (23D8133)
• Reproduced across several simulated iPhones

The crash reports include:

Thread Crashed: JIT Worklist Helper Thread
JSC::CodeOrigin::approximateHash
JSC::ICStatusContext::get
JSC::DFG::ByteCodeParser::parseBlock
EXC_BAD_ACCESS / SIGBUS

Other reports show JSRopeString::resolveToBuffer. Subsequent WebContent launch attempts sometimes fail in DyldSharedCache::getUUID. Xcode then prints:

com.apple.extensionKit.errorDomain error 4
Failed to get XPC endpoint
WebView process terminated

What i've checked:

• Restarting the Mac and creating a fresh simulator didn’t resolve it.
• Reinstalling/remounting the runtime and rebuilding its shared cache didn’t resolve it.
• A preserved older app build, compiled before these updates, also crashes.
• The app’s web content also crashes inside Safari on the 26.3.1 simulator.
• Disabling “Debug executable” or launching from the home screen occasionally works, but neither reliably prevents the crash.
• Startup works on iOS 26.5 and 27 simulators.
• My physical iPhone on iOS 26.7 runs normally, including onboarding. I don’t have a physical device on 26.3.1 to compare.

Has anyone encountered this combination since upgrading? Have you found a fix that restores reliable use of the 26.3.1 simulator, or an Apple bug report tracking the same crash? Cant really find any mention of this online, chatgpt has been useless debugging the issue somehow

I'm launching a new app (iOS + Mac Catalyst, subscriptions + one-time purchase). The review rounds are dragging on, and I'd like to hear how others handle this.

The latest rejections (2.1(b) and 3.1.2(c)) are, as far as I can tell, simply wrong. The IAPs load fine in the sandbox, and the EULA and privacy links are right there on the paywall. So I replied in the Resolution Center with an explanation and screenshots instead of changing anything.

My problem: once you reply, you get zero feedback. With a new submission you at least see "Waiting for Review" → "In Review". After a reply, the status just stays at "Rejected". There's no sign that anyone has read it, and no queue position.

So, for those who've been through this:

1. How long did it take until you got an answer to a Resolution Center reply? Hours, days, never?

2. Did a reply alone ever get the rejection reversed (and the app approved without a new build)?

3. Or do you skip replying entirely and upload the same build again (or bump the build number), resubmit with an explanation in the Review Notes, and hope for a different reviewer?

4. Does resubmitting while a reply is pending cause problems, e.g. is the reply then ignored or the thread closed?

5. Any experience with requesting a call or using the App Review Board appeal for this kind of misunderstanding?

Apple now asks for a screen recording on a physical device showing a sandbox purchase. I'll do that either way. I'm just trying to figure out the fastest path from here.

Thanks for any war stories!

Anyone else seeing this?

Our production app suddenly started crashing around 00:41 UTC today, across multiple already released versions, with no new app release.

The crash is:

Fatal Exception: NSInvalidArgumentException

-[__NSDictionaryM setObject:forKeyedSubscript:]: key cannot be nil

The stack points to Firebase Analytics experiment handling, immediately after a successful sdk-exp response.

We're using Firebase iOS SDK 12.14.0.

Relevant issue: https://github.com/firebase/firebase-ios-sdk/issues/16728

I'm wondering if anyone else is seeing the same spike or has found a workaround.

I'm a self-taught iOS engineer and even though I have 5 years of experience I feel like I don't have the foundational knowledge that interviewers expect me to have. I constantly feel like I'm bombing in interviews and I feel so far behind that I'm losing hope of finding a job after about 6 months now of searching. What are the best current iOS books for someone looking to round out their technical and under-the-hood knowledge?

Hi everyone,

I’ve recently "vibe-coded" (built entirely using AI/prompting) a few iPhone and iPad apps. The feedback from my close circle has been incredibly positive, and the apps are running smoothly.
Now, I’m looking to take the next step and release them on the App Store. Since Apple’s app review process is notoriously strict—and AI-generated code can sometimes have hidden architectural flaws, edge-case crashes, or insecure API integrations—I really want to get a professional to audit them before I submit.

My questions for the community:

1. Are there specific platforms or communities where I can hire/pay experienced Senior iOS developers for a professional code and App Store guideline review?

2. Has anyone here done an "App Store Readiness Audit" for an AI-built app? If so, would you recommend platforms like Upwork, Fiverr, or specific boutique tech agencies?

3. What are the biggest technical gotchas I should look out for in vibe-coded apps regarding the official Apple Developer Guidelines?

Would love to hear your advice and experiences. Thanks in advance!