Skip to content
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

import errors #5465

Open
1 of 2 tasks
samron03 opened this issue Feb 22, 2025 · 0 comments
Open
1 of 2 tasks

import errors #5465

samron03 opened this issue Feb 22, 2025 · 0 comments
Labels
status: needs triage A potential issue that has not been confirmed as a bug.

Comments

@samron03
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

I make a custom function and it could have literally nothing else besides the imports, and somehow all of the default imports get errors. There is no possible way I could be mistyping something because I am not even the one putting those imports there. I cannot do my work because it gets nonstop errors. This also happens with custom widgets and custom actions

Expected Behavior

I would expect default imports to not get errors every time I use the custom code section of FlutterFlow

Steps to Reproduce

  1. Create new custom code
  2. Pick any of the options; Custom function, custom widget, etc.
  3. Errors show up

Reproducible from Blank

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

Bug Report Code (Required)

IT4szPHlz89NsdtJ+Kr+bsBB/GMUNn4nRLgKscp/bxIgGIDzPOw+ZPWlRFVBONenTFFiMESmmkcEwvOPk+PiGO06KSmYbJRe/qVibg7iIVKQUZOBDbiCbX97L9JmFUiP0qWrniV+KbdsdC0kwFyPNui/Xg/AHYz0ImdISq/LZO4=

Visual documentation

Image

Environment

- FlutterFlow version: v5.0
- Platform: Web
- Browser name and version: Google Chrome Version 133.0.6943.98
- Operating system and version affected: Windows 10 Pro

Additional Information

No response

@samron03 samron03 added the status: needs triage A potential issue that has not been confirmed as a bug. label Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs triage A potential issue that has not been confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

1 participant