Tracking Review Status (In Review, Rejected, Waiting to Release)
After submitting a native app to the App Store / Google Play, you can track review status in real time from the relay router's admin screen. There's no need to check Apple's or Google's official screens (App Store Connect / Google Play Console) directly. Both platforms' status can be viewed side by side in a single screen integrated into the store admin.
This article covers what each status means, the action store owners should take next, and how to respond when a submission is rejected.
Opening the status tracking screen
From the store admin screen, open "Store App" → "Native App Submission." Apps that are in submission or already published are shown side by side in iOS / Android cards, with the current status, last updated date/time, and next action visible at a glance.
What each status means and the next action
Building
The relay router is currently building the app. This usually finishes in 10–30 minutes.
- Action for the store: none — just wait. Once the build finishes, it automatically moves to the next status
- Time required: typically 10–30 minutes, varying with the app's asset size
Preparing Submission
The built app is being uploaded to App Store Connect / Google Play Console, and the information required for submission is being filled in.
- Action for the store: none — just wait. Typically completes in 5–15 minutes
Waiting for Review
Submission is complete and the app has entered Apple's / Google's review queue. Actual review hasn't started yet.
- Action for the store: none — just wait. Depending on how congested Apple's / Google's queue is, this can take anywhere from a few hours to a few days
- Time required: iOS is typically within 24 hours; Android typically takes a few hours
In Review
Apple's / Google's reviewer is actively reviewing the app.
- Action for the store: none — just wait. The status will change to either "Rejected" or "Waiting to Release" partway through
- Time required: iOS typically takes 24–48 hours; Android typically takes a few hours to 24 hours
Rejected
The submission was rejected during review. The status tracking screen shows the rejection reason from Apple / Google along with the response plan prepared by the relay router support team.
- Action for the store: review the response plan shown on screen. In most cases, the relay router side makes the fixes needed for resubmission, so additional work for the store is kept to a minimum
- How to respond: click the "Resubmit" button to re-enter the queue with the fix applied
- If store action is required (e.g. updating the privacy policy text), the screen displays "Store action required" in red
Waiting to Release
The app passed review. Once the store clicks "Release," it will go live on the App Store / Google Play.
- Action for the store: click the "Release" button to publish. The store can control the exact timing
- Example uses: releasing to coincide with the start of a grand-opening campaign, or releasing after announcing it on social media
- You can also leave it in "Waiting to Release" indefinitely — there's no time limit
Released
The app is now downloadable by customers on the App Store / Google Play.
- Action for the store: return to day-to-day operation. Content updates such as announcements, menus, or business hours made from the CMS are reflected automatically (no resubmission needed)
- If a change requires altering the app's structure, such as adding a new feature, you can start an "Update Submission" from the status screen
Other statuses
- Preparing — a draft that hasn't been submitted yet via the submission wizard. You can resume editing anytime
- Update in Review — an update to an already-released app is under submission. Behavior is the same as the normal "In Review" status
- Removed — the app has been taken down from the App Store / Google Play. Re-publishing requires submitting again
Common rejection reasons and how to avoid them
The relay router's submission wizard is designed to comply with Apple Review Guideline 4.2.6, but that doesn't reduce the chance of rejection to zero. Here are the most common reasons and how to respond.
- Insufficient privacy policy — using the relay router's standard privacy policy avoids this. If you use your own policy, make sure it includes the required items (what personal information is collected, its purpose, and whether it's shared with third parties)
- Screenshots don't match the actual app — the wizard automatically captures screenshots from your live app, but depending on the timing of the capture, placeholder data may appear. Replace them with real data
- Incorrect store information — the store information on the App Store / Google Play (address, business hours, contact info) must match the store's actual registered information
- A feature doesn't work — before submitting, confirm that all features work correctly in the web channel. The native app provides the same functionality as the web channel
- Inappropriate category selection — choose a category appropriate to your business type (the wizard suggests one automatically)
Status change notifications
When the status changes, a notification is sent to the store admin screen roles (owner / store manager).
- Notification center on the store admin screen — shown in real time
- Email notification — emails are sent for major changes such as "Build Complete," "Review Started," "Rejected," "Waiting to Release," and "Released"
- LINE notification (optional) — if you've chosen LINE as a notification destination, it also arrives via LINE Talk
You can adjust who receives notifications and through which channels in "Notification Settings" on the store admin screen.
Differences in pace between iOS and Android
Apple and Google have significantly different review processes. Common patterns:
- Android is usually released first — Google's review typically finishes within a few hours, so Android tends to go live first
- iOS lags by half a day to two days — Apple's review is stricter and averages 24–48 hours
- iOS has a higher rejection rate — because Apple's review standards are stricter, there are cases where Android passes but iOS gets rejected. In most cases, this can be resolved with a fix related to 4.2.6
If you want to launch on both platforms at the same time, we recommend holding Android at "Waiting to Release" once it gets there, and releasing both simultaneously once iOS also reaches "Waiting to Release."
Past submission history
You can view the history of every submission made so far from the "History" tab on the status tracking screen. This includes rejected submissions, which can serve as a useful reference for resubmissions.