Rename OneSignalCore class to prevent conflict with the framework name#1382
Merged
Rename OneSignalCore class to prevent conflict with the framework name#1382
OneSignalCore class to prevent conflict with the framework name#1382Conversation
Named `OneSignalCore` class to `OneSignalCoreImpl`
aff4cf2 to
240876e
Compare
jkasten2
approved these changes
Mar 6, 2024
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
One Line Summary
Rename
OneSignalCoreclass to prevent conflict with the framework name, which was causing Swift apps to have build errors.Details
Motivation
After we released
v5.1.1with the new CD action and thenv5.1.2manually (thinking the error was due to the CD process), both releases caused Swift build errors in apps that looked like this.I noticed only
OneSignalFrameworkimport was erroring. Using OneSignalUser or OneSignalCore directly was ok.It is because of adding a class called
OneSignalCorein theOneSignalCoreframework in #1371. The Swift interface inOneSignalFrameworkhad a conflict between the class name and framework name. No other modules have a Swift interface.Renamed the class to
OneSignalCoreImplbut considered other choices like "manager", "controller", etc.Scope
Renaming internal class
Testing
Unit testing
None
Manual testing
OneSignalXCFrameworkpod to a project using the local path to the iOS SDK and confirmed the error went away and the app built and ran successfully."nil"json values to be""#1373Affected code checklist
Checklist
Overview
Testing
Final pass
This change is