Closed JordyLangen closed 1 year ago
Removing the Podfile.lock
seems to fix it, but that should not be needed.
Hi @JordyLangen,
In the Cocoapods docs for pod install
, it notes that the command will take into account the specific version inside the Podfile.lock
instead of updating to the latest version. Adding the flag --repo-update
will run pod repo update
prior to the command, but it will still use the pod install
command afterwards.
In this case, it sounds like you'd want to use the pod update
command to ensure that the latest version of the Braze pod is used instead of the version in Podfile.lock
. Let us know if that resolves the issue - thanks!
We did not seem to have to do this in the past, anyway thanks for the reply.
After updating our plugin dependency to 5.0.0 and running
pod install –repo-update
I get the following: