iPhone App Notifications Work Only When the Screen Is Unlocked
Notifications arrive in the app, but banners or lock-screen alerts do not appear. This guide separates focus or notification summary rules from lock-screen alert setting with a controlled test before recommending changes.
Send one test notification with the phone locked and another unlocked while recording Focus status. Start by review app notification options, Focus and scheduled summary without disabling unrelated privacy rules. Confirm success only when a permitted notification appears on the lock screen with the desired visibility setting.
Symptoms
Quick orientation: Notifications arrive in the app, but banners or lock-screen alerts do not appear. The purpose of this guide is to distinguish a local display or account problem from a failure in the operation itself. Delivery to the app and permission to present on the lock screen are separate decisions.
Start with observable behavior, not a guessed cause. A useful failing example is the exact action that produces this result: Notifications arrive in the app, but banners or lock-screen alerts do not appear. Record which account, device, file or session was active at the time. In parallel, identify a baseline that still works; here, the most revealing baseline is described below.
- Observed: Notifications arrive in the app, but banners or lock-screen alerts do not appear.
- Control case: Send one test notification with the phone locked and another unlocked while recording Focus status.
- Recovery target: A permitted notification appears on the lock screen with the desired visibility setting.
On phones, an app setting and the operating system permission, account or hardware routing can have separate effects. A feature that works in one app may not be available to another even on the same device.
Why It Happens
There are at least three plausible explanations. None should be treated as a confirmed diagnosis until the comparison produces evidence. They affect different points on the route from device hardware → operating-system permission → application feature → saved result.
- Focus or notification summary rules. This is most plausible when the failure tracks the affected item or state rather than every use of mobile devices. The crucial evidence comes from the original comparison: Send one test notification with the phone locked and another unlocked while recording Focus status. If that comparison changes the outcome, document the exact setting or input that changed before trying another fix.
- Lock-screen alert setting. Look for a mismatch between active device setting and permission scope. A setting shown as enabled in one place may not apply at the next layer. Delivery to the app and permission to present on the lock screen are separate decisions. Do not infer this cause merely because the interface displays a warning or stale preview.
- App push registration issue. This remains possible if both the clean control and affected case behave similarly or a working path stops after an update, policy change or new session. Check the appropriate product-status or permission records, then preserve evidence for official support rather than guessing at a hidden server condition.
If the first test reproduces the fault, record which stage of device hardware → operating-system permission → application feature → saved result was last confirmed healthy. That narrows responsibility more effectively than attempting unrelated resets.
Before Making Changes
Preservation rule: Do not expose sensitive message previews on a shared lock screen. Save a copy of any unique original, note the current account or device state, and keep the last successful sign-in, file, download or save location available. If the affected data belongs to another person or organization, check permission before using it as a diagnostic sample.
Choose an ordinary, harmless control case and note the date, device, software version and exact error wording if present. Do not change password, profile, router, cache, storage and application settings at the same time. Record which SIM, account, audio endpoint, storage location or permission is active before changing anything. Device-specific screens can move between software releases.
Problem-Specific Diagnosis
The discriminating comparison: Send one test notification with the phone locked and another unlocked while recording Focus status. Perform the comparison on one variable at a time; leave the working sample unchanged. Note whether the failure follows the account, the item, the device, the network or the viewer.
| Hypothesis | Targeted check | What the result means |
|---|---|---|
| Focus or notification summary rules | Send one test notification with the phone locked and another unlocked while recording Focus status. | A different outcome between the controlled examples raises the likelihood of focus or notification summary rules; identical outcomes do not confirm it. |
| lock-screen alert setting | Review app notification options, Focus and scheduled summary without disabling unrelated privacy rules. | If this reversible correction changes only the affected path, lock-screen alert setting deserves closer inspection. |
| app push registration issue | Compare the same app on a second device, inspect device notification logs if supported and test an authorized reinstall only after preserving data. | If the clean and affected examples still fail together, collect logs or official service evidence for app push registration issue. |
Follow the actual path: device hardware → operating-system permission → application feature → saved result. Mark the last stage that is visibly successful and the first that is not. For example, a completion indicator is not equivalent to an accepted upload, and a locally visible edit is not necessarily synchronized to its recipient. The same distinction applies to app cache or local file versus external result in this particular workflow.
Do not guess: If you can reproduce the condition only in one controlled example, preserve it for escalation. If both examples fail, stop modifying the original and look for a shared dependency or a service incident.
Start with the controlled comparison. Use advanced checks when the reversible route does not isolate the cause. Notifications arrive in the app, but banners or lock-screen alerts do not appear. Before changing anything, identify the correct account or device, the latest successful attempt and the one affected item. Save an ordinary working example and note whether a warning actually names focus or notification summary rules. Do not assume it does. Send one test notification with the phone locked and another unlocked while recording Focus status. Keep the original copy untouched and repeat the same steps on the working sample. Write down the first stage where the two outcomes differ, using the pathway device hardware → operating-system permission → application feature → saved result. Review app notification options, Focus and scheduled summary without disabling unrelated privacy rules. Change only the smallest supported setting or input necessary for this test. If the control example stops working, undo the change and preserve the original configuration. A permitted notification appears on the lock screen with the desired visibility setting. Test again after a normal refresh or reconnect and check the actual recipient, saved file, viewer or device endpoint. A progress badge or an editor preview does not count as final proof. Test whether focus or notification summary rules follows the affected item across a clean profile, alternative authorized device or supported workflow. Compare its result with the unchanged baseline rather than altering production data. Inspect the distinction between active device setting and permission scope. Check relevant event history, processing state, status notice or policy restrictions. Determine whether lock-screen alert setting can explain a difference between the two paths. Compare the same app on a second device, inspect device notification logs if supported and test an authorized reinstall only after preserving data. Use official logs or diagnostics only where available and authorized. If app push registration issue is implicated, capture the observed evidence before any higher-risk change. Summarize the symptom, the controlled comparison, the outcomes of the three hypotheses and the result against this pass condition: A permitted notification appears on the lock screen with the desired visibility setting. Give support only sanitized identifiers and timestamps; preserve the original and avoid destructive resets.Step-by-Step Troubleshooting
Document the iPhone App Notifications Work Only... failure
Compare: Send one test notification with the phone...
First safe fix: Review app notification options, Focus...
Verify: A permitted notification appears on the...
Isolate: Focus or notification summary rules
Investigate: lock-screen alert setting
Trace: app push registration issue
Escalate with iPhone App Notifications Work... evidence
Solution Checklist
Common Mistakes to Avoid
- Turning off all Focus modes without checking the affected app's rule. The original comparison should be checked before committing to that conclusion.
- Changing too many variables. The result of send one test notification with the phone locked and another unlocked while recording Focus status. becomes uninterpretable if several account, network and application settings are changed together.
- Ignoring the preservation rule. Do not expose sensitive message previews on a shared lock screen. Reinstallation, factory reset or cache removal may destroy unsynchronized local data or useful diagnostic records.
- Trusting an intermediate success indicator. Delivery to the app and permission to present on the lock screen are separate decisions. The definitive result is the separate pass condition below, not a spinner disappearing.
How to Verify the Fix
Run the original control again under the same conditions and compare the result with your notes. Send one test notification with the phone locked and another unlocked while recording Focus status. Do not change the control case, account and network between the before and after observations.
- Function: A permitted notification appears on the lock screen with the desired visibility setting.
- Persistence: Repeat the successful action after a normal app reload, reconnect or new session that is appropriate for mobile devices. This tests whether a temporary on-screen state was mistaken for a durable correction.
- Destination: Inspect the recipient, public viewer, saved file, second device or other authoritative destination when the operation has one. A locally visible confirmation alone may be incomplete.
- Side effects: Confirm the previously working comparison still behaves correctly and that no security setting, unrelated account or unique file was lost.
If the initial symptom recurs, note whether it returns immediately, after switching devices, after the app sleeps, or after the next synchronization. Those timings point to different remaining causes.
If the Problem Continues
The next proportionate investigation is: Compare the same app on a second device, inspect device notification logs if supported and test an authorized reinstall only after preserving data. Perform it on a duplicate, clean test profile or authorized diagnostic session where possible. If it indicates app push registration issue, use the official product support route or an administrator who controls the relevant layer rather than making unsupported changes.
A useful support report includes the exact title of this problem, device and app versions, an approximate timestamp and time zone, the outcome of Send one test notification with the phone locked and another unlocked while recording Focus status., the result of the reversible first correction, and what was observed after the advanced comparison. Redact private conversations, personal identifiers, purchase details, access tokens and security codes.
Prevent Recurrence
After a successful correction, keep a short private note showing what changed, why it was changed and which comparison confirmed it. The saved baseline for this case is: Send one test notification with the phone locked and another unlocked while recording Focus status. The long-term observable goal remains: A permitted notification appears on the lock screen with the desired visibility setting.
Before the next relevant app update, account migration, accessory change or network replacement, protect local copies or recovery methods, and confirm that active device setting, permission scope and app cache or local file remain configured for the intended use. Delivery to the app and permission to present on the lock screen are separate decisions. If the problem returns, repeat the same baseline test before making a new change.
FAQ
Can focus or notification summary rules cause this even if the rest of the service works?
Yes, it is a plausible cause, not a certainty. The meaningful distinction is whether the affected action differs from the working control. Send one test notification with the phone locked and another unlocked while recording Focus status. If the same cause cannot explain both observations, move to the next hypothesis rather than forcing a reset.
Is reinstalling the app the fastest solution?
Usually not the best first test. Do not expose sensitive message previews on a shared lock screen. Check the non-destructive comparison and try: Review app notification options, Focus and scheduled summary without disabling unrelated privacy rules. Reinstallation is appropriate only after you have verified that local data and access can be restored.
How can I tell whether the fix really worked for mobile devices?
Look for this observable result: A permitted notification appears on the lock screen with the desired visibility setting. Repeat it from the appropriate destination or second session. A status badge or partial preview should not be the only evidence.