Skip to content

Commit 964de2c

Browse files
authored
Merge branch 'main' into fix/test-auth-on-local-run
2 parents d6b4e02 + 2b22b3a commit 964de2c

31 files changed

+713
-2
lines changed

docs/accounts-billing/new-pricing-comparison.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -342,7 +342,7 @@ export const PricingToggles = () => {
342342
<td>Automated Testing<br/><span className="feature-description">Run automated tests on your applications</span></td>
343343
<td>❌</td>
344344
<td>❌</td>
345-
<td></td>
345+
<td>1 test per project</td>
346346
<td>Up to 3 tests per project</td>
347347
<td>Unlimited tests</td>
348348
</tr>

docs/ff-concepts/layout/responsive-layout.md

Lines changed: 55 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -196,4 +196,58 @@ To implement this, we can go to its widget properties and toggle the device icon
196196

197197
And now you have a more responsive screen for this shopping app use case that looks good in both mobile and desktop formats.
198198

199-
With these adjustments, your shopping app now boasts a highly responsive screen that seamlessly adapts to both mobile and desktop formats. This ensures an optimal user experience across all devices, maintaining both functionality and aesthetic appeal.
199+
With these adjustments, your shopping app now boasts a highly responsive screen that seamlessly adapts to both mobile and desktop formats. This ensures an optimal user experience across all devices, maintaining both functionality and aesthetic appeal.
200+
201+
## Responsive Value
202+
203+
**Responsive Values** allow you to define different property values, such as widths, heights, font sizes, or padding, for different device sizes (mobile, tablet, desktop, and wide). At runtime, your app evaluates the screen width and automatically applies the appropriate value based on your configurations.
204+
205+
:::info[possible use cases]
206+
207+
- **Adaptive Layouts**: Automatically adjust element sizes to deliver a consistent UI across devices.
208+
- **Better Readability**: Increase font size on larger screens to improve legibility.
209+
- **Improved Spacing**: Use different padding or margins on tablets and desktops to optimize content flow.
210+
211+
:::
212+
213+
To set a responsive value, select a widget and choose a property that supports responsiveness. Click **Set from Variable > Responsive Value**, then enter different values for each screen size:
214+
215+
- Mobile (below `Breakpoint Small`)
216+
- Tablet (below `Breakpoint Medium`)
217+
- Desktop (below `Breakpoint Large`)
218+
- Wide (above `Breakpoint Large`)
219+
220+
As you preview on different devices, the property will automatically adjust based on the selected screen size.
221+
222+
:::tip[Customizing Breakpoints]
223+
224+
You can adjust the default screen size breakpoints (mobile, tablet, desktop, wide) in FlutterFlow’s Theme Settings. See how to [**Customize Breakpoints**](#customize-responsive-breakpoints).
225+
226+
:::
227+
228+
229+
<div style={{
230+
position: 'relative',
231+
paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
232+
height: 0,
233+
width: '100%'}}>
234+
<iframe
235+
src="https://demo.arcade.software/0XfY0BCqlcIrsXhOGlCh?embed&show_copy_link=true"
236+
title=""
237+
style={{
238+
position: 'absolute',
239+
top: 0,
240+
left: 0,
241+
width: '100%',
242+
height: '100%',
243+
colorScheme: 'light'
244+
}}
245+
frameborder="0"
246+
loading="lazy"
247+
webkitAllowFullScreen
248+
mozAllowFullScreen
249+
allowFullScreen
250+
allow="clipboard-write">
251+
</iframe>
252+
</div>
253+
<p></p>
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
{
2+
"label": "GitHub"
3+
}
Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
keywords: ['github', 'push', 'repository', 'initialize', 'error']
3+
slug: /initialize-github-repository
4+
title: Initialize GitHub Repository
5+
---
6+
7+
# Initialize GitHub Repository
8+
9+
When pushing code to GitHub, the following error may occur:
10+
11+
```js
12+
Error pushing repository. Make sure your repository is initialized
13+
```
14+
15+
This typically happens if the GitHub repository was not initialized correctly or if the project exceeds GitHub’s file size limits.
16+
17+
:::info[Prerequisites]
18+
- Access to your GitHub account.
19+
- A FlutterFlow project with GitHub integration enabled.
20+
:::
21+
22+
Follow the steps below to initialize a GitHub repository:
23+
24+
1. **Create a New Repository**
25+
26+
- Go to **[GitHub](https://github.com/)** and click **New** to create a repository.
27+
- Enable the option **Add a README file** during creation.
28+
29+
2. **Connect Repository to FlutterFlow**
30+
31+
- Open your FlutterFlow project.
32+
- Navigate to **GitHub Integration** and follow the instructions to connect the new repository.
33+
34+
![](../assets/20250430121522561282.gif)
35+
36+
3. **Download and Inspect Your Project**
37+
38+
- Download the full source code from FlutterFlow.
39+
- Navigate to the `assets` folder.
40+
- Identify any files larger than **25MB**.
41+
42+
:::warning[Check Your Asset Size]
43+
GitHub does not allow individual files larger than 25MB. Large image or video files may cause push failures.
44+
:::
45+
46+
47+
:::tip[Tips to Reduce Project Size]
48+
- Use **network assets** instead of uploading large media files directly to FlutterFlow.
49+
- Optimize images using tools like TinyPNG or ImageOptim before uploading.
50+
:::
51+
52+
:::info[Additional Resources]
53+
- **[Connect a GitHub Repo](/exporting/push-to-github/#connect-a-github-repo)**
54+
- **[State Management](/concepts/state-management/)**
55+
:::
Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
---
2+
keywords: ['deployment', 'github', 'repository', 'codemagic']
3+
slug: /repository-head-deployment-failure
4+
title: Repository Head Deployment Failure
5+
---
6+
7+
# Repository Head Deployment Failure
8+
9+
This error may occur when deploying your FlutterFlow app to GitHub using Codemagic. The message `Failed to set the repository head` indicates a problem with repository access, configuration, or connectivity.
10+
11+
:::info[Prerequisites]
12+
- A connected GitHub repository with appropriate access permissions.
13+
- GitHub deployment enabled within FlutterFlow.
14+
:::
15+
16+
**The Error Message**
17+
18+
```js
19+
Failed to set the repository head
20+
```
21+
This message typically appears in the build log during deployment.
22+
23+
Below are the possible causes of this error:
24+
25+
- The GitHub repository does not exist or was deleted.
26+
- The branch specified in build settings does not exist.
27+
- Insufficient permissions to push or write to the branch.
28+
- GitHub API or network connectivity issues.
29+
- Local build errors in the codebase.
30+
31+
**Steps to Fix the Deployment Error:**
32+
33+
1. **Confirm the Repository Name**
34+
35+
Ensure the repository name in your FlutterFlow deployment settings exactly matches the name in GitHub.
36+
37+
2. **Verify the Branch**
38+
39+
Check that the branch exists in the repository and is correctly specified in your build settings. Avoid typos or casing mismatches.
40+
41+
3. **Review Repository Permissions**
42+
43+
Confirm that your GitHub account or connected GitHub App has push/write access to the repository and branch.
44+
45+
4. **Check Network Access**
46+
47+
Make sure your environment is not blocking GitHub via VPN, firewall, or DNS restrictions.
48+
49+
5. **Validate the Codebase Locally**
50+
51+
Run the downloaded Flutter project locally to confirm that it builds without errors.
52+
53+
:::info[Additional Resources]
54+
- **[GitHub Deployment Overview](/deployment/deploy-from-github/#steps-to-deploy)**
55+
- **[Codemagic Error Identification Guide](/codemagic-deployment-error-identification/)**
56+
:::
119 KB
Loading
140 KB
Loading
262 KB
Loading
84.1 KB
Loading
110 KB
Loading

0 commit comments

Comments
 (0)