Module 'FBSDKCoreKit' not found #1102

dafong · 2019-11-08T12:47:22Z

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, the Facebook Developer Community Forum 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

Xcode Version: 11.2
Cocoapods 1.8.4
Facebook SDK Version 5.10
Unity2017.4.33f1

Goals

build iOS Project Successful

Expected Results

no compile error

Actual Results

has compile error
" Module 'FBSDKCoreKit' not found "

Steps to Reproduce

export iOS Project from Unity and build

Code Samples & Details

notice the error from below code

#ifdef BUCK
#import <FBSDKCoreKit/FBSDKCoreKit.h>
#else
@import FBSDKCoreKit;
#endif

the compile execute the else part then throw a error.

when replace all these code with

#import <FBSDKCoreKit/FBSDKCoreKit.h>

it work's perfect.

The text was updated successfully, but these errors were encountered:

dafong · 2019-11-08T12:49:55Z

It seems add these code in version 5.9 and 5.10. if change back the version to 5.8. It's still ok

katou-o · 2019-11-08T13:17:19Z

The downgrade from version 5.10 to 5.8 worked for me. Thank you.

joesus · 2019-11-08T15:16:37Z

Is this issue unity specific? Are you able to reproduce this using FBSDKCoreKit v5.10.0 via Cocoapods in a sample project?

joesus · 2019-11-08T15:21:33Z

I ask because in a new sample project with a very simple Podfile that just includes:
pod 'FBSDKCoreKit'
I am able to import into a Swift file with:
import FBSDKCoreKit
and build without issue.

Have you tried cleaning and removing derived data? (probably not the solution but usually helps surface things)

polmum · 2019-11-08T15:29:18Z

I ask because in a new sample project with a very simple Podfile that just includes:
pod 'FBSDKCoreKit'
I am able to import into a Swift file with:
import FBSDKCoreKit
and build without issue.

Have you tried cleaning and removing derived data? (probably not the solution but usually helps surface things)

Are you using use_frameworks! in your sample project? Without it, the import should fail.

Also, adding the modular_headers flag should fix the issue:
pod 'FBSDKCoreKit', :modular_headers => true

nicolasform · 2019-11-08T17:43:55Z

Same error with this config:

    Xcode Version: 11.2
    Cocoapods 1.6.1
    Facebook SDK Version 5.10
    Unity2019.2.11f1

I solved the problem by doing the following:

Edit the file Podfile at the root of the xcode project
Replace '~> 5.2' by '5.8.0' in all the Facebook pods
Run 'pod install' from a terminal at the root of the project
Build the project in xcode, it should work

Here is my full Podfile in case you need more details:

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '10.0'

target 'Unity-iPhone' do
  pod 'Crashlytics', '3.13.1'
  pod 'Fabric', '1.10.1'
  pod 'FBSDKCoreKit', '5.8.0'
  pod 'FBSDKLoginKit', '5.8.0'
  pod 'FBSDKShareKit', '5.8.0'
  pod 'Firebase/Core', '6.1.0'
  pod 'Firebase/DynamicLinks', '6.1.0'
end

joesus · 2019-11-08T17:55:42Z

@nicolasform, using the modular_headers => true flag, I was able to compile your podfile in a sample project.

This is clearly not a good solution and I will revisit using @import syntax or alternately see if there is a way to do this at the Podspec level.

Apologies for the inconvenience. Going to close this for now as there is a plan to fix as well as the two workarounds:

Using the modular_headers => true flag
Rolling back to 5.8

Thanks a ton @polmum for saving me the valuable time of finding the modular headers fix. :D

joesus · 2019-11-08T19:10:41Z

Pushed updated versions of the pods. Please try again without any workarounds. :D

bobber205 · 2019-11-08T19:22:25Z

@joesus I don't see any new releases. Any advice on how to get the update "to take"?

joesus · 2019-11-08T19:48:28Z

@joesus I don't see any new releases. Any advice on how to get the update "to take"?

It is bad practice but I decided it made sense in this case to overwrite the pushed pods because they were mis-released and unusable. If you deintegrate your pods 'pod deintegrate' and reinstall 'pod install' you should get the current code.

I would also recommend the usual incantation of deleting derived data and cleaning the build folder.

thiagosmagalhaes · 2019-11-09T00:37:43Z

I ask because in a new sample project with a very simple Podfile that just includes:
pod 'FBSDKCoreKit'
I am able to import into a Swift file with:
import FBSDKCoreKit
and build without issue.
Have you tried cleaning and removing derived data? (probably not the solution but usually helps surface things)

Are you using use_frameworks! in your sample project? Without it, the import should fail.

Also, adding the modular_headers flag should fix the issue:
pod 'FBSDKCoreKit', :modular_headers => true

Thanks, that solved my problem after a lot of brainstorming trying to solve

floriangbh · 2019-11-10T14:04:32Z

Hello,

I think I have the same issue with v5.10.0. I'm trying to migrate my pods to SPM, but I have this error after migrate FBSDK to SPM :

Some of my pods aren't SPM compliant so I can't remove Cocoapods at this moment.

joesus · 2019-11-10T15:55:02Z

@floriangbh, thanks for bringing this up! I am kicking myself! 😣Fix pushed to #1106. Feel free to point your package to that branch and let me know if it works. Hoping to get this into the first patch release sometime in the near future!

floriangbh · 2019-11-10T17:16:08Z

@joesus thanks for the quick-fix ! It seem to be ok when I targeting the cocoapods-preprocessor-fix branch. Thanks !

tgensol · 2019-11-12T08:22:12Z

On my side the branch didn't change anything, I was still unable to compile, but :modular_headers => true fixed it

nilsk123 · 2019-11-12T11:12:19Z

On my side the branch didn't change anything, I was still unable to compile, but :modular_headers => true fixed it

same here, this is not fixed yet

raulrom13 · 2019-11-14T09:51:32Z

Same here, with version 5.10.1 this is not fixed yet.

stkman · 2019-11-14T10:05:59Z

really stupid...

regevbr · 2019-11-14T16:17:34Z

5.8.0 doesn't work for me...

cosgunhalil · 2019-11-14T16:23:47Z

Open Xcode and add -fcxx-modules to Build Settings->Other C++ Flags->Debug and Release fields.
https://stackoverflow.com/questions/58853168/xcode-11-2-111b53-import-fbsdkcorekit-error

adamlucktastic · 2019-11-14T20:59:34Z

Yes as stated above, the facebook-unity-sdk-7.17.2 worked when it pointed to version 5.8.
5.10 no longer works
You can just update your Dependencies.xml file
<?xml version="1.0" encoding="utf-8"?> <dependencies> <androidPackages> <androidPackage spec="com.parse.bolts:bolts-android:1.4.0" /> <androidPackage spec="com.facebook.android:facebook-core:[5,6)" /> <androidPackage spec="com.facebook.android:facebook-applinks:[5,6)" /> <androidPackage spec="com.facebook.android:facebook-login:[5,6)" /> <androidPackage spec="com.facebook.android:facebook-share:[5,6)" /> </androidPackages> <iosPods> <iosPod name="Bolts" version="~> 1.7" /> <iosPod name="FBSDKCoreKit" version="5.8" /> <iosPod name="FBSDKLoginKit" version="5.8" /> <iosPod name="FBSDKShareKit" version="5.8" /> </iosPods> </dependencies>

umairh2018 · 2019-11-18T12:27:29Z

Yes as stated above, the facebook-unity-sdk-7.17.2 worked when it pointed to version 5.8.
5.10 no longer works
You can just update your Dependencies.xml file
<?xml version="1.0" encoding="utf-8"?> <dependencies> <androidPackages> <androidPackage spec="com.parse.bolts:bolts-android:1.4.0" /> <androidPackage spec="com.facebook.android:facebook-core:[5,6)" /> <androidPackage spec="com.facebook.android:facebook-applinks:[5,6)" /> <androidPackage spec="com.facebook.android:facebook-login:[5,6)" /> <androidPackage spec="com.facebook.android:facebook-share:[5,6)" /> </androidPackages> <iosPods> <iosPod name="Bolts" version="~> 1.7" /> <iosPod name="FBSDKCoreKit" version="5.8" /> <iosPod name="FBSDKLoginKit" version="5.8" /> <iosPod name="FBSDKShareKit" version="5.8" /> </iosPods> </dependencies>

Its a stupid question but i really don't know where do i update 5.8 inplace of 5.10.
& how to & where to add
pod 'FBSDKCoreKit', :modular_headers => true

joesus · 2019-11-18T16:17:50Z

Should be fixed for Unity projects with: #1122

umairh2018 · 2019-11-18T16:56:22Z

I couldn't avle to resolve this issue. Kindly guide me if any1 resolved this issue

…

On Mon, 18 Nov 2019, 9:18 pm Joe Susnick, ***@***.***> wrote: Should be fixed for Unity projects with: #1122 <#1122> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1102?email_source=notifications&email_token=ALX3CE27J6DL6SJ3D4TSHPTQUK545A5CNFSM4JKW2PE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEK75YA#issuecomment-555089632>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALX3CE7TFRJ3FQ35TW4SY43QUK547ANCNFSM4JKW2PEQ> .

jeffposey · 2019-11-27T00:30:35Z

Yep, we are still stuck.

pod 'FBSDKCoreKit', :modular_headers => true

Does not seem to change anything. We need more information.

I changed all 10 files to #import instead of @import, and then it was all reverted the next build I made.

jeffposey · 2019-11-27T00:57:02Z

Ok, thanks. I believe this was installed from the Unity package 'facebook-unity-sdk-7.18.0' so I will try 'facebook-unity-sdk-7.17.2' which sounds like it uses 5.8?

adamlucktastic · 2019-11-27T01:09:19Z

The problem is that they use ~> 5.2 which is picking the latest 5.x build. So you just need to find your Dependencies.xml file and change the ~> 5.2 to = 5.8

…

On Nov 26, 2019, at 7:57 PM, jeffposey ***@***.***> wrote: Ok, thanks. I believe this was installed from the Unity package 'facebook-unity-sdk-7.18.0' so I will try 'facebook-unity-sdk-7.17.2' which sounds like it uses 5.8? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

amirkhavari99 · 2019-11-30T10:58:11Z

After I update from ~> 5.2 to 5.8.0 the CoreKit problem disappears buy now ShareKit is not found, Could you please release a new Facebook SDK for Unity if you have solved it in iOS? None of the Unity SDK versions build on iOS and I really don't know what should we do, we are stuck here.

riazhazan · 2019-12-06T11:45:12Z

Same error with this config:
    Xcode Version: 11.2
    Cocoapods 1.6.1
    Facebook SDK Version 5.10
    Unity2019.2.11f1
I solved the problem by doing the following:

Edit the file Podfile at the root of the xcode project

Replace '~> 5.2' by '5.8.0' in all the Facebook pods

Run 'pod install' from a terminal at the root of the project

Build the project in xcode, it should work

Here is my full Podfile in case you need more details:
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '10.0'

target 'Unity-iPhone' do
  pod 'Crashlytics', '3.13.1'
  pod 'Fabric', '1.10.1'
  pod 'FBSDKCoreKit', '5.8.0'
  pod 'FBSDKLoginKit', '5.8.0'
  pod 'FBSDKShareKit', '5.8.0'
  pod 'Firebase/Core', '6.1.0'
  pod 'Firebase/DynamicLinks', '6.1.0'
end

This solved my issue.

adamlucktastic · 2020-01-09T14:33:09Z

did you try 5.8 instead of 5.8.0 ?

…

On Thu, Jan 9, 2020 at 3:10 AM Jason Phan ***@***.***> wrote: Neither solution worked for me. flutter clean, clear DerivedData, pod deintegrate, then even tried explicitly stating FBSDK* to be 5.8.0 and set modular header to true in podfile did not do the trick. App is still running perfectly fine in the iOS/Android emulators. pod 'FBSDKCoreKit', '5.8.0', :modular_headers => true pod 'FBSDKLoginKit', '5.8.0' Any other suggestions? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1102?email_source=notifications&email_token=AGJLYGBUU2G6D6UBQJYALIDQ43LY5A5CNFSM4JKW2PE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIPMPMQ#issuecomment-572442546>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJLYGBTZZGFKJ4REXCZRHDQ43LY5ANCNFSM4JKW2PEQ> .

iojason · 2020-01-10T02:44:50Z

@adamlucktastic - I tried '5.8'; still set to 5.8.0 with the same error. So far, I've tried downgrading the version to 5.8, use modular headers, add missing framework search path, and manually add the framework but no luck - Nothing works. The weird thing is building succeeds and I'm able to login successfully via Facebook on the iOS emulator. I just can't archive it to publish the app.

umairh2018 · 2020-01-10T05:02:10Z

Have you install pod for unity build Xcode project. It helped me fix the issue. Write cd & drag Unity-iphone.xcodeproj in terminal & press enter then write pod install in terminal. it will install pod file & xcworkspace file in your Xcode project. open that file & build the Xcode project from Xcode. I hope it helps.

…

On Fri, Jan 10, 2020 at 7:44 AM Jason Phan ***@***.***> wrote: @adamlucktastic <https://github.com/adamlucktastic> - I tried '5.8'; still set to 5.8.0 with the same error. So far, I've tried downgrading the version to 5.8, use modular headers, add missing framework search path, and manually add the framework but no luck - Nothing works. The weird thing is building succeeds and I'm able to login successfully via Facebook on the iOS emulator. I just can't archive it to publish the app. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1102?email_source=notifications&email_token=ALX3CE5FO3SAFFKMCO642ATQ47OKJA5CNFSM4JKW2PE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEISPTBA#issuecomment-572848516>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALX3CE2M7KJFDN3WTYLCGB3Q47OKJANCNFSM4JKW2PEQ> .

ZebingZong · 2020-01-10T06:52:35Z

For anyone that this issue still happens, can you guys try to add use_frameworks! after platform :ios, '9.0' as a new line to see whether it fixes the issue? Here is an example Podfile

platform :ios, '9.0'

use_frameworks!

target 'ASRIOS' do

  # Pods for ASRIOS
  pod 'FBSDKCoreKit', '5.11.1'
  pod 'FBSDKLoginKit', '5.11.1'
  pod 'FBSDKShareKit', '5.11.1'

  target 'ASRIOSTests' do
    inherit! :search_paths
    # Pods for testing
  end

  target 'ASRIOSUITests' do
    # Pods for testing
  end

end

iojason · 2020-01-10T06:57:44Z

@ZebingZong I tried setting use_frameworks! right after platform declaration as well but no luck. I even tested it with use_modular_headers! but still can't archive the iOS app. I created a new Flutter app and able to archive it with no problem. There's something funky going on with FB SDK. It's never good to have too many dependencies/pods - I'm considering an alternative login method.

iojason · 2020-01-10T06:58:45Z

@umairh2018 Thanks for the help. I'm actually using FBSDK on Flutter iOS. Tested most of the solutions proposed on the web and still unable to archive it. Possibly building an alternative by end of the week.

ZebingZong · 2020-01-10T07:05:55Z

@jasondphan sorry for the unpleasure experience but we are actively working on the fix. Because it is holidays seasons, so the response is slower than usual. Have you tried with some early versions of FBSDK (e.g., 5.5.0) to unblock yourself? And please make sure you delete 1) Podfile.lock 2) Pods folder 3) yourprojectname.xcworkspace. And also clean the build for xcode before you try to build new project with new podfile.

iojason · 2020-01-10T07:28:32Z

@ZebingZong Thank you for working on a fix for this critical error. Yes, I've been carefully cleaning and deleting the needed files/folders before each podfile run. Just tested it with 5.5.0 and can't archive. After commenting out import FBSDKCoreKit in the AppDelegate.swift to see where it takes me, I'm now getting errors in the GeneratedPluginRegistrant.m file stating some of the @import modules are missing. Not sure if this is related or another Swift/Obj-C issue.

` - FBSDKCoreKit (5.5.0):
- FBSDKCoreKit/Basics (= 5.5.0)
- FBSDKCoreKit/Core (= 5.5.0)

FBSDKCoreKit/Basics (5.5.0)
FBSDKCoreKit/Core (5.5.0):
- FBSDKCoreKit/Basics
FBSDKLoginKit (5.5.0):
- FBSDKCoreKit (~> 5.0)`

ZebingZong · 2020-01-10T07:34:24Z

Hmm, it is very interesting. Can you please share the podfile for your project? Also which interface that you are using for FBSDK (Objective-C / Swift / Unity)?

iojason · 2020-01-10T07:41:56Z

The interface is compiled to Objective-C from Flutter and using flutter_facebook_login package.

Podfile below:
`// Uncomment this line to define a global platform for your project
platform :ios, '11.0'

// CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
'Debug' => :debug,
'Profile' => :release,
'Release' => :release,
}

def parse_KV_file(file, separator='=')
file_abs_path = File.expand_path(file)
if !File.exists? file_abs_path
return [];
end
generated_key_values = {}
skip_line_start_symbols = ["//", "/"]
File.foreach(file_abs_path) do |line|
next if skip_line_start_symbols.any? { |symbol| line =~ /^\s*//{symbol}/ }
plugin = line.split(pattern=separator)
if plugin.length == 2
podname = plugin[0].strip()
path = plugin[1].strip()
podpath = File.expand_path("//{path}", file_abs_path)
generated_key_values[podname] = podpath
else
puts "Invalid plugin specification: //{line}"
end
end
generated_key_values
end

target 'Runner' do
use_frameworks!
use_modular_headers!

// Flutter Pod

copied_flutter_dir = File.join(dir, 'Flutter')
copied_framework_path = File.join(copied_flutter_dir, 'Flutter.framework')
copied_podspec_path = File.join(copied_flutter_dir, 'Flutter.podspec')
unless File.exist?(copied_framework_path) && File.exist?(copied_podspec_path)
// Copy Flutter.framework and Flutter.podspec to Flutter/ to have something to link against if the xcode backend script has not run yet.
// That script will copy the correct debug/profile/release version of the framework based on the currently selected Xcode configuration.
// CocoaPods will not embed the framework on pod install (before any build phases can generate) if the dylib does not exist.

generated_xcode_build_settings_path = File.join(copied_flutter_dir, 'Generated.xcconfig')
unless File.exist?(generated_xcode_build_settings_path)
  raise "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first"
end
generated_xcode_build_settings = parse_KV_file(generated_xcode_build_settings_path)
cached_framework_dir = generated_xcode_build_settings['FLUTTER_FRAMEWORK_DIR'];

unless File.exist?(copied_framework_path)
  FileUtils.cp_r(File.join(cached_framework_dir, 'Flutter.framework'), copied_flutter_dir)
end
unless File.exist?(copied_podspec_path)
  FileUtils.cp(File.join(cached_framework_dir, 'Flutter.podspec'), copied_flutter_dir)
end

end

// Keep pod path relative so it can be checked into Podfile.lock.
pod 'Flutter', :path => 'Flutter'

// Plugin Pods

// Prepare symlinks folder. We use symlinks to avoid having Podfile.lock
// referring to absolute paths on developers' machines.
system('rm -rf .symlinks')
system('mkdir -p .symlinks/plugins')
plugin_pods = parse_KV_file('../.flutter-plugins')
plugin_pods.each do |name, path|
symlink = File.join('.symlinks', 'plugins', name)
File.symlink(path, symlink)
pod name, :path => File.join(symlink, 'ios')
end
end

// Prevent Cocoapods from embedding a second Flutter framework and causing an error with the new Xcode build system.
install! 'cocoapods', :disable_input_output_paths => true

// To resolve FirebaseCore missing headers when building for iOS
system("mkdir -p Pods/Headers/Public/FirebaseCore && cp Pods/FirebaseCore/Firebase/Core/Public/* Pods/Headers/Public/FirebaseCore/")
end

pod 'Firebase/Analytics'
pod 'Firebase/AdMob'

// pod 'FBSDKCoreKit' // didn't work
// pod 'FBSDKCoreKit', :modular_headers => true // didn't work
// pod 'FBSDKCoreKit', '5.8', :modular_headers => true

// Didn't work
//pod 'FBSDKCoreKit', '5.8'
//pod 'FBSDKLoginKit', '5.8'

// Didn't work
//pod 'FBSDKCoreKit', '5.8', :modular_headers => true
//pod 'FBSDKLoginKit', '5.8'

// pod 'FBSDKCoreKit', '~> 5.8', :modular_headers => true // didn't work
pod 'FBSDKCoreKit', '5.5.0'
pod 'FBSDKLoginKit', '5.5.0'`

ZebingZong · 2020-01-10T07:45:36Z

So to make sure I understand your issue, you are actually being able to compile and build the project with FBSDK but only encounter the issue when you are trying to archive it. If this is correct, I think your issue is not directly related to this one. I would suggest you to open another issue and give detailed explanation there to avoid the confusion. Thanks for your cooperation!

iojason · 2020-01-10T07:58:38Z

So to make sure I understand your issue, you are actually being able to compile and build the project with FBSDK but only encounter the issue when you are trying to archive it. If this is correct, I think your issue is not directly related to this one. I would suggest you to open another issue and give detailed explanation there to avoid the confusion. Thanks for your cooperation!

Correct, "Module 'FBSDKCoreKit' not found" when trying to archive to publish the app. I'll create a separate issue if I can't solve this by end of Sunday or use a different login method. Thanks for your time @ZebingZong

adamlucktastic · 2020-01-10T13:04:37Z

Are you having archiving or distributing to the store. Can you provide some of the errors you’re seeing ?

…

On Jan 10, 2020, at 12:02 AM, umairh2018 ***@***.***> wrote: Have you install pod for unity build Xcode project. It helped me fix the issue. Write cd & drag Unity-iphone.xcodeproj in terminal & press enter then write pod install in terminal. it will install pod file & xcworkspace file in your Xcode project. open that file & build the Xcode project from Xcode. I hope it helps. On Fri, Jan 10, 2020 at 7:44 AM Jason Phan ***@***.***> wrote: > @adamlucktastic <https://github.com/adamlucktastic> - I tried '5.8'; > still set to 5.8.0 with the same error. So far, I've tried downgrading the > version to 5.8, use modular headers, add missing framework search path, and > manually add the framework but no luck - Nothing works. The weird thing is > building succeeds and I'm able to login successfully via Facebook on the > iOS emulator. I just can't archive it to publish the app. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#1102?email_source=notifications&email_token=ALX3CE5FO3SAFFKMCO642ATQ47OKJA5CNFSM4JKW2PE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEISPTBA#issuecomment-572848516>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ALX3CE2M7KJFDN3WTYLCGB3Q47OKJANCNFSM4JKW2PEQ> > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

developer239 · 2020-01-16T00:39:28Z

How is this closed? 😂

developer239 · 2020-01-16T00:40:25Z

Also rolling back to 5.8 is not a solution. 🙂

iojason · 2020-01-16T01:05:09Z

Are you having archiving or distributing to the store. Can you provide some of the errors you’re seeing ?
…
On Jan 10, 2020, at 12:02 AM, umairh2018 @.> wrote: Have you install pod for unity build Xcode project. It helped me fix the issue. Write cd & drag Unity-iphone.xcodeproj in terminal & press enter then write pod install in terminal. it will install pod file & xcworkspace file in your Xcode project. open that file & build the Xcode project from Xcode. I hope it helps. On Fri, Jan 10, 2020 at 7:44 AM Jason Phan @.> wrote: > @adamlucktastic https://github.com/adamlucktastic - I tried '5.8'; > still set to 5.8.0 with the same error. So far, I've tried downgrading the > version to 5.8, use modular headers, add missing framework search path, and > manually add the framework but no luck - Nothing works. The weird thing is > building succeeds and I'm able to login successfully via Facebook on the > iOS emulator. I just can't archive it to publish the app. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#1102?email_source=notifications&email_token=ALX3CE5FO3SAFFKMCO642ATQ47OKJA5CNFSM4JKW2PE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEISPTBA#issuecomment-572848516>, > or unsubscribe > https://github.com/notifications/unsubscribe-auth/ALX3CE2M7KJFDN3WTYLCGB3Q47OKJANCNFSM4JKW2PEQ > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

@adamlucktastic - Archiving to release to the App store. It's working perfectly on the emulator. The only error I was seeing was "Module 'FBSDKCoreKit' not found". I even tried writing a custom header but it wouldn't take it. Tried Swift 4.2 and 5 too. In the end, I opted for a better login method for my target audience. Thanks for jumping in.

@developer239 - word.

mtfum · 2020-01-18T08:17:41Z

Changing pod 'FBSDKCoreKit' to pod 'FacebookCore' solved in my case!

#1132 (comment)

joesus · 2020-01-18T16:03:50Z

Changing pod 'FBSDKCoreKit' to pod 'FacebookCore' solved in my case!

#1132 (comment)

Please do not do or advise doing this.
These are different pods. ‘FacebookCore’ will pull down the deprecated Facebook Swift SDK. You absolutely DO NOT want to use this pod. It will not have critical bug fixes.

Happy to help diagnose the issue with using the latest version of the FBSDKCoreKit pod.

Also, just so we can improve the documentation. How did you decide to use ‘pod FacebookCore’? Did you read this somewhere?

mtfum · 2020-01-18T17:48:05Z

@joesus
Thanks for your advice.
At first, I read Facebook Analytics Quickstart Guide for iOS
So I didn't notice that.

joesus · 2020-01-18T17:55:55Z

@joesus
Thanks for your advice.
At first, I read Facebook Analytics Quickstart Guide for iOS
So I didn't notice that.

Good to know! I’ll make sure we get that updated to avoid future confusion!

umairh2018 · 2020-01-20T19:33:08Z

Anybody can resolve my this issue https://stackoverflow.com/questions/59062922/facebook-banner-ad-issue-in-unity Can't able to use banner ad in unity

…

On Sat, 18 Jan 2020, 10:55 pm Joe Susnick, ***@***.***> wrote: @joesus <https://github.com/joesus> Thanks for your advice. At first, I read Facebook Analytics Quickstart Guide for iOS <https://developers.facebook.com/docs/analytics/quickstart-list/ios> So I didn't notice that. Good to know! I’ll make sure we get that updated to avoid future confusion! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1102?email_source=notifications&email_token=ALX3CEYT3WGKSV5VQCV36KLQ6M7C5A5CNFSM4JKW2PE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJJ6H7A#issuecomment-575923196>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALX3CE5AOCA4WPYPVZ6P44TQ6M7C5ANCNFSM4JKW2PEQ> .

umairh2018 · 2020-01-21T09:03:01Z

I am using the facebook audience network in Unity for advertisement. I am currently facing an issue while showing facebook banner ads in unity. Just when i call banner ad show call. Exception triggers:

java.lang.illegalargumentexception: adsize at com.facebook.ads.redexgen.x.8h.(:18251)

Anybody knows how can I resolve this issue? Thanks in advance

joesus · 2020-01-22T17:18:13Z

@umairh2018 please open a new issue with steps to reproduce.

joesus · 2020-01-22T17:19:40Z

The openers issue has been resolved. Comments on this issue are not longer helpful. Locking it.

This comment has been minimized.

Sign in to view

joesus closed this as completed Nov 8, 2019

tgensol mentioned this issue Nov 12, 2019

Project does not compile anymore after updating to 5.10.0 #1105

Closed

atavci mentioned this issue Nov 14, 2019

fatal error: module 'FBSDKCoreKit' not found roughike/flutter_facebook_login#214

Open

DawnKing mentioned this issue Nov 18, 2019

FB SDK 7.18.0 - Module 'FBSDKCoreKit' not found facebook/facebook-sdk-for-unity#352

Closed

5 tasks

dmitryermichev mentioned this issue Dec 16, 2019

FBSDKHashtag.h:24:9: Module 'FBSDKCoreKit' not found facebookarchive/react-native-fbsdk#684

Open

facebook locked as off-topic and limited conversation to collaborators Jan 22, 2020

Module 'FBSDKCoreKit' not found #1102

Module 'FBSDKCoreKit' not found #1102

Comments

dafong commented Nov 8, 2019

Checklist

Environment

Goals

Expected Results

Actual Results

Steps to Reproduce

Code Samples & Details

dafong commented Nov 8, 2019

katou-o commented Nov 8, 2019

This comment has been minimized.

joesus commented Nov 8, 2019

joesus commented Nov 8, 2019

polmum commented Nov 8, 2019

nicolasform commented Nov 8, 2019

joesus commented Nov 8, 2019

joesus commented Nov 8, 2019

bobber205 commented Nov 8, 2019

joesus commented Nov 8, 2019

thiagosmagalhaes commented Nov 9, 2019

floriangbh commented Nov 10, 2019

joesus commented Nov 10, 2019

floriangbh commented Nov 10, 2019

tgensol commented Nov 12, 2019

nilsk123 commented Nov 12, 2019

raulrom13 commented Nov 14, 2019

stkman commented Nov 14, 2019

regevbr commented Nov 14, 2019

cosgunhalil commented Nov 14, 2019

adamlucktastic commented Nov 14, 2019 • edited

umairh2018 commented Nov 18, 2019

joesus commented Nov 18, 2019

umairh2018 commented Nov 18, 2019 via email

jeffposey commented Nov 27, 2019

jeffposey commented Nov 27, 2019

adamlucktastic commented Nov 27, 2019 via email

amirkhavari99 commented Nov 30, 2019

riazhazan commented Dec 6, 2019

adamlucktastic commented Jan 9, 2020 via email

iojason commented Jan 10, 2020

umairh2018 commented Jan 10, 2020 via email

ZebingZong commented Jan 10, 2020

iojason commented Jan 10, 2020

iojason commented Jan 10, 2020

ZebingZong commented Jan 10, 2020 • edited

iojason commented Jan 10, 2020

ZebingZong commented Jan 10, 2020 • edited

iojason commented Jan 10, 2020 • edited

ZebingZong commented Jan 10, 2020

iojason commented Jan 10, 2020

adamlucktastic commented Jan 10, 2020 via email

developer239 commented Jan 16, 2020

developer239 commented Jan 16, 2020 • edited

iojason commented Jan 16, 2020

mtfum commented Jan 18, 2020

joesus commented Jan 18, 2020 • edited

mtfum commented Jan 18, 2020

joesus commented Jan 18, 2020

umairh2018 commented Jan 20, 2020 via email

umairh2018 commented Jan 21, 2020

joesus commented Jan 22, 2020

joesus commented Jan 22, 2020 • edited

adamlucktastic commented Nov 14, 2019 •

edited

ZebingZong commented Jan 10, 2020 •

edited

ZebingZong commented Jan 10, 2020 •

edited

iojason commented Jan 10, 2020 •

edited

developer239 commented Jan 16, 2020 •

edited

joesus commented Jan 18, 2020 •

edited

joesus commented Jan 22, 2020 •

edited