Problem with Buildprint issue checker

Bugs
1

Ran into a bubble platform issue which has prevented any work on my app for 3.5 weeks now. It was escalated to engineering on August 24.

I have been unable to get any assistance, support, or status (only thank you for your patience, which is long since gone).

In the meantime, they are expecting me to pay for my subscription which I am not willing to do under the current circumstances.

Anyone else running into anything like this? If so, how did you get support and resolution? I have been happy with bubble up to this point.

2

What issue have you run into? If you share more details, someone here will be able to help you. You should detail what you observed, what you expected, and what you’ve tried so far.

3

Part 1 - core finding:

  • Development branch is the affected branch; Live remains untouched.
  • BubbleScript was disabled in the supplied evidence.
  • Bubble recorded the History restoration, but the resulting branch is internally inconsistent.
  • Bubble reports 81 issues, while the Buildprint branch snapshot preserves only 43 issue records and omits some contradictory navigation warnings.
  • The branch snapshot still consistently defines My Space and Member Profile as User pages, Board Detail as Board, Prayer Requests as Prayer Request, and Story Reader and Search as Post.
  • Therefore, repairing individual links, page types, workflows, uploaders, searches, or layout warnings is unsafe. The evidence points to incomplete or mismatched Bubble dependency metadata—not 81 independent configuration mistakes.
4

Part 2 - After restoring the Development branch to August 21, 2026 at 15:23:35 through Bubble History, Bubble’s issue count increased from 21 to 77. One controlled correction—setting My Space’s Type of content to User—increased it again to 81.

Bubble now reports contradictory type requirements. For example:

  • Some My Space navigation actions require User data.
  • Other links to the same page say User data should be text.
  • Member Profile is configured as a User page, and its links correctly send Users, but Bubble still says those links should send text.
  • Similar false type conflicts affect Board, Post, and Prayer Request pages.

The restored branch also contains apparently stripped or incomplete configuration affecting:

  • Toolbox Server Script parameters
  • Repeating-group child positioning
  • Advanced search constraints
  • File attachment targets
  • Image expressions
5

Isn’t this a Buildprint issue, not a Bubble issue? Announcing Buildprint AI: Build on Bubble with Claude Code and Codex 🎉

If you contact get in touch through Buildprint’s support form, I’ll be able to help you out…

6

Thanks George, will do