Usage limits do not work
We understand how confusing and frustrating it can be when AppBlock says your usage limits are reached, even though you haven’t used the app much, or at all. We’ll try to explain what’s happening and what you can do.
🔄 First, try refreshing your blocking settings
Sometimes, usage limits might be off by a few seconds due to how quickly (or slowly) the system reports app usage. Before jumping to other conclusions, try refreshing your blockings manually in AppBlock. It might solve the problem right away.
For AppBlock version 3.8.0 and newer:
- Open AppBlock: Launch the AppBlock app on your device
- Go to the Blocking tab: Tap on the “Blocking” tab within the app
- Tap the refresh icon in the top-right corner
For AppBlock version 3.7.0 and older:
- Open AppBlock
- Go to the Blocking tab: Tap on the “Blocking” tab within the app
- Pull to refresh: Swipe down on the screen to refresh process (you’ll see a message “Blocking refreshed”)
⚠️ Still not working? It might be a system issue on iOS 26 / iOS 18
Starting with iOS 26, and also on iOS 18 (due to shared developer tools), we’ve observed a bug in the system’s reporting of app usage. The system may say the limit has been reached even if you haven’t actually used the app much, or at all.
AppBlock doesn’t have access to your actual screen time due to Apple’s privacy restrictions. Instead, we rely on the system to tell us when an app was used, and unfortunately, that data may currently be inaccurate.
🛠 What you can try:
Our developers tried their best to change whatever is possible from our side and have implemented several updates in version 4.6.6 to improve how usage limits work. Please make sure your app is updated to this version (or later).
If you’re still experiencing issues after updating:
- Try using only one usage limit at a time, especially if you have multiple overlapping ones
- Consider switching to the “Open Limit” feature, which doesn’t rely on usage time and may be more stable
We’re actively monitoring the situation and exploring possible workarounds. But ultimately, a permanent fix will need to come from Apple in a future iOS update.
💬 Still have questions?
If this issue affects you and you’d like us to take a closer look or offer help specific to your case, don’t hesitate to contact our support team. We’re here to help!
