ReedVerde brandmarkReedVerde
    Back to Blog

    Your App Won't Work Until Your Developer Accounts Do

    Reed VerdesotoReed VerdesotoDigital Systems Architect
    Your App Won't Work Until Your Developer Accounts Do, custom Subsplash blog by ReedVerde

    Your Subsplash App Can't Move Forward Until Your Developer Accounts Are Current

    If you need anything to work in your app — notifications, message alerts, new artwork, branding changes, TV app updates, bug fixes, or even the newest features Subsplash releases — there is one non-negotiable requirement:

    Your church must own and maintain its own Apple and Google developer accounts, and those accounts must be fully up to date and in good standing.

    There is no workaround. There is no secret path. This is simply how Apple and Google operate. And until your accounts are current, Subsplash cannot push updates, renew certificates, enable new features, or fix anything — no matter how urgent it feels.

    Why This Matters: You Are the "Business Owner" of Your App

    Apple and Google see your church as the official business owner of your app. That means you must personally: log in, accept all terms and agreements, resolve any billing or compliance issues, maintain an active developer account, and authorize Subsplash through that account.

    If your accounts are expired, suspended, or owned by Subsplash instead of your church, everything stops. Subsplash is effectively locked out. They can't publish updates, renew push notification certificates, or release new features until your accounts are compliant.

    Start with Google: The 2024 Policy Change

    Go to your Subsplash dashboard, visit Settings → Developer Accounts → Google. If your Google Play account shows as belonging to Subsplash instead of your church, you must create your own Google Play Developer Account immediately. Google changed its requirements in 2024, and every organization must now own its app. Subsplash cannot bypass this or fix it for you.

    Apple Made the Same Move in 2020

    It's rare today, but if your app somehow still sits under a Subsplash-owned Apple developer account, you must migrate to your own account as well.

    Once Your Accounts Are Good, Then Subsplash Can Help

    After your accounts are healthy, do two things: Request that Subsplash renew your push notification certificates, and request an app update in your Subsplash dashboard under Settings → App Store Info.

    Set Yourself Up for Success

    Put a reminder on your calendar twice a year to: log into Apple and Google, accept new terms, check your billing, and request an app update through Subsplash.

    Almost every app issue I see comes down to this one thing: developer accounts that aren't up to date. Keep your developer accounts healthy and you'll save yourself a world of frustration and delays. Subsplash can only move when you do.

    Originally published on reedverde.com