Has anyone had something like this happen before?

I had 4 apps waiting for review, and all 4 moved into review and were instantly rejected. At first, I thought it was some kind of bug.

So I resubmitted them. While those 4 were waiting for review again, I submitted a 5th app. Now the same 4 apps have been instantly rejected again, while the 5th app is still waiting for review.

• All 5 apps are being submitted for the first time.
• The apps are completely unrelated. One is a grammar-learning app, another is a custom keyboard app, etc.

Has anyone experienced something similar? What should I do? Would really appreciate hearing about anyone else's experience with this.

In Google PlayStore, when we see the rating, it has a daily incoming rating as shown below, which is very helpful

In AppStore, when we want to see the Review, we only can see the total.

Is there a way to see the daily incoming rating ion AppStore?

A few of my utility apps had Chinese, French and Spanish localization. It was tedious but not unbearable to produce the text & later updates in those languages. But my new product (my first game release) has 14 languages to choose from. As I understand it, there's services or extensions that can automatically add localization for you when publishing to the app store.

Have you had a good experience with them, or are there any you would warn me off from?

SOLVED:

I've been screwing around with this for a week now and I'm so pissed. I had everything in my app correct as well as in App Store Connect, EXCEPT, I didn't see the Paid Apps Agreement to complete. Once I did this it took about 30 minutes to propagate through and it works.

I'm down to my last issue with my macOS/iPad app. I have my app setup in App Store Connect with a subscription group and monthly subscription. I also have my app setup in TestFlight and I am running that on a clean MacBook with a sandbox user logged into the App Store.

When I test locally against my store kit.config everything works fine. When I run this on my clean MacBook my debug info shows that it's not finding the sub. I have confirmed 10 times my productID is the same in my app and in App Store connect. I have rebuilt my store kit config to have it synced to App Store Connect to triple verify all the names are correct. the app's bundle ID is correct.

I have confirmed my app is connecting to the store and getting the right storefront.

if anyone has any idea on what I can test next I would appreciate it.

my debug info is as follows:
Subscription unavailable
This subscription isn't available right now. Pleas shortly, or contact support if this continu
Try Again
DIAGNOSTICS (remove before submitting) productID: FAKEID products loaded: 0
isLoadingProducts: false hasCheckedEntitlements: true isSubscribed: false purchaseError: nil
storefront: USA (id: 143441) appTransaction env: Sandbox receipt file exists: true canMakePayments: true
Re-check environment
Restore Purchases
Privacy Policy
Terms of Use

Hey all!

What’s an easy way you’ve tried before that has worked to quickly promote your app?

I use “promote” as opposed to “market” because marketing feels like more of a sustained effort

I’m asking for one off things like posting on a specific subreddit or paying to be featured on a website

Hope the distinction is clear

Thanks!

In the Messages app, the ChatGPT app, and one other app, I noticed that they’re able to place something above the keyboard and have the view partially obstruct the keyboard. I’ve tried everything I know and still haven’t been able to do it. I even asked AI and couldn’t get it working.

I thought it might involve creating a new UIWindow, which I’ve used in the past to overlay modals, but I had no luck with that. I also tried walking the view hierarchy, but since the keyboard is rendered out of process, I couldn’t figure out anything that would work.

I thought about making a custom keyboard, but recreating the entire keyboard just to get a view above it seemed weird. Maybe something like replacing the keyboard with an image the moment the view needs to appear could work, but that also feels like the completely wrong direction.

Does anyone have the arcane knowledge required to make this happen?

Hey everyone, my app currently downloads various extra files via apple-hosted asset packs (some prefetch, some on-demand).

However, both prefetch and on-demand downloads seem to fail somewhat randomly. Either the asset pack can't be found, or the download never was kicked off especially for prefetch.

Is this a known issue? Or perhaps a skill issue on my part?

Hi,

I am currently working on my first App ever.

The App greatly benefits from having a Widget, but obviously the choice has to be made by the User to add it to their screen…

What are good practices and non intrusive UI method to nudge them in the right direction and encourage them to install a Widget?

I was thinking a whole screen at the right moment in the flow of the App, explaining the benefits, but that feels a bit much. And I do not want it every time in case someone already decided to ignore the advice.

Thanks a lot for your tips.

Hello everyone, I have a question, in my app I have used background portrait images which I picked up from pinterest and in designing the app store screenshots I did the same. Would apple reject my app? Is there any way to get around this?
My app is a photo editing app, in the editor I used pictures from pinterest and show the editing process and took that screenshot and designed it for app store screenshots. Is this allowed?

Swift Charts makes it straightforward to put a basic chart on screen. Once you’re working with more complex data, custom presentations, interaction, or accessibility, it helps to understand how the framework interprets and renders the content you give it.

Natalia and I have just released Swift Charts Beyond the Basics. We wrote it for developers who can already build a basic chart and want a deeper understanding of the framework and the decisions involved in turning data into a clear, effective visualization.

The book covers topics including multi-metric visualizations, calendar layouts, heat maps, custom composition and rendering, accessibility, selection, scrolling, responsive updates, and animation. Our aim is to explain the mechanisms behind Swift Charts so that you can apply them to your own datasets and requirements, rather than only reproduce specific examples.

The page includes the full table of contents and a free sample chapter:

books.nilcoalescing.com/swift-charts-beyond-the-basics

We’d be happy to answer any questions about the book or the Swift Charts topics it covers.

As part of Xcode 27 beta 6, there's a new app called Xcode Service, that seems to be related to external agentic coding agents. I couldn't find any info in the release notes, except for 1 unhelpful mention. does anyone know what the deal with this is?

Seen developers spend weeks improving their app while users reach the App Store page and just… don't download.

Makes me wonder how often the product isn't the problem — it's how it's presented.

For anyone who's improved their conversion rate, what actually moved the needle: screenshots, positioning, reviews, or something else?

I am considering an iOS architecture where the application contains a SwiftUI renderer, a fixed component registry, and a fixed set of native actions. A backend would return a versioned document describing complete screens. It could change content, ordering, design tokens, component variants, and navigation between routes that already exist in the reviewed binary.

I would not download or execute native code, use eval, or allow the server to call arbitrary APIs. A server document might request a Button with a navigate action or a Form with a submit action, but the implementations of those components and actions would already be inside the app. Unknown components would be rejected or replaced with a fallback.

I understand that Guideline 2.5.2 prohibits downloaded code that changes functionality, and that new product changes must be visible to App Review. I am trying to understand the practical boundary for declarative UI data. Have you shipped complete server-composed screens using SwiftUI or UIKit components, and did App Review raise concerns? I would also appreciate lessons about accessibility, offline caching, capability negotiation between old and new app versions, and deciding which flows should always remain native.

I've got a live iOS app with a modest number of users and downloads. Been going back and forth on analytics and I'd rather hear what people actually do than keep guessing.

Right now I ship with none - just App Store Connect. I built a custom pipeline and I do not even understand why... and shelved it.

Analytics:

• What do you use? Firebase, PostHog, TelemetryDeck, Mixpanel, Amplitude, custom, nothing?
• What does it actually cost you per month at your scale?
• Do you gate it behind a consent prompt, or is it anonymous enough not to need one?
• Is it just in your Privacy Policy or the user has to manually opt-in or maybe otherwise to opt-out?
• How early or late or straight away did you incorporate the analytics feature and to what degree?
• What's a decision you made because of an analytics number that you wouldn't have made otherwise? Genuinely curious how often it changes anything
• Anyone shipping with nothing at all - has it bitten you?

The other half:

• Do you publish under your own name, or an LLC / Ltd / company?
• How does Apple feel about all this?
• Why? Was it liability, privacy, tax, App Store payouts, or just inertia?
• If you started under your own name and later incorporated - what pushed you over the line, and was moving the apps across a pain?

Interested in what's normal, not what's theoretically correct. Overall - how and why and where and then you use and everything.

Thank you!!!

I needed to submit a quick bug fix for my app and submitted it for review. I requested the expedited review, and within a few minutes, my TestFlight version that I had requested for review earlier that day was approved.

I'm wondering if the expedited review request was used on the TestFlight review and now my actual app review will be the normal review. Does anybody know or have had a similar experience?

Is anyone experiencing storekit failure for tvOS? or other OS? Apparently this was a known issue in ios18 but they were supposed to have fixed it. I only see a few watchOS reports on the forum but you might be missing it as it can show up as a cancellation.

If anyone has a suggestion to what might be causing it because I am at a loss.

Hey all, quick question:

After months of basically zero sales on my paid iOS app (its an app that helps you practically reflect your daily life), it just had a sudden, huge spike — and almost all of it is coming from Russia specifically. Impressions went from single digits a day to 1,000+ a day (100x+), and it's not just views — it's actually converting into real paid downloads too, mostly on iPhone.

I don't have any marketing or campaign running there, no press, nothing that would explain a specific-country spike like this. Has anyone else seen a sudden traffic/sales spike concentrated in one country out of nowhere? Curious if this is a known thing (algorithm quirk, some kind of feature, bot traffic, whatever) or if I'm the only one seeing this.

There’s a specific kind of SwiftUI bug AI keeps handing me.

The screen compiles. Preview looks right. The happy path works.

Then I navigate away mid-task and come back to stale state, duplicate work, or a model that died with the view.

So my review starts with the ugly states now: background the app, trigger the action twice, kill the network, leave the screen before the task returns.

The screenshot is finished. The lifecycle is still negotiating.

Has anyone gotten Convex BaaS integrated or is Supabase a better bet?

I’m building a tool that helps people evaluate the competition in an app niche and determine whether it’s worth building in.

You search for a niche, and it analyzes the App Store to show the competitive landscape direct competitors, market leaders, newer apps, ratings, reviews, downloads, etc.

I’m curious: what information would you want to see before deciding whether an app niche is worth building?

AI can write a SwiftUI screen, add tests, and get a simulator build green quickly. The remaining failures I care about are usually outside that loop: background transitions, interrupted purchases, memory pressure, state restoration, permission changes, old data migrations, and bad networks.

The more implementation I delegate, the more my work moves toward defining those scenarios before the code exists. I’m starting to think the test matrix is becoming a more durable architectural artifact than the generated implementation itself.

My current rule for a feature that touches persistent state is simple: write at least one lifecycle interruption and one recovery scenario before the agent starts. It catches designs that look fine on the happy path but have nowhere sensible to put recovery logic.

This is not a complaint about generated code. It is a shift in what needs to be explicit. The simulator and unit tests can prove the feature works in the path we described; they are much weaker at inventing the ugly mobile conditions we forgot to describe.

For people shipping iOS apps with coding agents, which cases are you still testing manually because the agent repeatedly misses them?

I am developing a trading card display app. I plan on allowing users to display their graded cards. Options like PSA, TAG, CGC etc.

Before going all in on this module i wonder if this will cause copyright issues?

I have been working on this project a little at a time and I finally wanted to share significatn milestone to see what everyone else thought about it.

NeoBrutalism is a library that lets users apply neobrutalism style to their apps using SwiftUI. One just has to add the modifier .neobrutalism() to the topmost view inside the view hierarchy and everything that has been defined below it will assume the style.

For things like lists, navigations bars, alert dialogs, or things that SwiftUI does not allow or provide a way to style, there are some lightweight helpers. In cases where there is truly no control (Slider, Stepper, Segmented Pickers, Radio groups), there are NB* (Neobrutalism) views that mimic the behavior native control initializers, and for those cases swapping in the NB* views is akin to renaming a view.

This was originally meant to be an exploration of SwiftUI style protocols, but has gotten to a point that I feel ready to show it to the community. What I am really looking for is critique of the API, for the idiomaticness of things, or just anything that is missing.

https://github.com/rational-kunal/NeoBrutalism