Keeping your branded app live in the App Store and Google Play Store requires both Guidebook's work behind the scenes and a few things only your team can do. We handle the day-to-day — building updates, submitting new versions, renewing certificates — but there are aspects of your Apple Developer account that only you can manage. This article covers what we do automatically, what we need from you, and what to do when something needs your direct attention.
We'll automatically update your app
When your Guidebook subscription includes a branded app, you have access to any app-specific features we release. To update your app with new features or bug fixes, a new version must be submitted to Apple's App Store and Google's Play Store. We'll submit updates frequently each year, depending on how often you publish and attach new guides to your app.
Submitting a new version of your app does not affect the functionality or availability of its current version.
A few things will prevent us from updating your app:
- We don't have the correct access to your Apple Developer account
- There are pending agreements on your Apple Developer account (see below)
- Your Apple Developer Program membership has expired
- There are no published guides attached to your app
If we run into any issues updating your app, we'll let you know.
If you don't want us to update your app automatically, speak with your account manager or support@guidebook.com.
What we need from you
There are a few things on your Apple Developer account that need ongoing attention from your team. If they fall behind, we can't move your app forward, and in some cases your app may be removed from the App Store altogether.
Keep your Apple Developer Program membership active
Apple Developer Program memberships are renewed annually by your Account Holder.
If your membership lapses, your app is removed from the App Store immediately. It can take up to 24 hours to reappear in the store after the membership is renewed.
Until the membership is restored, we cannot submit updates or renew certificates on your account.
Keep your Account Holder current
The Account Holder is the person on your Apple Developer account whose name is registered with Apple. They hold ultimate authority on the account and are the only person who can accept Apple's agreements on your organization's behalf. The Account Holder must have the legal authority to bind your organization to legal agreements. Guidebook can never hold this role.
If your Account Holder leaves your organization, you'll need to go through Apple's transfer process to appoint a new one. See When your Account Holder leaves below.
Keep your Apple agreements up to date
Apple periodically introduces new agreements that your Account Holder must accept in App Store Connect before we can submit or renew anything. The three you'll encounter:
- Program License Agreement (PLA): Updated periodically. Until your Account Holder accepts the latest version, all submissions and certificate operations on your account are blocked. This is the most common reason an update is held up.
- Digital Services Act (DSA) declaration: An EU regulation requiring app developers to declare trader status before distributing in EU countries. This is a one-time declaration made by your Account Holder in App Store Connect. Without it, your iOS app is unavailable to users in EU countries.
- Paid Applications Agreement: A separate Apple agreement that lives in the Business section of App Store Connect. When pending, it can block submissions from progressing to be reviewed by Apple. Although your app does not have a cost associated, this agreement still has to be accepted but no payment information needs to be provided.
If any of these are blocking your account, we'll reach out to your point of contact.
Keep Guidebook's access in place
Guidebook needs to be invited to your Apple Developer team as either an Admin or App Manager with access to Certificates, Identifiers, and Profiles. If your team revokes or reduces our access during a security review or account audit, we'll reach out to request what we need to keep your app running.
Apple Wallet for Guidebook ID requires Admin access specifically. If we only have App Manager access, we cannot generate the Pass certificate needed for Apple Wallet. Contact support@guidebook.com to discuss.
When Apple needs to hear from you directly
Apple Support only engages with people whose names are on the Apple Developer account. Guidebook staff aren't named on your account, so we have no standing to contact Apple Support on your behalf, even with you copied in. When something requires Apple's involvement, the conversation has to come from your team.
This applies to:
- Apple Developer Program membership applications
- Account Holder changes
- Account recovery
- Verification document requests
- Any account-level issue Apple has raised
The most reliable route is to request a callback via Apple's Developer Support contact form. Callbacks usually resolve faster than email tickets.
When your Account Holder leaves
If the person who holds the Account Holder role on your Apple Developer account leaves your organization, you'll need to transfer the role to someone else before they can accept Apple's agreements or renew your membership.
Guidebook cannot initiate or facilitate this transfer. The incoming Account Holder must contact Apple themselves.
The steps your team needs to take:
- Identify the new Account Holder: Someone at your organization with the legal authority to bind your organization to legal agreements.
- Create an Apple ID for that person: Use their work email; the Apple ID should be personally tied to them, not a shared inbox.
- Contact Apple to initiate the transfer: Request a callback via Apple's Developer Support contact form. Apple will work directly with your team to verify identity and complete the transfer.
What to expect:
- Apple will likely request verification documents (such as business registration or government-issued ID).
- The transfer can take a few weeks.
- If a PLA, DSA, or membership renewal is pending while the transfer is in progress, submissions and certificate operations stay blocked until either the transfer completes or the outgoing Account Holder (if still reachable) accepts the pending items.
- Once the transfer completes, the new Account Holder should accept any pending agreements in App Store Connect immediately so we can resume submissions.
Request an app update when needed
If you'd like us to update your app outside the regular cycle, request an app update from your branding dashboard.
Before you submit your app, it's a good idea to review its branding and store listing information to ensure they are up to date. Once we start the update process, you won't be able to make changes to your app until the new version has been released.
You can continue to make changes and update your guide while your app is being submitted to stores. The guide attached must include enough content for Apple and Google to understand your app's value and use case.
Select Resubmit app for approval when you're ready to submit a new version. Your app will be added to our submission queue.
Guidebook support will then review your app, update your screenshots for the app store listing, and submit it for Apple and Google to review.
We recommend that you submit your app to us 10 days before you start promoting it to ensure enough time for it to be reviewed and approved. The majority of app submissions go live within a day to Google's Play Store and within 4 days to Apple's App Store.
If an app is rejected by Apple for any reason, they usually respond to appeals within a day. Google can take up to 7 days to respond to an appeal of a rejection.