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
feat: fixed issues with adding file to target #10
Conversation
Pull request title looks good 👍! If this pull request gets merged, it will cause a new release of the software. Example: If this project's latest release version is All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time. To merge this pull request, add the label This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...This project uses a special format for pull requests titles. Don't worry, it's easy! This pull request title should be in this format:
If your pull request introduces breaking changes to the code, use this format:
where
Examples:
Need more examples? Want to learn more about this format? Check out the official docs. Note: If your pull request does multiple things such as adding a feature and makes changes to the CI server and fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests. |
@xtreem88 Why is this PR a breaking change? Since we are still just in |
Thanks for pointing this out. This was a mistake... I was testing the integration with |
@ami-aman @levibostian I am going to clean up this PR soon. I have been testing the changes with different Expo managed projects, and it seems to hold up well. After this, I would need another round of reviews. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocking PR because the way we install versions of RN and iOS SDKs are not consistent. My PR comments address this.
## [1.0.0-alpha.6](1.0.0-alpha.5...1.0.0-alpha.6) (2022-12-30) ### ⚠ BREAKING CHANGES * changed googleServicesFilePath to googleServicesFile (#16) ### Features * fixed issues with adding file to target ([#10](#10)) ([0674c66](0674c66)) * rich push environment variable setup ([#23](#23)) ([8d83c95](8d83c95)) * user agent for expo ([#8](#8)) ([19e78b1](19e78b1)) ### Code Refactoring * changed googleServicesFilePath to googleServicesFile ([#16](#16)) ([26be4db](26be4db))
🎉 This PR is included in version 1.0.0-alpha.6 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
## 1.0.0-beta.1 (2022-12-30) ### ⚠ BREAKING CHANGES * changed googleServicesFilePath to googleServicesFile (#16) ### Features * added ability to set use_frameworks to static ([#9](#9)) ([05d7012](05d7012)) * fixed issues with adding file to target ([#10](#10)) ([0674c66](0674c66)) * rich push environment variable setup ([#23](#23)) ([8d83c95](8d83c95)) * user agent for expo ([#8](#8)) ([19e78b1](19e78b1)) ### Bug Fixes * fixed info.plist formatting issue ([#18](#18)) ([d701794](d701794)) * update .releaserc.json ([#21](#21)) ([8c751cf](8c751cf)) * updated package version ([#19](#19)) ([ab30383](ab30383)) ### Code Refactoring * changed googleServicesFilePath to googleServicesFile ([#16](#16)) ([26be4db](26be4db))
🎉 This PR is included in version 1.0.0-beta.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
https://github.com/customerio/issues/issues/8669
This PR fixes the issue with xcode not recognizing
PushNotification.swift
and requiring an extra step of adding the file afterprebuild