Help for owners
Another company changed their service and my app stopped working
Short answer
Your app depends on outside services, and when one changes how it works, the app can break without any change on your side. Find out which service, check its status and announcements, and send your developer the exact error. Do not change keys or accounts yourself. The fix is usually a small update to the integration.
Does this sound like your situation?
- A feature that worked yesterday fails today and nobody touched the app.
- Payments, maps, shipping rates or logins stopped working.
- I got an email from a service about a change, a retirement or a new version, and ignored it.
- The app works in some regions or for older users only.
- My developer says the other company changed something.
Why does this happen?
Services release new versions and retire old ones
Outside providers change their interfaces over time. An app built against an older version keeps working until that version is switched off or its behaviour changes.
Some providers pin you to a version, others do not
Stripe, for example, states that its monthly releases have no breaking changes and that twice a year a major release starts with an API version that contains breaking changes. Upgrading to a major release can require changes to an existing integration. Your account keeps a default version until you upgrade it.
Confirmed by docs.stripe.com
Notices went to someone who left
Change announcements go to the email on the provider account. If that is a former developer or an unwatched inbox, nobody on your side saw them.
Keys, accounts or plans expired
Sometimes nothing in the interface changed. A key was revoked, an account was suspended or a plan limit was reached, and the service rejects every call.
Nothing tests the integration regularly
Without a scheduled check, the first test is a customer using it.
Technical detail: OpenWeatherMap returns 401 Unauthorized in a Flutter app
What can I do about it today?
- Name the serviceAsk which outside service the broken feature uses: payments, maps, email, shipping, login. The error text usually names it.
- Check the provider's status page and your inboxLook for the provider's status page and search your email, including spam, for notices from them in the last months.
- Send the exact error to your developerA screenshot with the time and what you clicked is enough. Do not paraphrase it.
- Do not regenerate keys or close accountsReplacing a key in a hurry can break other parts that use it. Leave provider accounts as they are until the cause is known.
- Make sure you own the provider accountsCheck that the accounts are in your company's name with an email you read. If the developer's name is on them, ask for access.
When should I bring someone in?
- The broken feature takes payments or bookings.
- The provider says the old version is retired and you have no developer.
- You cannot get into the provider account.
How do I handle it?
- Reproduce the failureI call the service the way your app does and read the answer, to see whether it is a change, a key or an account problem.
- Read the provider's change notesI check the provider's official changelog and upgrade guide to find what changed and what the new version expects.
- Update the integration in a copyI change the integration, test it in the provider's test mode and deploy after a backup, with a tested rollback.
- Set up a watchI add a scheduled check of the integration and list provider notices to a shared address, so a retirement notice is not missed again.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can the provider just break my app like this?
Providers can change or retire versions. Good ones announce it first, which is why notices must reach a mailbox someone reads.
Do I have to upgrade to the newest version?
Not always. Some providers let you stay on a version for a while. I check the provider's documentation for what it allows.
Will the fix be big?
Often it is a small change. If the provider removed a whole feature, I tell you so in writing before any work starts.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
Webhook signature verification failed. Err: No signatures found matching the expected signature for payload.Stripe webhook: no signatures found matching the expected signatureInvalid API keyOpenWeatherMap returns 401 Unauthorized in a Flutter appError 400: redirect_uri_mismatchGoogle sign-in stops with Error 400: redirect_uri_mismatch