# Endless build errors

**URL:** <https://forum.cursor.com/t/endless-build-errors/88937>\
**Category:** Feedback\
**Created:** [May 8, 2025, 7:40pm UTC](https://forum.cursor.com/t/endless-build-errors/88937 "2025-05-08T19:40:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bl84](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bl84/32/44802_2.png) [@bl84](https://forum.cursor.com/u/bl84)\
**Post date:** [May 8, 2025, 7:40pm UTC](https://forum.cursor.com/t/endless-build-errors/88937/1 "2025-05-08T19:40:11Z")

</div>

Have been building some apps with Swift and Flutter… the rate at which Cursor causes build errors is extremely high. I haven’t been tracking, but I would say more than half of edits result in build errors. Then, after prompting Cursor with the error, it will often take several attempts to resolve the error, or just get completely stuck. It’s pretty frustrating and I would also say it’s a predatory business practice to count edits that result in build errors as “fast” requests. I could very easily write error-riddled code on my own.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 7, 2025, 7:40pm UTC](https://forum.cursor.com/t/endless-build-errors/88937/2 "2025-06-07T19:40:53Z")

</div>

Closed on June 7, 2025, 7:40pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
