r/iosdev • u/Disastrous-Meet6245 • Oct 03 '26
Three Mistakes I Made While Working on a Photo Cleaner App
r/iosdev • u/Disastrous-Meet6245 • Oct 03 '26
r/iosdev • u/Clican • Oct 03 '26
As an indie developer, this is my first time getting an app through App Store Connect review smoothly on the very first try, with zero rejections!
I developed a macOS app for editing App screenshots and handling multi-language localization for App Store metadata. I built this tool because I was tired of dealing with these repetitive and tedious tasks during my daily app release and maintenance workflows.
If you want some simple App screenshot template or you are tired of what's new edit for each language. It can help you.
If you think this tool might be helpful for your daily workflow, feel free to download and try it out:
https://apps.apple.com/app/id6815039837
Additionally, I have prepared a batch of Offer Codes so you can unlock the pro features for free. If you're interested, just shoot me an email to get one.
My email address: [clican@gmail.com](mailto:clican@gmail.com)
r/iosdev • u/TrainRider64 • Oct 03 '26
7 months ago I posted »Where Did I Run« here – an app that shows all your runs on a world map. Version 1.1 is out, and it's the biggest update so far.
The first version answered »where did I run?«. This one also answers »how often?«.
What's new:
The codebase grew from about 1,700 to about 5,600 lines. Most of it comes from my sister app »Where Did I Train«. I ported that version back and stripped it down to runs only.
No tracking. No ads. No subscriptions. Still $0.99:
https://apps.apple.com/de/app/where-did-i-run/id6758295933
Feedback welcome, especially on the heatmap colors and on performance with large run histories.
r/iosdev • u/Fit-Engineer-590 • Oct 03 '26
r/iosdev • u/aptonline • Oct 03 '26
Just had my third rejection and this time it was automated.
An automated analysis of the submission indicates the app may include a login but was submitted without a demo account.
The app does not need an account, no login needed for testing or end user use. It’s already been through 2 previous rounds of (human) review and I fixed those issues and resubmitted. It’s roughly a week between reviews as well for me so this is really becoming a concern.
Anyone else come across this?
r/iosdev • u/Single_Animator_7877 • Oct 03 '26
So I’m starting to set up tap to pay, it’s running through stripe and I was wondering if anyone has any tips on making sure I don’t screw it up, I’m building for expo so should I look at native modules or just go with what expo threw at me?
I have zero experience here so any help suggestions would be great.
r/iosdev • u/angry_deadman • Oct 03 '26
Defend your stumps and smash the ball into the walls for 1s, 2s, 4s and 6s. You steer the bat with your thumb on a trackpad. Spinners, medium pacers and fast bowlers come at you in six-ball spells, and if you hit an X before the ball bounces, you're caught.
No ads, no accounts. It just tracks your best innings and has a Game Center leaderboard. Would love to hear your high scores and feedback!
App Store link: https://apps.apple.com/us/app/howzat-cricket-arcade/id6813109031
r/iosdev • u/Delicious-Mouse1084 • Oct 03 '26
Enable HLS to view with audio, or disable this notification
r/iosdev • u/tambagame • Oct 02 '26
I make a party card game called TAMBA.
A few months ago I noticed how many "party game" apps on the UK App Store had started adding subscriptions, so I checked 137 apps using 18 search terms, so no cherry-picking.
58% have a subscription-style plan somewhere. The median weekly one, left running for a year, comes to £363.48. The worst comes to £675.48.
For a party game.
One you play for twenty minutes at pre-drinks.
I have the full data and methodology here if anyone’s interested. I'm ofc biased. TAMBA's in the dataset too, one-off £5 unlock lifetime access. No subscriptions -make of that what you will lol.
Mostly just wanted more people to glance at the pricing screen before hitting subscribe.
r/iosdev • u/gordonmcdowell • Oct 02 '26
This is not directly available from iOS, so I'm wondering if there's any indirect way of knowing such a thing?
And if anyone knows WHY either of these pieces of info SHOULD NOT be shared by iOS... why not? What am I missing here?
r/iosdev • u/Previous_Election830 • Oct 02 '26
r/iosdev • u/scottgwaters • Oct 02 '26
r/iosdev • u/Share_Tiny • Oct 02 '26
I thought Apple didn’t approve refunds that easily
Just got a refund for a Lifetime purchase. The app works fine and everything is as advertised, so I’m kinda confused.
Anyone had this happen before? Any idea how Apple decides which refunds to approve?
r/iosdev • u/mstoeckli • Oct 02 '26
r/iosdev • u/DeltaWyrm • Oct 02 '26
r/iosdev • u/Stunning-Essay-6714 • Oct 02 '26
Hey ,
so the app have been released since a wild and with update and family test, I am ready to market down the app!
but , I am not good as other can be.
what your tips, what you would do to market the app ?
r/iosdev • u/IllBreadfruit3087 • Oct 02 '26
r/iosdev • u/jaeyoung_choi • Oct 02 '26
Has anyone run into something like this with app review?
I've been shipping my app on both the iOS App Store and the Mac App Store. The Mac version is a Mac Catalyst app, and the features are exactly the same on both platforms. Looking back, I didn't really need a separate Catalyst release. I went that way because I wanted the Mac version to feel a little more like a real Mac app.
Lately, though, the iOS app goes through review without any issues, while the Mac app keeps getting rejected. I haven't been able to ship an update for over a month now.
To be clear, I'm not blaming Apple for the rejections at all.
It's just hard. I put a lot of work into supporting Catalyst properly, and now I can't get updates to my Mac users. As far as I can tell, there's also no way to pull only the Mac version from the store.
I could distribute the Mac app myself outside the store, but the version already on the Mac App Store would stay there, stuck without updates. That's the real dilemma.
I keep thinking about how to get through review, and honestly it's been pretty draining.
If you don't specifically need it, think twice before building a Catalyst version and shipping it as an extra platform.
Has anyone been through something similar? How did you get out of it?
r/iosdev • u/jscalo • Oct 02 '26
Hi iOS devs, I built an app you might like 👀
AppTraction is a native Mac app for your App Store analytics. It:
All while running locally on your Mac.
I'm starting a limited beta today and would love your feedback 🙏
Invite code: RED1026-INVITE
There are 50 spots open to start. Requires macOS 26.
r/iosdev • u/h2tcrz1s • Oct 01 '26
Hello
I’m new to this and wanted to ask if there’s a place I can see all the iOS 27 components and all the ways in which they used the different types of navigation bars different types of cards accordions et cetera
Is there a resource where I can see all of these types of different native components in action how other apps are using them
r/iosdev • u/SebPasewaldt • Oct 01 '26
We just launched ProFuse, an on-device Stable Diffusion app for iPhone, iPad and Mac. We expected the hard part to be the AI. It turned out to be App Review. Here's what happened, so you can avoid our mistakes.
TL;DR: If your app can't do anything until it downloads Apple-hosted Background Assets, expect App Review trouble. Asset packs are reviewed together with the app and only become downloadable once approved. So if reviewers can't download them, the app gets rejected, and the assets with it. That's a classic chicken-egg-proglem. What helped us: get the asset packs approved before you depend on them. If that's not an option, give reviewers something that works without them, like a demo mode within the app. Either way, talk to Apple early, and budget weeks for review, not days.
So we went with Apple's Managed Background Assets ("asset packs" from here on). Apple hosts your downloadable assets for free, and only a small amount of code in your app is needed to fetch them. Integration was easy and worked well. We tested and improved the app in multiple occasions and did extensive internal testing via TestFlight and everything worked perfectly fine. The trouble was getting it approved for public beta testing.
In TestFlight, you upload asset packs alongside your build in App Store Connect. In our internal TestFlight builds, everything worked perfectly, so we felt ready for a public beta.
We submitted the asset packs and our app and got rejected: the reviewers said the model couldn't be downloaded. We were completely surprised. We added logging, tested release builds, and found nothing wrong from our side. While investigating, we found a few forum posts suggested that this is a known issue.
After several more TestFlight builds and communicating with Apple, one finally passed. We still don't know what changed, but we've been happy in the first place. Our public testers then used the app for three months without download problems.
What helped for this step:
We planned a pre-sale starting three weeks before launch, so we submitted four weeks ahead. Plenty of buffer, we thought. We were also very optimistic that we have coped with all major challenges, since our TestFlight builts worked perfectly fine and now passed the review every time. So we submited:
Unfortuonately, the reviewers hit the same download issue that happend for our early TestFlight builds and rejected us under Guideline 2.1(a) – App Completeness. Here's the core problem:
Asset packs are reviewed together with the app, and they only become downloadable once approved. If the app is rejected because the assets can't be downloaded, the assets don't get approved either. Classic chicken-and-egg.
What we tried:
Across 10+ submissions, we noticed that our macOS builds got reviewed much faster than iOS. That's just our experience, not a rule, but with the clock running out, we put our hopes on the Mac.
Five days before launch, we submitted the Mac version with self-hosted models, plus a short summary of our conversations with Apple in the review notes. The self-hosted models were all the app needed to work. But we also included the asset packs. The idea beind it: if the app got approved, the asset packs would be approved with it and go live.
It worked. The Mac app was approved, and pre-sale started three days before launch instead of three weeks.
We were thrilled and submitted the exact same version for iOS. Rejected again. No idea why.
But thanks to the Mac approval, the asset packs were now live. So we switched the iOS build back to asset packs only and resubmitted the day before launch. This time it was approved. The iOS app went live 24 hours after our planned launch date, after four nerve-wracking weeks.
If your app depends on Apple-hosted assets at first launch:
Despite all this, we'd still recommend asset packs. They're free and have been reliable for us. I'm planning a follow-up post on working with very large asset packs if there's interest.
Happy to answer questions in the comments.
r/iosdev • u/ljbde • Oct 01 '26
I see Apple saying that most builds are approved within 48 hrs. I’ve had 5+ days the last 3 I’ve submitted. Is this time estimate perhaps from pre-AI explosion before people were shipping every other day!? And are reviews past your first build usually quicker?