Skip to content

Commit c0d2c21

Browse files
authored
Merge branch 'main' into fix/update-stripe-coutry-code
2 parents 887f167 + dae840e commit c0d2c21

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

docs/resources/projects/libraries.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -430,3 +430,14 @@ We're working on Library Values, which will allow users to set specific values w
430430
Projects can import libraries that themselves have imported other Libraries as dependencies. However, if the project and the library share the same dependency, the version must match exactly to avoid conflicts.
431431
</p>
432432
</details>
433+
434+
<details>
435+
<summary>Why do I get collision errors when importing a duplicated project as a library?</summary>
436+
<p>
437+
When you duplicate a project and publish it as a library, the unique identifiers (keys) for components and other resources are not automatically changed. If you then import this library back into the original project, it causes key collisions between the original and duplicated resources.
438+
439+
To help with this, FlutterFlow shows a dialog that offers to automatically delete the original resources in your base project and update all references to point to the library versions.
440+
441+
If you prefer to resolve this manually, you can duplicate individual components within the library after importing, this will generate new keys and avoid the collision.
442+
</p>
443+
</details>

0 commit comments

Comments
 (0)