You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please help prevent duplicate issues before submitting a new one:
I've searched other open/closed issues for duplicates before opening up this new issue.
Report
What did you do?
I created an xcframework that has a dependency on Down, then integrated the framework into an app that pulls Down in via Cocoapods.
What did you expect to happen?
I expected to be able to call methods from the framework in the app that relied on Down.
What happened instead?
There is an EXC_BAD_ACCESS crash anytime the app calls a method from the framework that uses Down.
I've successfully integrated a separate xcframwork with a third-party dependency in this way, so I'm guessing this is related to how Down is referencing libcmark.
I've attached two sample projects which demonstrate the issue. The xcframework linked in the TestApp was generated from the TestFramework project by running the build_xcframework shell script included in the folder.
Please help prevent duplicate issues before submitting a new one:
Report
What did you do?
I created an xcframework that has a dependency on Down, then integrated the framework into an app that pulls Down in via Cocoapods.
What did you expect to happen?
I expected to be able to call methods from the framework in the app that relied on Down.
What happened instead?
There is an EXC_BAD_ACCESS crash anytime the app calls a method from the framework that uses Down.
I've successfully integrated a separate xcframwork with a third-party dependency in this way, so I'm guessing this is related to how Down is referencing libcmark.
I've attached two sample projects which demonstrate the issue. The xcframework linked in the TestApp was generated from the TestFramework project by running the build_xcframework shell script included in the folder.
DownTest.zip
The text was updated successfully, but these errors were encountered: