Closed TwistedMinda closed 1 year ago
Sorry you encountered this error, @TwistedMinda. We are working on making improvements to our SDK to prevent errors like this from happening. I understand they can be frustrating.
Try to run pod update --repo-update --project-directory=ios
in your React Native project and see if the build error goes away.
If you still get a build error, please, follow these steps to further help you.
pod update...
command. ios/Podfile
and ios/Podfile.lock
files. You can paste them here or send them to win@customer.io
. Hi, thanks for the fast response!
It didn't help, no changes happened when trying to repo-update, here is the output:
Can you explain a bit more on why would I need to update the repo when customerio package should just set the specific version of the native SDK. Is there something I'm missing?
Thank you!
My mistake, I had pod 'CustomerIO/MessagingPushAPN', '~> 2.1.2'
in my Podfile
causing the troubles linking the Pods with the new version. Setting it to pod 'CustomerIO/MessagingPushAPN', '~> 2.7.0'
and the problem is gone ;)
Thanks again for the fast response.
Glad to hear that you were able to fix this.
Great timing as version 3 of the SDK has just released and it should prevent the error you experienced from occurring.
Update the React Native SDK to 3.0.0 in your package.json
file, follow our migration docs (only requires a change to your Podfile
), and enjoy!
SDK version: 2.5.0 (react-native 0.71.6)
Platform: iOS
Are logs available?
Describe the bug: When updating from 2.3.3 to 2.4.2 or newer
To Reproduce
Update from 2.3.3 to >= 2.4.2 (where the first imports to CioInternalCommon appeared)
Expected behavior
I expect no build errors ;)
Screenshots