Open ChaseGuru opened 2 weeks ago
We've had problems with optimistic locking letting versions slip and creating unexpected problems with transitives breaking builds, so they're exact in purpose. I thought they would be better as well but in practice, over a long enough time scale, it has caused us problems
Here is the problem I mention, for posterity - which was actually an incompatibility with an untested patch release:
I was getting an error when trying to add:
When it works fine with my Podfile locking
- Firebase/Firestore (11.4.0)
: and- Firebase/Firestore (11.4.0):
.My iOS minimum deployment target is 13.0 Podfile:
And every instance of deployment target in the pbx project is: IPHONEOS_DEPLOYMENT_TARGET = 13.0;
But I get this error doing a pod install:
I swear that was happening with
pod update
or when I removed the podfile.lock alike, and it was throwing me off because it sounds like it's saying it wants me to upgrade my deployment target for iOS.Though, if I manually specify FirebaseCoreExtension 11.4.0, it works.
But resetting, it's now working if I
pod update
or rm Podfile.lock. I'm not sure what changed, BUT at this point it seems like the error is just because I had resolved 11.4.1 and your package requires 11.4.0 specifically.It still seems like a bad cocoapods error, i would expect something like:
but maybe this is the typical error :shrug:
Request: So perhaps some of this was me being dumb somehow and not doing pod update/removing the Pod lock like I thought, though it also seems like it may be good for the package to be allowing patch updates:
Since I suspect your package isn't actually incompatible with for example
11.4.1
. So perhaps:Should be something like: