Hello, I'm getting the following crash on iOS:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[FIRActionCodeSettings setDynamicLinkDomain:]: unrecognized selector sent to instance 0x600000012250'
*** First throw call stack:
(
0 CoreFoundation 0x00000001804f39e8 __exceptionPreprocess + 172
1 libobjc.A.dylib 0x000000018009c084 objc_exception_throw + 72
2 CoreFoundation 0x00000001805092a8 +[NSObject(NSObject) instanceMethodSignatureForSelector:] + 0
3 CoreFoundation 0x00000001804f7cb8 ___forwarding___ + 1196
4 CoreFoundation 0x00000001804fa1fc _CF_forwarding_prep_0 + 92
5 DoubleStrain dev.debug.dylib 0x0000000105d2be78 kfun:dev.gitlive.firebase.auth#toIos__at__dev.gitlive.firebase.auth.ActionCodeSettings(){}cocoapods.FirebaseAuth.FIRActionCodeSettings + 1472
6 DoubleStrain dev.debug.dylib 0x0000000105d27a28 kfun:dev.gitlive.firebase.auth.FirebaseAuth#sendSignInLinkToEmail#suspend(kotlin.String;dev.gitlive.firebase.auth.ActionCodeSettings;kotlin.coroutines.Continuation<kotlin.Unit>){}kotlin.Any + 608 7 DoubleStrain dev.debug.dylib 0x00000001055b95c4
It seems to be caused by calling setDynamicLinkDomain in firebase-ios-sdk which doesn't exist in the version my app depends upon (12.4.0 but also if I upgrade to 12.7.0). Dynamic domains are deprecated and about to go away entirely so losing access to this upstream API wouldn't be a loss at all.
I can work around this locally by swizzling setDynamicLinkDomain to a no-op but it would be much cleaner to not have to do that and it's not a best practice.
I think this could be fixed by upgrading the firebase-cocoapods dependency to a newer version. I'm not sure exactly which one but it seems to be at least one major version behind.
Hello, I'm getting the following crash on iOS:
It seems to be caused by calling
setDynamicLinkDomaininfirebase-ios-sdkwhich doesn't exist in the version my app depends upon (12.4.0but also if I upgrade to12.7.0). Dynamic domains are deprecated and about to go away entirely so losing access to this upstream API wouldn't be a loss at all.I can work around this locally by swizzling
setDynamicLinkDomainto a no-op but it would be much cleaner to not have to do that and it's not a best practice.I think this could be fixed by upgrading the
firebase-cocoapodsdependency to a newer version. I'm not sure exactly which one but it seems to be at least one major version behind.