While im archiving and uploading an build to the appstore connect through xcode im facing this error.
The archive did not include a SYM for the Flutter.framework with the UUIDs
[4C4C44D2-5555-3144-A107-7B9E8F9E2FF7]. Ensure that the archive’s dSYM folder includes a
DWARF file for Flutter.framework with the expected
Its saying dSYM is not included in the archive. Im using macos15 with xcode version 16.0
Is there anything that i need to change or add to the project?
2
Answers
You can try these methods to fix this issue
1. Ensure dSYM files are generated correctly
Open your project in Xcode.
Go to your Build Settings tab.
Search for "Debug Information Format" under the Build Settings.
Ensure that the value for both Debug and Release is set to DWARF with dSYM File.
2. Verify Build Configuration
Make sure that in Scheme -> Archive settings, the build configuration is set to Release.
Go to Product -> Scheme -> Manage Schemes, and ensure the Build Configuration for Archive is set to Release.
3. Rebuild the Project
After ensuring the above settings are correct:
Clean the project in Xcode by clicking Product -> Clean Build Folder.
Then, rebuild the project by clicking Product -> Build.
Archive the project again and check if the error persists.
4. Verify that dSYMs are included in the Archive
After archiving the app, go to Window -> Organizer in Xcode, select the archive you created, and click Show in Finder.
In Finder, right-click the archive and choose Show Package Contents.
Go to dSYMs folder and verify that the Flutter.framework.dSYM is present.
5. Check Flutter Frameworks
If the issue still persists, ensure you are packaging your Flutter app correctly:
Run the following command in the terminal in your project folder:
This will clean and rebuild your Flutter iOS app, regenerating the necessary files, including dSYM files.
After following these steps, attempt to archive and upload again. Let me know if you encounter further issues!
I discovered this error after updating to macOS 15 and Xcode 16.0. The previous archive, which didn’t show an error during validation before the update, now shows this error during validation. I’ll try to send the app to Connect with this error.