Skip to content

"Remove from Set" with Firestore "Doc Reference" silently fails on iOS after June 2025 update #5985

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 2 tasks
bmvictorb opened this issue Jun 12, 2025 · 2 comments
Open
1 of 2 tasks
Assignees
Labels
status: can't reproduce Following the reported steps did not reproduce the bug.

Comments

@bmvictorb
Copy link

Can we access your project?

  • I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

`

🧩 Description:

After the recent FlutterFlow update in early June 2025, the Remove from Set Firestore action (used to remove a DocumentReference from an array field) no longer works on iOS/TestFlight builds, though it still works perfectly on Android and Web.

This was working fine across all platforms prior to the update, but now the removal action silently fails on iOS only, with no error logs or Firebase crash reports.


✅ Expected Behavior

When using:

  • Update Document

  • Remove from Set on a field like Guidance_Verses (an array of Doc Reference (Verses_Collection))

…the selected document reference should be removed from the list on all platforms, including iOS.


❌ Actual Behavior

  • On Android & Web: item is correctly removed.

  • On iOS (TestFlight): nothing happens. The Firestore array field remains unchanged.

  • No crash, no error — just silent failure.


🔁 Reproduction Steps

  1. In FlutterFlow, create a loop over a list of Doc Reference (Verses_Collection).

  2. Inside the loop, add Update Document action to:

    • Remove from SetGuidance_Verses

    • Value: current loop item (typed as Doc Reference)

  3. Run on:

    • Android: ✅ Works

    • Web: ✅ Works

    • iOS (TestFlight): ❌ Fails silently


🧪 Tests Attempted

To isolate the issue, I also tested:

  • ✅ Using Set Variable to rebind loop item as a new Doc Reference

  • ✅ Reading document and using .reference in update

  • ✅ Disabling batched writes

  • ✅ Adding delay between actions

None of these solved the iOS failure.


🛠 Temporary Workaround

I can work around this issue by:

  • Using a custom backend call with raw Firestore arrayRemove

  • Or migrating to using a subcollection instead of a Doc Reference list field

…but ideally, the built-in Remove from Set logic should be cross-platform stable.


🖥 Platform & Environment

Detail | Value -- | -- FlutterFlow Version | June 2025 (latest) Affected Platform | iOS (TestFlight) Working Platforms | Android, Web Firestore Field Type | Array of Doc Reference User Auth | Firebase Email Auth Batched Writes | Tested both ON/OFF
`

Expected Behavior

The Remove from Set action should successfully remove a DocumentReference from a Firestore array field (e.g. Guidance_Verses) on all platforms, including iOS. This behavior worked prior to the June 2025 FlutterFlow update and continues to work on Android and Web. iOS should behave the same.

Steps to Reproduce

`In FlutterFlow, create a loop over a list of Doc Reference (Verses_Collection).

Inside the loop, add Update Document action to:

Remove from Set → Guidance_Verses

Value: current loop item (typed as Doc Reference)

Run on:

Android: ✅ Works

Web: ✅ Works

iOS (TestFlight): ❌ Fails silently`

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

ITFXk8nfsJVNssRE1bXiYPl4mWEwFjsFUOdEl9dTaEobfJysB4kqeer+VG9DXOnnegl6PFejrE8EptL3keDlJMAEGweVeINozLlyegHMfF+5RaqqC5C/dWh6J/tYf3Kx4Ji32B14D7JiL05kw2z/cq3qNleeY8aSfxBlZ7vfcPo=

Visual documentation

Image

Environment

the bug is only on iOS, (on web and android it works perfectly). ALso it worked on iOS before the udpate in june, but now it fails to work.

Additional Information

No response

@bmvictorb bmvictorb added the status: needs triage A potential issue that has not been confirmed as a bug. label Jun 12, 2025
Copy link
Collaborator

Hello!

I wasn’t able to replicate the issue on my end. For further assistance, please reach out to our support team via the in-app chat or by emailing [email protected]—they’ll be able to help you resolve this issue directly within your project.

Thanks!

@Alezanello Alezanello self-assigned this Jun 13, 2025
@Alezanello Alezanello added the status: can't reproduce Following the reported steps did not reproduce the bug. label Jun 13, 2025 — with Linear
@Alezanello Alezanello removed the status: needs triage A potential issue that has not been confirmed as a bug. label Jun 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: can't reproduce Following the reported steps did not reproduce the bug.
Projects
None yet
Development

No branches or pull requests

2 participants