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
When attempting to compile a project with splunk-otel-ios-crashreporting added as a Swift Package Manager (SPM) dependency, I encounter a build failure with the following error message:
Null objc class data for 'OBJC_METACLASS$_PLCrashHostInfo' in CrashReporter.o'
Steps to Reproduce:
Create a new project in XCode 15 (currently in beta).
Navigate to Swift Package Manager and add splunk-otel-ios-crashreporting as a dependency, using the following URL: https://github.com/signalfx/splunk-otel-ios-crashreporting/
Attempt to build the project.
Expected Result:
The project should build successfully without any errors.
Actual Result:
The build fails with the error message:
Null objc class data for 'OBJC_METACLASS$_PLCrashHostInfo' in CrashReporter.o'
Additional Information:
Even though XCode 15 is in beta, we are keen to test our app's compatibility with the forthcoming iOS 17 and this issue is currently blocking our progress. We would greatly appreciate any assistance in resolving this problem.
Best,
seviu
The text was updated successfully, but these errors were encountered:
Description:
When attempting to compile a project with
splunk-otel-ios-crashreporting
added as a Swift Package Manager (SPM) dependency, I encounter a build failure with the following error message:Null objc class data for 'OBJC_METACLASS$_PLCrashHostInfo' in CrashReporter.o'
Steps to Reproduce:
splunk-otel-ios-crashreporting
as a dependency, using the following URL:https://github.com/signalfx/splunk-otel-ios-crashreporting/
Expected Result:
The project should build successfully without any errors.
Actual Result:
The build fails with the error message:
Null objc class data for 'OBJC_METACLASS$_PLCrashHostInfo' in CrashReporter.o'
Additional Information:
Even though XCode 15 is in beta, we are keen to test our app's compatibility with the forthcoming iOS 17 and this issue is currently blocking our progress. We would greatly appreciate any assistance in resolving this problem.
Best,
seviu
The text was updated successfully, but these errors were encountered: