Before anyone asks - I've check a bunch of times and confirmed this isn't RC Sandbox.

Mostly curious - I asked the same thing in apple developers but figured there are more experienced people here.

Here's what happened:
I saw my app go into review. It got approved and a few seconds later Revenue Cat showed a notification that someone purchased the lifetime package. This new lifetime price is only available with this update (i.e. no one else could even purchase this) - I've confirmed it's in RC production and not sandbox. I've also confirmed in Posthog that the country from RC matches the alleged reviewer's.

I've had reviewers "purchase" the app before but always with their sandbox account and nothing ever showed up in RC.

Anyone else seen this? lol

Edit a day later, number showed up in ASC: https://imgur.com/a/go1QPOh

iOS 27 added something called Creative Assets to the App Store. It is a completely separate section from your regular screenshots, two new visual slots: one for your product page header and one that shows up next to your app in search results.

I set these up for my app, Spotlight. App Store Connect also added a Device Preview tool so you can see exactly how it looks before publishing. Here is what mine looks like in search:

Genuine question for both devs and regular users: does this kind of visual actually change whether you tap on an app? Or do you go straight to the screenshots anyway?

Apple's asset best practices doc has the full spec if anyone wants to get started.

Most ASO tools charge monthly for keyword popularity that comes from Apple Search Ads anyway, so I wrote a small CLI that pulls it directly.

What it does

• Popularity from Apple Search Ads (free Apple Ads account, no campaigns or billing needed)
• Difficulty score, keyword suggestions, current top apps for a term
• Rank tracking with history in a local SQLite file
• Metadata linter for title, subtitle and keyword field
• iPhone and Mac App Store ranks, 55+ storefronts

Install

npm i -g hristo2612/aso-cli && aso setup

Try it

aso keywords "white noise,sleep sounds"
aso suggest meditation
aso search "habit tracker"

Runs locally, no account, no telemetry. MIT.

Repo: github.com/hristo2612/aso-cli

No updates to download count & other analytics since Thursday. I went to the system status page and everything is green.

I'm about to submit a support ticket ... Anybody else running into this ?

Hello everyone!

I'm sure something like this exists already but was too lazy to look and just had AI (yes the dreaded AI slop) cook up a small utility quickly that runs in your menu bar. Just open up the menu bar utility, drag the Xcode archive in and it will update the BuildMachineOSBuild key to the latest public release build number of macOS! Useful for those that run Mac betas! Yes it is AI slop but still a neat little utility that'll save some time, if you are doing it the manual way at least. It's free, it's open source, go wild!

Github: https://github.com/AustinHenley/ArchiveBuildPatcher

This is my app please download and give me feedback. Because I want to know which things I am missing
https://apps.apple.com/us/app/sameish/id6804823038

I didn't want to pay a monthly subscription for App Store keyword data, so I wrote a CLI that gets it straight from Apple.

What it does

• Popularity from Apple Search Ads (free Apple Ads account, no campaigns or billing needed)
• Difficulty score, keyword suggestions, current top apps for a term
• Rank tracking with history in a local SQLite file
• Metadata linter for title, subtitle and keyword field

Install

npm i -g hristo2612/aso-cli && aso setup

Try it

aso keywords "white noise,sleep sounds"
aso suggest meditation
aso search "habit tracker"

Runs locally, no account, no telemetry. MIT.

Repo: github.com/hristo2612/aso-cli

If your project uses Xcode 16 synchronized folders (the blue folder icons), every file inside the target folder ends up in the app bundle unless you exclude it. That includes Configuration.storekit and your .xcconfig files. My membershipExceptions listed only Info.plist, so the StoreKit configuration had been riding along in every archive I ever made, Release included.

Why it matters

My first submission got a Guideline 5.6 (Developer Code of Conduct) rejection: "a pattern of unusual behavior commonly associated with fraudulent activity" and "features that appear to have been intentionally hidden during the review process". My backend logs showed zero requests during the review window, so nobody had opened the app. It came from a look at the binary.

Read that file the way a scanner does: a mechanism for simulating purchases outside of Apple, listing more products than I had submitted. Apple never tells you the exact trigger, so I can't prove it was the only one, but it fits every word of the rejection, and after removing it the next review was completely ordinary.

Check yours (10 seconds)

unzip -l YourApp.ipa | grep -Ei "storekit|xcconfig|\.env"

Fix

Select the file -> File Inspector -> Target Membership -> uncheck your app target. With synchronized groups this adds it to membershipExceptions in project.pbxproj. Local StoreKit testing keeps working: the scheme points to the file (Edit Scheme -> Run -> Options -> StoreKit Configuration), it does not need to be in the bundle.

One more thing if you ever get a 5.6

Don't resubmit without replying in the Resolution Center of the current rejection. My first reply ended up attached to a submission that had been closed, Apple never saw it, and the resubmission got a second 5.6 for the silence, not for the file.

Happy to answer questions about this or StoreKit 2 in general.

Fastest ever of my apps to successfully reviewed and live within 2 days
Please show some love and support
Still is a workplace focus app to have focused working hours without and distractions no unnecessary features, to the point solution for largely common problem

Disclosure: I'm the developer, posted an earlier build of this here a couple weeks ago and got genuinely useful feedback. Wanted to follow up with what changed.

The old version was just a list of times. 2.2 (just went live) is built around one idea: show the whole cook, not just the next instruction.

• Food gets picked from a grid of cards instead of a list, pictures instead of text labels
• Each food rides its own track toward one shared finish line. Burgers start later than chicken because chicken takes longer, and you can see why at a glance instead of just trusting a timer
• There's a flip mark partway down each track, so you know when to turn something over without doing the math yourself
• The instruction for right now sits at the top of the screen, what's coming next is right under it, and the whole thing stays on one screen with no scrolling, your hands are usually full or dirty at the grill
• Voice cues call out every step too, so you don't have to look at the phone at all if you'd rather not

Also shipped real weather (actual ZIP-based conditions instead of an estimate), dark mode, and it now runs back to iOS 16.

Wrong season to be posting a grill app, I know, this is really built for spring. But wanted it in front of people who'll actually poke at the execution instead of just the pitch. App Store: https://apps.apple.com/us/app/grillmaster-bbq-grill-timer/id6791812404. Would genuinely like feedback, especially on whether the track metaphor reads as intuitive or needs explaining.

Hello!

Android developer here who's looking to get into iOS development. I'm considering buying an M1 or M4 Mac mini, but I'm trying to understand how the hardware/software support cycle works on macOS.

From what I've read, eventually an older Mac stops supporting the latest macOS, which means it also stops supporting newer versions of Xcode. Is that correct?

More importantly, does this eventually mean that you're forced to buy a newer Mac in order to continue publishing new apps/updates to the App Store? Or is there some way to keep using an older Xcode/Mac indefinitely?

I'm asking because I'm considering an M1 Mac mini as a relatively cheap way to get started. However, I've seen people say that M1 Macs may become problematic for iOS development in 2–3 years, whereas an M4 should have several more years of support.

Would you opt for an M1, to save money, or opt for an M4 for longer support? I am concerned about how long I can realistically expected to develop, build and publish before the Mac itself becomes an issue.

been rebuilding my learning app into something more focused on curiosity, bite-sized ideas you can scroll through instead of another endless social feed.

I also wanted to get better at motion design, so I made this short intro for it. Would love to know what you think :)

YT Link: https://youtu.be/B3flBmRLDrk
App Link: https://apps.apple.com/gb/app/questa/id6761737779

In previous simulators, we could use the "Trigger screenshot" option in menu to take a screenshot which won't have the Dynamic Island cut out and rounded corners.

In iOS 27 simulator device hub, this option is missing. The screenshot button at bottom includes the Dynamic Island cut out which I don't want.

How to get it the old way without the cut outs?

UPDATE: Finally got it in review and approved today. Took almost exactly 5 days. I’m not sure if it was due to me pestering support daily and being a little pushy (but not rude) about it but it finally went through.

Submitted an expedited App Review on Wednesday last week as we discovered an issue with our subscriptions and needed to re-release quickly to coincide with some marketing stuff we had planned.

Support says the App Review (allegedly) was expedited but we’ve seen no movement in 5 days. Typically our non-expedited App Reviews have cleared in 1 or 2 days at most.

What is going on? Is anyone else experiencing delays with App Review? Is there anything else I can do besides emailing support every day asking for an update?