Start with one app and one boundary. That makes it easier to distinguish a missed block from an allowance, a different screen, or another active rule. The browser preview explains the controls; testing protection requires the installed Android app.
Coming to Google Play for Android. See availability.
1. Check whether the service is running
Open SwipeLess and check the blocking status on Home. A saved rule and a running service are separate things: the app can remember your boundary while Android’s Accessibility service is off or not responding.
Follow the in-app service check. If it sends you to Android Accessibility settings, find SwipeLess and confirm its access is enabled. Return to SwipeLess and check again before trying the feed. If access looks enabled but the service still needs attention, turn SwipeLess’ Accessibility access off and back on, then repeat the check. Settings names can differ between phones.
2. Match the rule to the screen
In Blocks, open the affected app. Check What closes, the allowance and the saved summary. Tap Save after editing. Then test the exact part you selected.
| Your setting | What to expect | What to check |
|---|---|---|
| Reels or Shorts | The selected feed closes. | Messages or an ordinary video staying open can be correct. |
| Minutes a day | Access remains while that allowance lasts. | Check today’s remaining time. |
| A few short turns | Brief visits are allowed within your plan. | Check remaining turns and the current visit. |
| Block the whole app | All parts of that selected app close. | Confirm the app itself was selected and saved. |
Nothing means no allowance. Use the feed versus whole-app guide if you are unsure which boundary you need. You can make an ordinary Blocks rule stricter at any time. You can loosen it only once every seven days per app or website.
3. Check Work and Schedules separately
If an app stays closed when you expect it to open, check active Work sessions and Schedules as well as Blocks. Each can protect the app independently. Ending one source does not remove another.
Selected apps remain blocked during a Work session’s manual pause and planned breaks. For a schedule that starts late, check its enabled switch, starting weekdays, time window and scheduled-alarm access. An overnight Monday 22:00–07:00 schedule starts Monday and ends Tuesday. Work and schedule edits remain freely available; they do not use the seven-day Blocks restriction.
4. Use the permission for the feature
Accessibility access runs blocking. Usage access is optional for Android screen-time readings; missing it does not, by itself, explain an open feed. Work no longer requests notification access or postpones notifications from selected apps. If already enabled, the optional listener only detects call/alarm categories for block recovery. Do Not Disturb and scheduled alarms have their own access.
Check the permission overview rather than enabling unrelated permissions. The app privacy policy explains what each feature reads and keeps on your phone.
5. Check app and browser differences
Feed blocking recognises supported screens. A new social-app version, another route into a feed, or a different language can change what is recognised. Compare your situation with the supported targets and dated check records; a past check is not proof that every newer version works.
For websites, check the domain or link saved in Blocks and try a listed browser. Chrome, Samsung Internet, Firefox, Edge, Opera and DuckDuckGo are listed as tested; Brave is unverified. Links inside another app and installed web apps may behave differently. See the website-blocking guide.
Send a useful report
If the problem remains, send feedback with your phone model, Android and affected-app versions, app language, selected boundary and exact steps. Include the browser for website problems. Say whether nothing blocked or a useful screen closed unexpectedly. A short recording can help; leave private messages, usernames and account details out.