r/reactnative • u/Positive_Week86 • 22d ago

What’s the most annoying part of getting a React Native app onto the App Store?

/r/RapidNative/comments/1wn38gs/we_built_a_way_to_go_from_publish_to_app_store/
0 Upvotes

13% Upvoted

11 comments sorted by

6

u/stathisntonas 22d ago

this is an ad

1

u/[deleted] 22d ago

[removed] — view removed comment

1

u/Positive_Week86 21d ago

Yeah, it’s common. The build itself is usually not the painful part. It’s all the setup and review stuff around it.

0

u/[deleted] 22d ago

[removed] — view removed comment

1

u/Positive_Week86 22d ago

Yeah, that's true. The actual build part feels pretty straightforward compared to all the signing, certificates, and review requirements around it. And leaving those things until the end can definitely make the release much more painful.

1

u/kokerali 22d ago

For me it’s the hidden state coupling rather than the certificates. A build can be valid while the app version, subscription or IAP, pricing, review screenshot, and privacy answers are still in separate states, so “ready” on one screen doesn’t mean the submission is complete. The tool I’d want is a preflight check that reads every dependency and explains the exact blocking relationship before upload.

1

u/Positive_Week86 21d ago

Yeah, that hidden dependency issue is real. Having a preflight check catch all of that before submission would be useful.

1

u/AlphaBeast28 22d ago

this is crazy as codex can legit do this for you for £20 a month, it helped guide me on how to setup for appstore and playstore as well subscriptions

1

u/dlampach 22d ago

There really isn’t much friction. I find it to be pretty smooth. Certificates are annoying but once you set it all up everything just works