Skip to content
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.

VimeoClient init creates memory leak #430

Open
PawelAmbrozej opened this issue Jan 13, 2021 · 0 comments
Open

VimeoClient init creates memory leak #430

PawelAmbrozej opened this issue Jan 13, 2021 · 0 comments

Comments

@PawelAmbrozej
Copy link

Using Debug Memory Graph in Xcode I noticed that whenever I create VimeoClient, it creates memory leak in the app. To confirm if this is not because my app creates that, I created dummy app with just one UIViewController and with this test code:

class ViewController: UIViewController {
    override func viewDidLoad() {
        super.viewDidLoad()
        let appConfiguration = AppConfiguration(
            clientIdentifier: Constant.VIMEO_CLIENT_IDENTIFIER,
            clientSecret: Constant.VIMEO_CLIENT_SECRETS,
            scopes: [.Public, .Private, .Interact, .Create, .Delete, .Edit],
            keychainService: Constant.VIMEO_KEYCHAIN_SERVICE)
        let vimeoClient = VimeoClient(appConfiguration: appConfiguration)
        let authenticationController = AuthenticationController(client: vimeoClient, appConfiguration: appConfiguration) { (vimeoSessionManager) -> VimeoSessionManager in
            return vimeoSessionManager
        }
    }
}

This is what I get in Memory Graph after running the app:

Screenshot 2021-01-13 at 14 15 38

Any ideas what can cause that or maybe my implementation is wrong ?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant