Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't use deprecated TUSClient initializer #37

Merged
merged 1 commit into from
Mar 6, 2024

Conversation

bourquep
Copy link
Contributor

@bourquep bourquep commented Mar 4, 2024

Using the deprecated initializer that takes a URLSession leads to TUSKit not registering its URLSessionDelegate.

See: https://github.com/tus/TUSKit/blob/main/Sources/TUSKit/TUSAPI.swift#L43-L51

By not registering its delegate, API calls never return because their callbacks are never called.

@donnywals
Copy link
Collaborator

This looks like it's mostly good to go. Given that we've only introduced the new init in 3.2 and have done some bug fixes since then, please update the TUSKit version in Package.swift to 3.3.0. The resolved version in this PR has already been updated but I'd like that to be explicit (since resolving to 3.1.5 somehow would not compile)

Using the deprecated initializer that takes a URLSession leads to TUSKit _not_ registering its URLSessionDelegate.

See: https://github.com/tus/TUSKit/blob/main/Sources/TUSKit/TUSAPI.swift#L43-L51

By not registring its delegate, API calls never return because their callbacks are never called.
@bourquep
Copy link
Contributor Author

bourquep commented Mar 5, 2024

Done!

@donnywals donnywals merged commit 522921e into transloadit:main Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants