Can we access your project?
Current Behavior
When generating screenshots for App Store deployment using FlutterFlow's built-in App Store Screenshot Generator tool, the generated images are sized for a 6.7-inch display format. App Store Connect requires 6.5-inch screenshots (e.g., 1242 x 2688 px or 1284 x 2778 px) and rejects the generated images upon upload.
Expected Behavior
The Screenshot Generator should export images in a compliant 6.5-inch resolution (1242 x 2688 px / 1284 x 2778 px) or offer an option to choose between 6.5" and 6.7" sizes to meet Apple's exact submission requirements.
Steps to Reproduce
Open a project in FlutterFlow.
Navigate to the App Store Screenshot Generator tool.
Generate screenshots for iOS / App Store.
Export the images and check their resolution or try uploading them to App Store Connect under the 6.5" display section.
Observe that Apple rejects the file due to incorrect dimensions.
Reproducible from Blank
Bug Report Code (Required)
Visual documentation
Environment
- FlutterFlow version:
- Platform:
- Browser name and version:
- Operating system and version affected :
Additional Information
No response
Can we access your project?
Current Behavior
When generating screenshots for App Store deployment using FlutterFlow's built-in App Store Screenshot Generator tool, the generated images are sized for a 6.7-inch display format. App Store Connect requires 6.5-inch screenshots (e.g., 1242 x 2688 px or 1284 x 2778 px) and rejects the generated images upon upload.
Expected Behavior
The Screenshot Generator should export images in a compliant 6.5-inch resolution (1242 x 2688 px / 1284 x 2778 px) or offer an option to choose between 6.5" and 6.7" sizes to meet Apple's exact submission requirements.
Steps to Reproduce
Open a project in FlutterFlow.
Navigate to the App Store Screenshot Generator tool.
Generate screenshots for iOS / App Store.
Export the images and check their resolution or try uploading them to App Store Connect under the 6.5" display section.
Observe that Apple rejects the file due to incorrect dimensions.
Reproducible from Blank
Bug Report Code (Required)
Visual documentation
Environment
Additional Information
No response