Latest version - Use of unresolved identifier 'AppEventsLogger'

[guidev]

Checklist

• I've updated to the latest released version of the SDK
• I've searched for existing GitHub issues
• I've looked for existing answers on Stack Overflow and the Facebook Developers Group
• I've read the Code of Conduct
• This issue is not security related and can safely be disclosed publicly on GitHub

Environment

Describe your dev environment here, giving as many details as possible. If you have them, make sure to include:

• Xcode Version: 10.2.1
• Swift Version: 5.0
• Installation Platform & Verison: [Cocoapods] version 1.6.1

Goals

Upgrade from FacebookCore 0.6.0 to FacebookCore 0.7.0

Expected Results

Being able to upgrade without any major change to the code.

Actual Results

AppEventsLogger is undefined.

Steps to Reproduce

Code Samples & Details

My Podfile

platform :ios, '9.0'
use_frameworks!
inhibit_all_warnings!

target 'Cinema' do
  pod 'SDWebImage'
  pod 'Fabric'
  pod 'Crashlytics'
  pod 'Alamofire'
  pod 'ObjectMapper'
  pod 'FacebookCore'
  pod 'Firebase/Core'
  pod 'Firebase/Performance'
end

[maksymhusar]

The same for me

[dfmarulanda]

Nothing is working in 0.7.0.
I had to downgrade.

[ethanwa]

Same problem for me as well.

[iKisliy]

Same for me

[adrianorezena]

I had the same problem and the changed the AppEventsLogger.log to AppEvents.logEvent.

It's compiling and logging for me now, but in the test events each log seems to be quadruplicated.
Does anyone had the same problem?

[iKisliy]

@adrianorezena did you had changed your .activate method? Neither AppEventsLogger.activate, nor AppEvents.activate works

[adrianorezena]

@iKisliy , have you tried AppEvents.activateApp()?

[AmrKafina]

Yup, spent more than two hours trying to integrate the SDK with my app.

[sglushchenko]

I added
pod 'FacebookSDK'
and use

import FBSDKCoreKit
...
AppEvents.activateApp()

[NikitaSkripchenko]

@dfmarulanda on which one you had downgraded?

[mouness2020]

same problem here

[piyush-cashify]

Facing same issue

[geronimowheeli]

Having the same problem. Going to downgrade right now.

[dfmarulanda]

13 days and @facebook-github-bot hasn't fixed this yet. SHAME

[idrougge]

One month…

[andrassomogyi]

Any workaround for this?

[kershner]

Can someone please walk through their steps for a working solution, via downgrading or otherwise? This is still very much a problem, and I bet most people who go to implement the SDK in their Swift apps using the official FB docs are going to end up here sooner or later.

[piyush-cashify]

Can someone please walk through their steps for a working solution, via downgrading or otherwise? This is still very much a problem, and I bet most people who go to implement the SDK in their Swift apps using the official FB docs are going to end up here sooner or later.

#463 (comment)

[rromanchuk]

The official docs are a complete mess, has anyone dug into the source to figure out what the actual signatures are to send analytics. All these language specific are bogus.

[joesus]

So the long story is that this SDK is a wrapper around the ObjC SDK. There's a little more information about this in the recently merged roadmap.

TLDR: If you look at the changes between v0.6.0 and v0.7.0 - compare we updated to point to version 5.0 of the ObjC SDK. This was a breaking change and we should have cut a major release to reflect that. We also deprecated a number of wrapper classes including AppEventsLogger.

Those changes constituted a major effort to enhance the usability of the Swift interface that's generated from the ObjC SDK but it was not communicated well in terms of this project. The changes are documented reasonably well in this changelog under the 5.0 release.

While it is completely reasonable to be upset about this series of events, I hope that this is enough explanation to unblock people who upgraded. Closing the issue as this was a bug in an evolving process and cannot be fixed by a simple code change.

[moesalih]

@joesus the docs you're linking to don't say what changes were done to AppEventsLogger. What's the solution? This is not resolved.

[joesus]

@moesalih, good call. I just merged a pr to update the changelog so it's easier to see what was changed on the Swift SDK end of things. Check out: v0.6.0...v0.7.0

I just realized I referenced this change-set in the previous message but did not call out the Swift changes specifically. I updated the previous message to include that breadcrumb. Thanks for bringing that to my attention!

[ethanwa]

For those who have simple implementations, the answer to get things working is simply this change:

AppEventsLogger.activate(application)

is now

AppEvents.activateApp()