🐞 Known Issues
This page lists known bugs or unexpected behaviors that we are currently aware of in ulives. We are working hard to address these issues in future updates.
Please note that due to the App Store review process, fixes may experience some delays. We appreciate your understanding and patience.
If you encounter a bug not listed here, please report it via our feedback form or by sending an email to fb@ulives.io.
Current Status (v1.10.0):
- Current public version: v1.10.0 (2026-08-31)
- v1.10.0 is currently rolling out gradually on the App Store. If you haven't received the update yet, open the App Store, search for ulives, and open the app's detail page to update manually.
- If you encounter any problems, please submit feedback via Settings → About → Feedback, or contact us via our feedback form or fb@ulives.io.
- We have confirmed a couple of known issues in v1.10.0. Details are listed below.
If you'd like to learn more about our upcoming development plans, check the Development Roadmap.
v1.10.0
Custom Level Model Values May Cause Overflow and Crashes — When using custom level models, some larger values may cause numeric overflow and app crashes. We will relax limits and add safeguards in a future update.
Pending Cycle Popup Does Not Support Subtask Cycle Status — The pending cycle popup does not yet support handling subtask cycle status. If a task's subtask completion rule requires completing all subtasks first, this popup may not handle the cycle correctly. Workaround: Find the task in the task list, tap the card to open task details, and handle subtasks from the historical cycle section in task details.