已获批Binary能否提交更新？更新遭拒后能否发布原开发者版？

1. Can you publish the previously approved developer binary if the updated one gets rejected? #

100% yes. The already approved developer build stays valid unless the platform explicitly revokes it (which only happens in extreme cases, like if that build violates policies). If your updated submission gets turned down, you can still proceed to release the approved version without any hurdles—this is exactly why teams often keep approved builds as a fallback when working on tight deadlines.

2. Is rushing the UI update worth it for your 3-day release goal? #

This boils down to risk vs. reward:

• Rejection risk: If your UI changes are minor (cosmetic tweaks, no new features that touch restricted areas like payments or data collection), the odds of passing review quickly are high. But if you’re making major overhauls or adding functionality that might trigger policy checks, the chance of rejection goes up significantly.
• Launch priority: If the new UI is critical to your launch success (e.g., fixes a major usability issue, aligns with brand goals), and you can get it polished enough to meet guidelines in time, go for it. But if there’s any uncertainty, prioritize releasing the approved version first. You can always push the UI update as a post-launch patch once it’s fully reviewed. Missing your 3-day deadline is likely worse than launching with the older UI and updating later.

3. Can you submit updates to an already approved binary? #

Absolutely. Approved binaries aren’t a one-and-done deal—you can submit updates to them as often as you need. Each update will go through the standard review process, but the original approved build remains available for release until you replace it with a new approved version (or it’s revoked for policy reasons).

内容的提问来源于stack exchange，提问作者Zhen Liu