Custom Function With Library Dependancy Not working

[DamusAI]

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

When you have a custom function that returns a data type struct from another library, you cannot build either in test or local run. You get the below error: (note, my library project id == 'animations-o5gwyw')

Failed to build iOS app
Error (Xcode): lib/flutter_flow/custom_functions.dart:228:14: Error:
'animations_o5gvwy_data_schema.PromptTemplateStruct' can't be used as a type because
'animations_o5gvwy_data_schema' isn't defined.
Could not build the application for the simulator.
Error launching application on iPhone 16

All other custom functions work fine, it is only when returning a struct which depends on a library's imported data struct.

For some debugging, the creation of the function itself did not require compiling the code as it normally does; there was a strange behaviour where the green tick is visible and defaulted to correct, so I am not sure if the code is not compiling and this is why?

Expected Behavior

Code should compile when saving the function.

When using the function in local run it should succeed in the build

Steps to Reproduce

1. Create a function which is return a data type for the child project
2. Save
3. Try and use the function
4. Attempt to build in local or test mode

Reproducible from Blank

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

Bug Report Code (Required)

IT48lPHqx89NobgF+KrqdflvoCUvKUM7U78V1uxTb0g8J6rPPJkAZffBblRuTde+TVdqOVmJrGc00qHKvtrxGsE7FxCqaYNe+pZUVD3jfFu6RpfQEquObXdBHeVRGkyu17WwmA9SFM9ZdCVmwUOueu+UVh/UGZDyPjBEAvijIrrJgWirGR3rUBZrzmNecCfn

Visual documentation

Environment

- FlutterFlow version:  6.1.32 (released August 5, 2025)
- Platform: We & MacOS Desktop
- Browser name and version: Chrome Version 138.0.7204.184 (Official Build) (arm64)
- Operating system and version affected: macOD Sequoia 15.5 (24F74)

Additional Information

No response

[caseyharlin]

This feels similar to my issue but I'm not sure. #6332

[bobcuzzah-oss]

Hi all,
I’m experiencing similar issues with custom functions on v6.1.32, as described in #6332. One function still looks like it works fine (no bugs for now), while others intermittently fail. Two functions that had been stable for the past two months stopped working after adding a new one a couple of days ago. Now, both an older function and the new one consistently trigger the error:
'The body might complete normally, causing 'null' to be returned, but the return type, 'int', is a potentially non-nullable type.'
The errors point to the lines ' /// MODIFY CODE ONLY ABOVE THIS LINE' for both functions, despite the code being syntactically correct (e.g., explicit returns and error handling). This suggests a parser or analyzer bug, possibly tied to the August 5, 2025 update.

Project Access: I grant permission for the FlutterFlow team to access and test my project for investigating this issue.

Impact: This blocks testing and deployment, aligning with the high-impact nature reported in #6332.

Any updates or workarounds would be greatly appreciated!
Thanks,

[Alezanello]

Hello!

Sorry for the delayed response. I wasn’t able to replicate this issue. Since we don’t have access to run your projects in Test Mode or Local Run, I downloaded the code and ran it directly from VS Code without encountering the problem.

Could you confirm if you’re still experiencing this issue when using Test Mode or Local Run on your side?

[DamusAI]

Yes, I can confirm this is still an issue. I have just retested. I have added in a function: createValuesPromptTemplate which you can now go in and check. See image below for the error I am getting (same as before).

I will leave this function in there for you to test and debug further. Also note the green tick also stayed on througout retesting this

[nathankrishnan]

@DamusAI one observation here is that titlePrompt for promptTemplate your Library's data schema expects the type String but in the screenshot for the createValuesPromptList Custom Function on line 32, it is being passed the parameter titlePrompt0 with the type List<String>.

[DamusAI]

Astute obsevation @nathankrishnan - that is indeed incorrect for the initial screenshot error I reported. I have however, as per the second screenshot i this trail, created a new function which is mapped correctly, and the same issue occurs. FYI @Alezanello

[bobcuzzah-oss]

My custom function bugs have not budged. I am new to all this and did not realise how Github was working exactly.
Will put my app on here today as well.

[fillipe-oliveira]

I’m seeing the similar issue.
A project that had been compiling fine suddenly broke ~6 days ago with no code changes on my side. The compiler stopped recognizing one of my custom code files (which defines BLE-related constants/classes used across the app).

Symptoms

Target of URI doesn't exist: '/custom_code/ble_uuids.dart'

Undefined name 'bleServiceUuid'
Undefined name 'bleFieldToUuid'

What I’m observing
From the editor tooltips/resolution hints, it looks like the analyzer/build is now resolving imports to the wrong package path. For example, when I hover a symbol it shows it coming from
package:./custom_code/functions/hex_to_integer.dart,
which doesn’t contain the BLE definitions that live in /custom_code/ble_uuids.dart. In other words, it seems to be pulling from a package that doesn’t even have those symbols, leading to broken imports and undefined names.

This exact setup worked until ~6 days ago, so it feels like a regression in how custom code files are compiled or how package:/absolute paths are being resolved.

Let me know what additional details would be most useful.