PFFacebookUtilsDevice or initializeFacebook not found

parse-community / Parse-SDK-iOS-OSX

The Apple SDK for Parse Platform (iOS, macOS, watchOS, tvOS)

https://parseplatform.org

Other

2.81k stars 865 forks source link

PFFacebookUtilsDevice or initializeFacebook not found #1706

Closed yasirmturk closed 5 months ago

yasirmturk commented 1 year ago

New Issue Checklist

[x] I am not disclosing a vulnerability.
[x] I am not just asking a question.
[x] I have searched through existing issues.
[x] I can reproduce the issue with the latest versions of Parse Server and the Parse ObjC SDK.

Issue Description

PFFacebookUtils.initializeFacebook(applicationLaunchOptions: launchOptions) PFFacebookUtilsDevice.initializeFacebook(applicationLaunchOptions: launchOptions)

Steps to reproduce

Download binary, unzip and add to project import ParseFacebookUtilsV4

Actual Outcome

Should be able to initializeFacebook

Expected Outcome

member not found

Environment

Client

Parse ObjC SDK version: 2.0.2

Logs

parse-github-assistant[bot] commented 1 year ago

Thanks for opening this issue!

🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

alexionut commented 6 months ago

Are there any updates on this issue?

mtrezza commented 5 months ago

The only supported install option is via SPM; closing as this issue describes downloading binaries and refers to an older version of the SDK.

alexionut commented 5 months ago

This issue is also in the latest version via SPM. PFFacebookUtils has no member 'initializeFacebook'. And from what I can tell, this issue has existed since the move from cocoapods to SPM. Or am I missing something?

mtrezza commented 5 months ago

If it hasn't already been removed, it will likely be removed in a future version. We do not plan to continue to support these convenience functions anymore, because the choice of Facebook and Twitter is arbitrary, given that there are many more login providers on the market and supported by Parse Server, and the functionality of 3rd party auth is there anyway and it's just a couple of lines of code more for the developer to integrate the auth provider of their choice.