Dsym files not present in Release mode of ObjectBox Dart

objectbox / objectbox-dart

Flutter database for super-fast Dart object persistence

https://docs.objectbox.io/getting-started

Apache License 2.0

918 stars 116 forks source link

Dsym files not present in Release mode of ObjectBox Dart #597

Closed ankitagarwal007 closed 1 month ago

ankitagarwal007 commented 3 months ago

Build info

objectbox version: 2.2.0
Flutter/Dart version: [e.g. 3.1.0, see flutter --version or dart --version]
Build OS: [e.g. Ubuntu 22.04 | Windows 11 | macOS 10.16 ]
Deployment OS or device: iOS

Steps to reproduce

Compile ObjectBox.xcframework for Release
There is a empty dSyms folder but no dsym file is present
This is causing issues as empty directories are not tracked in git. So empty Dsyms folder is getting ignored.
Build is failing because as per Info.plist file there is a dsym path which is not availabel

greenrobot-team commented 2 months ago

@ankitagarwal007 How are you building the app? E.g. do you use flutter build ipa? Can you share the error output of the build command please?

ankitagarwal007 commented 2 months ago

We are using the below.

flutter build ios-framework --xcframework --no-debug --no-profile --output=../Js/Flutter

greenrobot-team commented 2 months ago

Thanks! I verified that e.g. ObjectBox.xcframework\ios-arm64\dSYMs\ folders are empty and they are included in ObjectBox.xcframework\Info.plist.

If it makes a difference, based on the build command it looks like Flutter is integrated into an existing iOS app.

For us to check:

should our build actually include debug symbols (e.g. due to a misconfiguration the debug symbols are not copied when publishing to CocoaPods)
if not, can it be configured that these directories are not configured in ObjectBox.xcframework\Info.plist
or at last if this is a Flutter tooling issue.

greenrobot-team commented 2 months ago

@ankitagarwal007 So I tried building our relations example app with this command:

flutter build ios-framework --no-debug --no-profile --output=test-ios-framework

And besides a warning to turn off "Enable Bitcode" there are no other warnings or errors. This is using Xcode 15.0.1 on macOS 13.6.

Again, could you please share the error output of the build command?

ankitagarwal007 commented 2 months ago

The output command doesn’t give any error but when we commit our main app, and take a fresh checkout it doesn’t compile because empty folders of dSym doesn’t get committed.

greenrobot-team commented 2 months ago

@ankitagarwal007 Thanks for clarifying!

You are probably aware, but a workaround would be to add a .gitkeep file to those directories (or not check in the Pods directory at all).

Edit: created internal issue objectbox/objectbox-swift#275 for this.

ankitagarwal007 commented 2 months ago

Hi Team,

We currently do this only, but we must do it whenever we compile it. So it would be better if the object box framework either includes Dsym files or removes the path from Info.plist file

greenrobot-team commented 2 months ago

The latest release depends on a new ObjectBox Pod that includes debug symbol files.

Let us know if this resolves your issue!

github-actions[bot] commented 1 month ago

Without additional information, we are unfortunately not sure how to resolve this issue. Therefore this issue has been automatically closed. Feel free to comment with additional details and we can re-open this issue.