Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Application crash after adding Firebase Performance SDK. #1393

Closed
parth51 opened this issue Jun 11, 2018 · 7 comments

Comments

Projects
None yet
6 participants
@parth51
Copy link

commented Jun 11, 2018

[READ] Step 1: Are you in the right place?

YES

[REQUIRED] Step 2: Describe your environment

  • Xcode version: 9.2
  • Firebase SDK version:5.0.0
  • Firebase Component:
    FacebookCore (0.3.0),
    Firebase (5.0.0),
    FirebaseAnalytics (5.0.0),
    FirebaseCore (5.0.0),
    FirebaseInstanceID (3.0.0),
    FirebasePerformance (2.0.0),
    FirebaseSwizzlingUtilities (2.0.0)

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

The user in iOS 10.3.2 always having a crash while playing with the app after added Performance SDK

Relevant Code:

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
FirebaseApp.configure()
let audioSession = AVAudioSession.sharedInstance()
        do {
            try audioSession.setCategory(AVAudioSessionCategoryPlayback)
        } catch {
            print("Setting category to AVAudioSessionCategoryPlayback failed.")
        }
}

Report on Firebase Crash

Crashed: com.apple.root.default-qos
SIGABRT ABORT 0x0000000182145014
-[FIRInstanceIDAuthKeychain itemsMatchingService:account:accessGroup:error:] + 324
-[FIRInstanceIDAuthKeychain itemForService:account:accessGroup:error:] + 92
-[FIRInstanceIDTokenStore tokenInfoWithAuthorizedEntity:scope:] + 268
-[FIRInstanceIDStore tokenInfoWithAuthorizedEntity:scope:] + 136
-[FIRInstanceIDTokenManager cachedTokenInfoWithAuthorizedEntity:scope:] + 100
-[FIRInstanceID cachedTokenIfAvailable] + 104
-[FIRInstanceID token] + 88
-[FIRInstanceID getIDWithHandler:]_block_invoke.154 + 140

@eshiehz

This comment has been minimized.

Copy link

commented Jun 12, 2018

Thanks for the bug report! We're actively looking into this issue.

@mag10a

This comment has been minimized.

Copy link

commented Jul 11, 2018

@paulb777 - Any update on this issue? We are seeing this in our Cordova project and we are using FirebaseInstanceID 2.0.8.

@paulb777

This comment has been minimized.

Copy link
Member

commented Jul 11, 2018

@mag10a The current FirebaseInstanceID version is 3.1.1. Does that make a difference?

@Gujci

This comment has been minimized.

Copy link

commented Jul 16, 2018

I'm having a very similar issue.
My dependencies are:

binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json"
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAuthBinary.json"
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebasePerformanceBinary.json"
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseMessagingBinary.json"

These are freshly installed with Carthage 0.29.0.
As soon as the FirebaseApp.configure() is called, I get an error:

+[FIRSwizzler currentImplementationForClass:selector:isClassSelector:]: unrecognized selector sent to class 0x10279f6f8

I thought it might be a linking issue. I have only linked FirebaseSwizzlingUtilities.framework, but adding any other related frameworks, like FirebaseISASwizzler.framework results in a compile-time error.

My current solution is to use the 4.9.0 version.

@paulb777

This comment has been minimized.

Copy link
Member

commented Jul 16, 2018

@Gujci Try removing Carthage/Build/iOS/FirebaseSwizzlingUtilities.framework. It is no longer part of Firebase 5.4.0. It was split into FirebaseISASwizzler.framework and FirebaseMethodSwizzler.framework.

@Gujci

This comment has been minimized.

Copy link

commented Jul 16, 2018

@paulb777 thank you

@morganchen12

This comment has been minimized.

Copy link
Collaborator

commented Nov 7, 2018

Closing due to inactivity. If anyone is still experiencing this crash, please comment and I'll reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.