Closed wendyliga closed 2 months ago
@GuidoPu please help check this PR :pray:
While this technically works, I would personally recommend against this fix and use a proper one instead (not making external types conform to an internal protocol).
When using this fix, I had another issue when calling applicationInstance.open(url, options: [:], completionHandler: nil)
: Ambiguous use of 'open(_:options:completionHandler:)'
.
This is due to the completionHandler parameter having two possible types now: (@MainActor @Sendable (Bool) -> Void)?
and ((Bool) -> Void)?
.
To fix this issue one has now to call the open
method using open(url, options: [:], completionHandler: nil as (@MainActor @Sendable (Bool) -> Void)?)
, which is terrible.
While this technically works, I would personally recommend against this fix and use a proper one instead (not making external types conform to an internal protocol).
When using this fix, I had another issue when calling
applicationInstance.open(url, options: [:], completionHandler: nil)
:Ambiguous use of 'open(_:options:completionHandler:)'
.This is due to the completionHandler parameter having two possible types now:
(@MainActor @Sendable (Bool) -> Void)?
and((Bool) -> Void)?
. To fix this issue one has now to call theopen
method usingopen(url, options: [:], completionHandler: nil as (@MainActor @Sendable (Bool) -> Void)?)
, which is terrible.
So how did you fix that?
@WineKai I invite you to read literally the last sentence of the message you’re replying to: it’s the fix.
Guys. Did you check the latest release 2.5.0? Xcode 16.0 works for me
Confirmed, 2.5 works.
@WineKai I invite you to read literally the last sentence of the message you’re replying to: it’s the fix.
Ha ha ha, I see it. Thanks
as title described