Your App Won’t Work Until Your Developer Accounts Do: The Critical Step Every Church Must Take

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
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. The process and instructions are here:
https://support.subsplash.com/en/articles/9370468-keeping-your-developer-accounts-up-to-date
Once you have your accounts, log in to both Apple and Google and make sure everything is current—agreements accepted, payments handled, no outstanding alerts.
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.
Request an app update in your Subsplash dashboard under Settings → App Store Info.
With those two steps done—and your accounts in good standing—your notifications, artwork updates, branding changes, features, and bug fixes can finally move forward.
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
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. No matter how much Subsplash wants to help, they simply cannot publish anything if your accounts block them.
Keep your developer accounts healthy and you’ll save yourself a world of frustration and delays.
Subsplash can only move when you do.
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
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. The process and instructions are here:
https://support.subsplash.com/en/articles/9370468-keeping-your-developer-accounts-up-to-date
Once you have your accounts, log in to both Apple and Google and make sure everything is current—agreements accepted, payments handled, no outstanding alerts.
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.
Request an app update in your Subsplash dashboard under Settings → App Store Info.
With those two steps done—and your accounts in good standing—your notifications, artwork updates, branding changes, features, and bug fixes can finally move forward.
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
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. No matter how much Subsplash wants to help, they simply cannot publish anything if your accounts block them.
Keep your developer accounts healthy and you’ll save yourself a world of frustration and delays.
Subsplash can only move when you do.
Posted in App Management & Digital Infrastructure
Posted in Subsplash, Apps, Updates, Notifications, Compliance
Posted in Subsplash, Apps, Updates, Notifications, Compliance
Recent
Your App Won’t Work Until Your Developer Accounts Do: The Critical Step Every Church Must Take
December 8th, 2025
Learning the Pipes: My API Journey to Better Serve Subsplash Clients
October 17th, 2025
Streamlined Sundays: How We Create Live and Sermon-Only Versions Each Week
October 6th, 2025
How to Build a Consistent Photo Rhythm for Your Church
September 23rd, 2025
Why Every Event Matters (and How to Keep Graphics Simple)
September 23rd, 2025
Archive
2025
September
October

No Comments