Conversation
|
|
| When editing native files in FlutterFlow, you may need to include dynamic values, such as API keys, app configurations, or environment-specific settings. Instead of hardcoding these values directly in **`AndroidManifest.xml`**, **`Info.plist`**, or other native files, you can use FlutterFlow [**Environment Values**](../../testing-deployment-publishing/development-environments/development-environments.md#environment-values) and [**Library Values**](../../resources/projects/libraries.md#library-values) to keep your app flexible and secure. | ||
|
|
||
| FlutterFlow allows you to use placeholders in native files that get replaced with actual values during the app build process. These placeholders help in managing different environments (development, staging, production) and keeping sensitive data out of the codebase. | ||
| To include a variable in a configuration file, start by creating a **file-level variable** and assigning it a value from either your **environment values** or **library values**. Then, reference this variable using a placeholder format (e.g., `{{apiToken}}`) within the configuration file. These placeholders in native files are automatically replaced with their actual values during the app build process. |
There was a problem hiding this comment.
| To include a variable in a configuration file, start by creating a **file-level variable** and assigning it a value from either your **environment values** or **library values**. Then, reference this variable using a placeholder format (e.g., `{{apiToken}}`) within the configuration file. These placeholders in native files are automatically replaced with their actual values during the app build process. | |
| To include a variable in a configuration file, start by creating a **file-level variable** and assigning it a value from either your **Environment Values** or **Library Values**. Then, reference this variable using a placeholder format (e.g., `{{apiToken}}`) within the configuration file. These placeholders in native files are automatically replaced with their actual values during the app build process. |
There was a problem hiding this comment.
Also need links for env, lib values
There was a problem hiding this comment.
"their actual values during the code generation process" I think?
There was a problem hiding this comment.
@PoojaB26 yes updated to 'the code generation process' and the links are already added in a paragraph just above it. do we still need them again?
There was a problem hiding this comment.
oh missed it, no worries then
| height: 0, | ||
| width: '100%'}}> | ||
| <iframe | ||
| src="https://demo.arcade.software/srZqoYaaoVR1mCE3t8AL?embed&show_copy_link=true" |
There was a problem hiding this comment.
In the Arcades, the text boxes should be aligned with the circles, otherwise its hard to miss.
| height: 0, | ||
| width: '100%'}}> | ||
| <iframe | ||
| src="https://demo.arcade.software/szmDUd7g9ZqX9OoNJVws?embed&show_copy_link=true" |
There was a problem hiding this comment.
Can we show this example from an unlocked state? Like Ian's demo video? So manually writing a tag in the unlocked file and then using a new variable name there
There was a problem hiding this comment.
Yes, I actually tried that first, but it seems there’s an issue. After editing the file, we’re unable to save it, and the variable only gets created once the file is successfully saved. I’ll go ahead and report this as a bug.
There was a problem hiding this comment.
Ah good call to create a bug report! Because that would be high priority bug.
…terFlow/flutterflow-documentation into feature/configuration-files
PoojaB26
left a comment
PoojaB26
left a comment
There was a problem hiding this comment.
We'll update the Arcade when the fix is live.
2 participants
Description
Access Variables in Config Files
Linear ticket and magic word Fixes DEVR-864
Type of change