Can we access your project?
Current Behavior
Title: Server-side compileDslApp validation regression — byte-identical project source went from [OK] to [FAIL] with no project change
Project: rada-pbljmh
Summary: A project that validated and shipped successfully on 2026-06-06 now fails compileDslApp validation on 2026-06-07/08 with the exact same source (byte-identical) and the same build (36ba76e6) — no project/source change in between.
Evidence:
Run history: [OK] compileDslApp 2026-06-06 12:30 → [FAIL] compileDslApp 2026-06-07 22:35 (and persisting 06-08), same build.
Source byte-identical to the shipped archive (verified).
5 validation errors, all on one Button (CatSaveButtonSubCat): "Conditional execution for action is improperly set" ×2 (an If whose predicate is a CustomFunction), Field update value "not properly set" ×1, Field "not properly set in Database action" ×2 — on a chain that compiled & ran fine the day before.
Impact: Blocks all new pushes; the previously-shipped build runs fine.
Ask: Was there a server-side validator change around 2026-06-07 affecting If predicates that call a CustomFunction inside a Button onTap chain? Please advise / fix.
Expected Behavior
Title: Server-side compileDslApp validation regression — byte-identical project source went from [OK] to [FAIL] with no project change
Project: rada-pbljmh
Summary: A project that validated and shipped successfully on 2026-06-06 now fails compileDslApp validation on 2026-06-07/08 with the exact same source (byte-identical) and the same build (36ba76e6) — no project/source change in between.
Evidence:
Run history: [OK] compileDslApp 2026-06-06 12:30 → [FAIL] compileDslApp 2026-06-07 22:35 (and persisting 06-08), same build.
Source byte-identical to the shipped archive (verified).
5 validation errors, all on one Button (CatSaveButtonSubCat): "Conditional execution for action is improperly set" ×2 (an If whose predicate is a CustomFunction), Field update value "not properly set" ×1, Field "not properly set in Database action" ×2 — on a chain that compiled & ran fine the day before.
Impact: Blocks all new pushes; the previously-shipped build runs fine.
Ask: Was there a server-side validator change around 2026-06-07 affecting If predicates that call a CustomFunction inside a Button onTap chain? Please advise / fix.
Steps to Reproduce
Title: Server-side compileDslApp validation regression — byte-identical project source went from [OK] to [FAIL] with no project change
Project: rada-pbljmh
Summary: A project that validated and shipped successfully on 2026-06-06 now fails compileDslApp validation on 2026-06-07/08 with the exact same source (byte-identical) and the same build (36ba76e6) — no project/source change in between.
Evidence:
Run history: [OK] compileDslApp 2026-06-06 12:30 → [FAIL] compileDslApp 2026-06-07 22:35 (and persisting 06-08), same build.
Source byte-identical to the shipped archive (verified).
5 validation errors, all on one Button (CatSaveButtonSubCat): "Conditional execution for action is improperly set" ×2 (an If whose predicate is a CustomFunction), Field update value "not properly set" ×1, Field "not properly set in Database action" ×2 — on a chain that compiled & ran fine the day before.
Impact: Blocks all new pushes; the previously-shipped build runs fine.
Ask: Was there a server-side validator change around 2026-06-07 affecting If predicates that call a CustomFunction inside a Button onTap chain? Please advise / fix.
Reproducible from Blank
Bug Report Code (Required)
I
Visual documentation
Title: Server-side compileDslApp validation regression — byte-identical project source went from [OK] to [FAIL] with no project change
Project: rada-pbljmh
Summary: A project that validated and shipped successfully on 2026-06-06 now fails compileDslApp validation on 2026-06-07/08 with the exact same source (byte-identical) and the same build (36ba76e6) — no project/source change in between.
Evidence:
Run history: [OK] compileDslApp 2026-06-06 12:30 → [FAIL] compileDslApp 2026-06-07 22:35 (and persisting 06-08), same build.
Source byte-identical to the shipped archive (verified).
5 validation errors, all on one Button (CatSaveButtonSubCat): "Conditional execution for action is improperly set" ×2 (an If whose predicate is a CustomFunction), Field update value "not properly set" ×1, Field "not properly set in Database action" ×2 — on a chain that compiled & ran fine the day before.
Impact: Blocks all new pushes; the previously-shipped build runs fine.
Ask: Was there a server-side validator change around 2026-06-07 affecting If predicates that call a CustomFunction inside a Button onTap chain? Please advise / fix.
Environment
- FlutterFlow version:
- Platform:
- Browser name and version:
- Operating system and version affected:
Additional Information
No response
Can we access your project?
Current Behavior
Title: Server-side compileDslApp validation regression — byte-identical project source went from [OK] to [FAIL] with no project change
Project: rada-pbljmh
Summary: A project that validated and shipped successfully on 2026-06-06 now fails compileDslApp validation on 2026-06-07/08 with the exact same source (byte-identical) and the same build (36ba76e6) — no project/source change in between.
Evidence:
Run history: [OK] compileDslApp 2026-06-06 12:30 → [FAIL] compileDslApp 2026-06-07 22:35 (and persisting 06-08), same build.
Source byte-identical to the shipped archive (verified).
5 validation errors, all on one Button (CatSaveButtonSubCat): "Conditional execution for action is improperly set" ×2 (an If whose predicate is a CustomFunction), Field update value "not properly set" ×1, Field "not properly set in Database action" ×2 — on a chain that compiled & ran fine the day before.
Impact: Blocks all new pushes; the previously-shipped build runs fine.
Ask: Was there a server-side validator change around 2026-06-07 affecting If predicates that call a CustomFunction inside a Button onTap chain? Please advise / fix.
Expected Behavior
Title: Server-side compileDslApp validation regression — byte-identical project source went from [OK] to [FAIL] with no project change
Project: rada-pbljmh
Summary: A project that validated and shipped successfully on 2026-06-06 now fails compileDslApp validation on 2026-06-07/08 with the exact same source (byte-identical) and the same build (36ba76e6) — no project/source change in between.
Evidence:
Run history: [OK] compileDslApp 2026-06-06 12:30 → [FAIL] compileDslApp 2026-06-07 22:35 (and persisting 06-08), same build.
Source byte-identical to the shipped archive (verified).
5 validation errors, all on one Button (CatSaveButtonSubCat): "Conditional execution for action is improperly set" ×2 (an If whose predicate is a CustomFunction), Field update value "not properly set" ×1, Field "not properly set in Database action" ×2 — on a chain that compiled & ran fine the day before.
Impact: Blocks all new pushes; the previously-shipped build runs fine.
Ask: Was there a server-side validator change around 2026-06-07 affecting If predicates that call a CustomFunction inside a Button onTap chain? Please advise / fix.
Steps to Reproduce
Title: Server-side compileDslApp validation regression — byte-identical project source went from [OK] to [FAIL] with no project change
Project: rada-pbljmh
Summary: A project that validated and shipped successfully on 2026-06-06 now fails compileDslApp validation on 2026-06-07/08 with the exact same source (byte-identical) and the same build (36ba76e6) — no project/source change in between.
Evidence:
Run history: [OK] compileDslApp 2026-06-06 12:30 → [FAIL] compileDslApp 2026-06-07 22:35 (and persisting 06-08), same build.
Source byte-identical to the shipped archive (verified).
5 validation errors, all on one Button (CatSaveButtonSubCat): "Conditional execution for action is improperly set" ×2 (an If whose predicate is a CustomFunction), Field update value "not properly set" ×1, Field "not properly set in Database action" ×2 — on a chain that compiled & ran fine the day before.
Impact: Blocks all new pushes; the previously-shipped build runs fine.
Ask: Was there a server-side validator change around 2026-06-07 affecting If predicates that call a CustomFunction inside a Button onTap chain? Please advise / fix.
Reproducible from Blank
Bug Report Code (Required)
I
Visual documentation
Title: Server-side compileDslApp validation regression — byte-identical project source went from [OK] to [FAIL] with no project change
Project: rada-pbljmh
Summary: A project that validated and shipped successfully on 2026-06-06 now fails compileDslApp validation on 2026-06-07/08 with the exact same source (byte-identical) and the same build (36ba76e6) — no project/source change in between.
Evidence:
Run history: [OK] compileDslApp 2026-06-06 12:30 → [FAIL] compileDslApp 2026-06-07 22:35 (and persisting 06-08), same build.
Source byte-identical to the shipped archive (verified).
5 validation errors, all on one Button (CatSaveButtonSubCat): "Conditional execution for action is improperly set" ×2 (an If whose predicate is a CustomFunction), Field update value "not properly set" ×1, Field "not properly set in Database action" ×2 — on a chain that compiled & ran fine the day before.
Impact: Blocks all new pushes; the previously-shipped build runs fine.
Ask: Was there a server-side validator change around 2026-06-07 affecting If predicates that call a CustomFunction inside a Button onTap chain? Please advise / fix.
Environment
Additional Information
No response