capacitor-community / facebook-login

Facebook Login support
MIT License
103 stars 52 forks source link

Problem on iOS Intel CPU: version 4.0.0 (and version 4.0.0-1) don't work on real device (Android, Xcode Simulator with Intel Cpu and ARM real devices / Simulators work fine) #104

Closed ciccilleju closed 1 year ago

ciccilleju commented 1 year ago

hello, I'm developing a Ionic Capacitor 4 app.

My computer is an iMac with monterey and Intel I7 CPU

Until this morning I was using succesfuly plugin's version 3.4.0, after the update it doesn't work anymore. I've tried removing and reistalling the plugin again without any luck on real device (it still seems to be working on simulator)

I get this kind of error if I install it on a real device

image image

Showing All Messages Building for iOS, but linking in dylib file (/Users/francescodegiorgio/Library/Developer/Xcode/DerivedData/App-fzpdcmihaxuphrbsyzxauwqesjby/Build/Products/Debug-iphoneos/FBAEMKit.framework/FBAEMKit) built for iOS Simulator, file '/Users/francescodegiorgio/Library/Developer/Xcode/DerivedData/App-fzpdcmihaxuphrbsyzxauwqesjby/Build/Products/Debug-iphoneos/FBAEMKit.framework/FBAEMKit' for architecture arm64

this is a message I get running the simulator

image

if i revert my plugin to version 3.4.0 it works fine again, If i do the same on my Macbook Pro with M1 cpu, works fine.

I've noticed that FBAEMKit.release.xcconfig has a different configuration in version 4.0.0-1

this is 3.4.0 CONFIGURATION_BUILD_DIR = ${PODS_CONFIGURATION_BUILD_DIR}/FBAEMKit FRAMEWORK_SEARCH_PATHS = $(inherited) "${PODS_ROOT}/FBAEMKit/XCFrameworks" "${PODS_ROOT}/FBAEMKit/XCFrameworks/FBAEMKit.xcframework/ios-arm64_armv7" "${PODS_ROOT}/FBAEMKit/XCFrameworks/FBAEMKit.xcframework/ios-arm64_i386_x86_64-simulator" "${PODS_ROOT}/FBAEMKit/XCFrameworks/FBAEMKit.xcframework/ios-arm64_x86_64-maccatalyst" "${PODS_ROOT}/FBSDKCoreKit_Basics/XCFrameworks" "${PODS_ROOT}/FBSDKCoreKit_Basics/XCFrameworks/FBSDKCoreKit_Basics.xcframework/ios-arm64_armv7" "${PODS_ROOT}/FBSDKCoreKit_Basics/XCFrameworks/FBSDKCoreKit_Basics.xcframework/ios-arm64_i386_x86_64-simulator" "${PODS_ROOT}/FBSDKCoreKit_Basics/XCFrameworks/FBSDKCoreKit_Basics.xcframework/ios-arm64_x86_64-maccatalyst" GCC_PREPROCESSOR_DEFINITIONS = $(inherited) COCOAPODS=1 OTHER_LDFLAGS = $(inherited) -framework "FBSDKCoreKit_Basics" PODS_BUILD_DIR = ${BUILD_DIR} PODS_CONFIGURATION_BUILD_DIR = ${PODS_BUILD_DIR}/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME) PODS_ROOT = ${SRCROOT} PODS_TARGET_SRCROOT = ${PODS_ROOT}/FBAEMKit PRODUCT_BUNDLE_IDENTIFIER = org.cocoapods.${PRODUCT_NAME:rfc1034identifier} SKIP_INSTALL = YES USE_RECURSIVE_SCRIPT_INPUTS_IN_SCRIPT_PHASES = YES

this is 4.0.0-1 CONFIGURATION_BUILD_DIR = ${PODS_CONFIGURATION_BUILD_DIR}/FBAEMKit FRAMEWORK_SEARCH_PATHS = $(inherited) "${PODS_ROOT}/FBAEMKit/XCFrameworks" "${PODS_ROOT}/FBAEMKit/XCFrameworks/FBAEMKit.xcframework/ios-arm64" "${PODS_ROOT}/FBAEMKit/XCFrameworks/FBAEMKit.xcframework/ios-arm64_x86_64-maccatalyst" "${PODS_ROOT}/FBAEMKit/XCFrameworks/FBAEMKit.xcframework/ios-arm64_x86_64-simulator" "${PODS_ROOT}/FBSDKCoreKit_Basics/XCFrameworks" "${PODS_ROOT}/FBSDKCoreKit_Basics/XCFrameworks/FBSDKCoreKit_Basics.xcframework/ios-arm64" "${PODS_ROOT}/FBSDKCoreKit_Basics/XCFrameworks/FBSDKCoreKit_Basics.xcframework/ios-arm64_x86_64-maccatalyst" "${PODS_ROOT}/FBSDKCoreKit_Basics/XCFrameworks/FBSDKCoreKit_Basics.xcframework/ios-arm64_x86_64-simulator" GCC_PREPROCESSOR_DEFINITIONS = $(inherited) COCOAPODS=1 OTHER_LDFLAGS = $(inherited) -framework "FBSDKCoreKit_Basics" PODS_BUILD_DIR = ${BUILD_DIR} PODS_CONFIGURATION_BUILD_DIR = ${PODS_BUILD_DIR}/$(CONFIGURATION)$(EFFECTIVE_PLATFORM_NAME) PODS_ROOT = ${SRCROOT} PODS_TARGET_SRCROOT = ${PODS_ROOT}/FBAEMKit PRODUCT_BUNDLE_IDENTIFIER = org.cocoapods.${PRODUCT_NAME:rfc1034identifier} SKIP_INSTALL = YES USE_RECURSIVE_SCRIPT_INPUTS_IN_SCRIPT_PHASES = YES

thank you

ciccilleju commented 1 year ago

@rdlabo do you have any idea if it's something related to my computer or it is a real bug?

ciccilleju commented 1 year ago

started a blank ionic project, tried version 4.0.0 on ios / intel cpu, nothing to do. It always gives me back the error:

image

and all the other ones

cresjie commented 1 year ago

I experienced the same issue, but I was able to fix it by upgrading to Xcode 14

ciccilleju commented 1 year ago

Can you show me your app configuration? Maybe I have something to set

cresjie commented 1 year ago

@ciccilleju nothing special was set in my config, because before i upgrade my xcode, i deleted my ios folder (just to clear out all my fix attempts for this error). After the upgrade, i ran

are you using either xcode 11 or 12 ? I used xcode 11 before

ciccilleju commented 1 year ago

i'm using

image

you removed the ios folder inside your application?

ciccilleju commented 1 year ago

nothing. I tried to remove the ios folder and started from zero but i still get error messages:

image image
ciccilleju commented 1 year ago

@cresjie can you show me your build settings configuration?

image

i think it's where i must fix something but, rolling back to 3.4.0 suddenly makes the app works flawlessy and ran at first attempt

cresjie commented 1 year ago

@ciccilleju Capture Here are some other infos:

  • node 14.20.1
  • npm 6.14.17
  • ruby 3.0.0
  • gem 3.2.3
  • pod 1.11.3
ciccilleju commented 1 year ago

i have almost the same versions (anyway, i've updated to the latest ones). The only different flag was "build active architecture only" set to "yes", Setting "no" fixed the issue... it's CRAZY

cresjie commented 1 year ago

@ciccilleju i'm glad it helps

ciccilleju commented 1 year ago

@ciccilleju i'm glad it helps

you were great!