Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PLAT-6635] Verify BugsnagStatic usability during CI #1110

Merged
merged 1 commit into from
Jun 4, 2021

Conversation

nickdowell
Copy link
Contributor

Goal

To verify that libBugsnagStatic.a can be used by apps without requiring the -ObjC linker flag.

Relates to #1098

Changeset

libBugsnagStatic.a is now used when building the iOS test fixture. All import Bugsnag statements in Swift code needed to be removed since in this configuration Bugsnag is not built as a separate module.

The macOS fixture now links Bugsnag as a framework via CocoaPods.

Testing

Verified locally and on CI.

Tested these changes against v6.9.2 and saw an immediate crash due to unrecognized selector sent to instance when starting Bugsnag.

@nickdowell nickdowell force-pushed the nickdowell/static-linking-ci-check branch from 24140ba to 64fd2f0 Compare June 3, 2021 13:34
@nickdowell nickdowell force-pushed the nickdowell/static-linking-ci-check branch from 64fd2f0 to e53df1a Compare June 3, 2021 13:40
@github-actions
Copy link

github-actions bot commented Jun 3, 2021

Infer: No issues found 🎉

OCLint: No issues found 🎉

Bugsnag.framework binary size did not change - 1,126,592 bytes

Generated by 🚫 Danger

@nickdowell nickdowell requested review from kattrali and kstenerud June 3, 2021 13:49
@nickdowell nickdowell merged commit f7db679 into next Jun 4, 2021
@nickdowell nickdowell deleted the nickdowell/static-linking-ci-check branch June 4, 2021 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants