Tutorial August 9, 2026

LINE MINI App Re-review: Control Approved and Reflected Releases

A verified LINE MINI App needs re-review when you change review-controlled console settings such as its name, privacy-policy URL, Published endpoint, scopes, linked Official Account, service-message templates, or business information. For an already published app, approval does not deploy the change immediately: the channel enters Approved until you select Publish changes, after which it becomes Reflected. If you do nothing, LINE automatically reflects the approved changes on day 31.

Key takeaways

Changes to review-controlled LINE Developers Console settings require re-review; ordinary code or content changes outside those settings do not automatically require it, but they must still follow LINE MINI App Policy.
A verified MINI App has separate Developing, Review, and Published internal channels, each with its own LIFF ID.
For an existing verified app, Approved is a release window. Publish changes moves the reviewed configuration to Published and changes the status to Reflected.
LINE automatically reflects approved changes at 9:00 AM JST on the 31st day if the button is not used within 30 days, including weekends and holidays.
A temporary Published endpoint replacement for legitimate maintenance is a documented exception; treat it as an operational fallback, not a substitute for re-reviewing a permanent change.

Which LINE MINI App changes require re-review?

LINE’s official re-review guide lists the console settings that reopen the review path. The important distinction is not whether a deployment contains code. It is whether the release changes a reviewed LINE Developers Console contract.

Area	Examples that require re-review	Release implication
Basic settings	Icon, name, description, email, privacy policy, terms, localization, linked Official Account	Freeze brand and legal changes into one review set
Web app settings	`shareTargetPicker`, consent simplification, Published endpoint, scopes, add-friend option	Do not enable production behavior before the reviewed settings are reflected
Business and contact	Service, developer, provider, and all contact information	Keep legal ownership and support contacts consistent
Service messages	Any template information	Continue using the currently published approved set until the replacement is reflected
In-app purchase	Information in the application tab	Coordinate the separate in-app-purchase review before verification review

A change that does not touch these console settings does not require re-review solely because application code changed. That is not a policy exemption: LINE can still require corrections if released content or creative violates the MINI App Policy.

This post starts after initial verification. For the first submission, use the verification review checklist. If the change is specifically a service-message use case, variable, or link, prepare it with the template review checklist.

Approved is a release window, not production

The submission guide documents two different post-approval flows:

Situation	What approval does	Operator action	Automatic boundary
First verification	Status moves from `Approved` to `Reflected` immediately	Enable search separately when ready	Search is enabled at 9:00 AM JST on day 31 if not enabled manually
Re-review of an already published verified app	Status stops at `Approved`; production remains on the current reflected configuration	Select Publish changes	Approved changes are reflected at 9:00 AM JST on day 31 if not published manually

The second row is the critical release-control boundary. Approval says the submitted change may be released; it does not mean users are already seeing it. Once Publish changes is selected, the Reviewed configuration is copied to Published and the channel becomes Reflected. LINE notes that the day-31 automatic transition can be delayed by one to two hours.

Release checklist from Developing to Reflected

Inventory the reviewed settings. Export or record the exact name, URLs, scopes, linked account, template set, and business details included in the request.
Keep the three LIFF IDs separate. LINE creates Developing, Review, and Published internal channels. Initialize each environment with its matching LIFF ID and test the Review URL that reviewers will open.
Test production dependencies without publishing early. Confirm redirects, privacy and terms pages, permanent links, service-message templates, and any add-friend or consent behavior against the reviewed configuration.
Record the approval timestamp and day-31 deadline. Include weekends and holidays. Do not treat the automatic release as an indefinite holding state.
Schedule the Publish changes action. Assign one owner, define a go/no-go check, and capture the status transition from Approved to Reflected.
Run a post-release acceptance check. Open the Published LIFF URL on a real LINE client, verify the expected name and settings, and confirm that existing customer-message intake remains healthy.

When Reflected is reached, the channel returns to Not yet reviewed for the next change cycle. New edits remain in Developing and do not alter the currently published verified app until another review passes and is published.

Emergency endpoint changes and rollback

LINE states that temporarily replacing the Published endpoint for maintenance or another legitimate reason does not require re-review and switches immediately. Use this narrowly: point to a controlled maintenance surface, preserve the previous endpoint, validate the user-facing response, and restore the reviewed service when the incident ends.

Do not use the maintenance exception to ship a permanent product, scope, identity, or template change. Those changes remain review-controlled. If in-app purchase information also changes, sequence its application carefully: LINE does not allow verification review to be submitted while the in-app-purchase application is under review, and it does not allow applying for in-app purchase during verification review.

Where UnifyPort fits

UnifyPort does not submit a LINE MINI App for review, change Approved or Reflected, copy settings between internal channels, or grant verified features. The official LINE process is the correct path for MINI App identity, discovery, service messages, Quick-fill, shortcuts, and in-app purchase.

UnifyPort addresses a separate operational path: receiving supported messages from a connected ordinary LINE account as normalized message.received events. If a webhook endpoint has a signing_secret, verify X-Device-Timestamp and X-Device-Signature against the raw request body before routing the message.

Keeping these paths separate lets a MINI App release proceed through LINE review without silently changing the customer-support intake contract. Start with the LINE authorization guide and verify the current boundary in the provider message-support matrix.

Limitations and trade-offs

The official review route is mandatory when a change affects reviewed MINI App settings or verified-only capabilities. An unofficial interface cannot accelerate approval, prevent the day-31 release, roll back a LINE console change, or turn ordinary account messages into MINI App service messages.

Conversely, a successful re-review proves LINE accepted the submitted configuration; it does not prove your deployment, deep links, monitoring, or inbound queue works end to end. Keep review status and operational readiness as separate release gates.

FAQ

What is the difference between Approved and Reflected?

Approved means LINE accepted the submitted change. For an already published verified MINI App, users continue seeing the current configuration until Publish changes is selected or the automatic deadline is reached. Reflected means the reviewed change has been copied to Published.

How long can approved LINE MINI App changes wait before release?

Up to 30 days. If you do not select Publish changes, LINE automatically reflects the update at 9:00 AM JST on the 31st day, including weekends and holidays, with a possible one-to-two-hour delay.

Does every code deployment require re-review?

No. LINE says re-review is not required for updates that do not involve review-controlled console settings. The released service must still comply with LINE MINI App Policy.

Can I temporarily change the Published endpoint during maintenance?

Yes. LINE documents a temporary endpoint replacement for maintenance or another legitimate reason as not requiring re-review and taking effect immediately. Keep the change temporary and maintain a tested restoration plan.

Do service-message template edits require re-review?

Yes. LINE lists all service-message template information as review-controlled. The currently reflected template remains the production contract until the replacement passes review and is published.

Next step

Build the release calendar from LINE’s official re-review guide and submission workflow. If the separate requirement is ordinary LINE customer-message intake, follow the UnifyPort LINE authorization guide.

Sources

Official LINE sources checked on August 9, 2026: