Skip to content

Library Values Input Section Missing in Dependencies screen and when importing a library #6500

@sgardoll

Description

@sgardoll

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

Loom: https://www.loom.com/share/8727fc58c6bc4b36a324d2581698c8fa?sid=d087e603-a16e-4b6a-baee-04dee05ec7b3

When importing a library into a project, the section to input library values has disappeared, resulting in an error due to a required non-nullable library value. This issue prevents users from proceeding with their projects as they cannot set necessary values for the library components.

Expected Behavior

  • The section for inputting library values should be visible and accessible when a library is imported into a project.
  • Users should be able to input both nullable and non-nullable library values without encountering errors.
  • The error message regarding null values should not appear if the library values are correctly set.

Steps to Reproduce

  1. Create a library with a page called 'Demo' that includes two library values (one nullable, one non-nullable).
  2. Import this library into a different project.
  3. Attempt to locate the section for inputting library values in the project settings.
  4. Observe that the section is missing and an error is displayed regarding the non-nullable library value.

Reproducible from Blank

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

Bug Report Code (Required)

https://www.loom.com/share/8727fc58c6bc4b36a324d2581698c8fa?sid=d087e603-a16e-4b6a-baee-04dee05ec7b3

Visual documentation

https://www.loom.com/share/8727fc58c6bc4b36a324d2581698c8fa?sid=d2e1b6e2-94c8-4d11-bb57-c17fe8d7049b

Environment

- FlutterFlow version: 
- Platform:
- Browser name and version:
- Operating system and version affected:

Additional Information

No response

Metadata

Metadata

Assignees

Labels

Bugstatus: confirmedIssue has been reproduced and confirmed as a bug.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions