Can we access your project?
Current Behavior
Device: iPhone 13, iOS 26.5.2
Generated version: file_picker 10.1.9
Error: duplicate FileUtils implementation and startup crash
Workaround: changing only file_picker to 10.3.8
Result: repeated cold launches and stability tests passed
Expected Behavior
A FlutterFlow-generated iOS application should launch and reopen normally on a supported physical iPhone using the dependency versions automatically provided by FlutterFlow.
The application should not crash during Flutter plugin registration. Closing the application from the iPhone app switcher and reopening it from the Home Screen should work consistently without requiring a manual dependency change after every code export.
Steps to Reproduce
Open the attached FlutterFlow project using the supplied Bug Report Code.
Confirm that FlutterFlow automatically adds file_picker 10.1.9 under FlutterFlow Pub Dependencies.
Start Local Run on a physical iPhone 13 running iOS 26.5.2.
Allow the required permissions, install the application, and launch it.
Swipe the application away from the iPhone app switcher.
Reopen the application from the iPhone Home Screen.
The application displays a white screen briefly and then crashes back to the Home Screen.
The device log reports EXC_BAD_ACCESS during plugin registration. The Local Run log also reports that FileUtils is implemented both in Apple’s OSAnalytics framework and in Runner.debug.dylib.
Download or copy the same generated project.
Change only file_picker: 10.1.9 to file_picker: 10.3.8.
Run flutter clean, flutter pub get, and rebuild the application in profile mode.
Repeat multiple cold launches. The patched application launches normally and remains stable.
This result has been reproduced several times. Reverting to FlutterFlow’s managed file_picker 10.1.9 recreates the problem, while 10.3.8 resolves it.
Reproducible from Blank
Bug Report Code (Required)
IT8OlsmAuJZgrsdc7qrPbcBFpDgWQ182RYJNlutAEA81GIDoOolzZPTOVFJuOLGmT2xmPWaWrGYV/N7rhYbhD/kCaA6VbdVx1YdyVDzgXTuuQJO3O7WadnBAEeFPCWqf156nsAonAPdYSlllwzuHPvWyTijDNZD1NTIvAv+ZKrvNog6rKwDJEREz3TcVLEu7BskMXhKyuM+UtpJh0eDnyw==
Visual documentation
Environment
Project: BombReel Phase 2 MVP Foundation
Branch: main
FlutterFlow environment: Production
FlutterFlow version: v7.0.67
Flutter version: 3.38.6
Testing method: FlutterFlow Local Run on a physical iOS device
Computer: Apple Silicon MacBook Pro
macOS: 26.5.2
Xcode version: Version 26.6 (17F113)
Physical device: iPhone 13
Device identifier/model from crash report: iPhone14,5
iOS version: 26.5.2
Application identifier: app.bombreel.mobile
FlutterFlow-managed package: file_picker 10.1.9
Working package version: file_picker 10.3.8
Working-build command: flutter run --profile
Result with managed version: Application crashes during launch or cold relaunch
Result after package update: Multiple cold-launch and stability tests pass
Additional Information
Recreated from the FlutterFlow Local Run log captured during the crash. The original log reported that FileUtils was implemented in both Apple’s OSAnalytics framework and Runner.debug.dylib.
Permission is granted for investigation and inspection. Please do not modify the project without my written confirmation.
Can we access your project?
Current Behavior
Device: iPhone 13, iOS 26.5.2
Generated version: file_picker 10.1.9
Error: duplicate FileUtils implementation and startup crash
Workaround: changing only file_picker to 10.3.8
Result: repeated cold launches and stability tests passed
Expected Behavior
A FlutterFlow-generated iOS application should launch and reopen normally on a supported physical iPhone using the dependency versions automatically provided by FlutterFlow.
The application should not crash during Flutter plugin registration. Closing the application from the iPhone app switcher and reopening it from the Home Screen should work consistently without requiring a manual dependency change after every code export.
Steps to Reproduce
Open the attached FlutterFlow project using the supplied Bug Report Code.
Confirm that FlutterFlow automatically adds file_picker 10.1.9 under FlutterFlow Pub Dependencies.
Start Local Run on a physical iPhone 13 running iOS 26.5.2.
Allow the required permissions, install the application, and launch it.
Swipe the application away from the iPhone app switcher.
Reopen the application from the iPhone Home Screen.
The application displays a white screen briefly and then crashes back to the Home Screen.
The device log reports EXC_BAD_ACCESS during plugin registration. The Local Run log also reports that FileUtils is implemented both in Apple’s OSAnalytics framework and in Runner.debug.dylib.
Download or copy the same generated project.
Change only file_picker: 10.1.9 to file_picker: 10.3.8.
Run flutter clean, flutter pub get, and rebuild the application in profile mode.
Repeat multiple cold launches. The patched application launches normally and remains stable.
This result has been reproduced several times. Reverting to FlutterFlow’s managed file_picker 10.1.9 recreates the problem, while 10.3.8 resolves it.
Reproducible from Blank
Bug Report Code (Required)
IT8OlsmAuJZgrsdc7qrPbcBFpDgWQ182RYJNlutAEA81GIDoOolzZPTOVFJuOLGmT2xmPWaWrGYV/N7rhYbhD/kCaA6VbdVx1YdyVDzgXTuuQJO3O7WadnBAEeFPCWqf156nsAonAPdYSlllwzuHPvWyTijDNZD1NTIvAv+ZKrvNog6rKwDJEREz3TcVLEu7BskMXhKyuM+UtpJh0eDnyw==
Visual documentation
Environment
Additional Information
Recreated from the FlutterFlow Local Run log captured during the crash. The original log reported that FileUtils was implemented in both Apple’s OSAnalytics framework and Runner.debug.dylib.
Permission is granted for investigation and inspection. Please do not modify the project without my written confirmation.