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

Fatal Exception: NSInternalInconsistencyException Cannot fetch token invalid checkin state #3018

Closed
deanthibault opened this issue May 16, 2019 · 12 comments
Assignees

Comments

@deanthibault
Copy link

@deanthibault deanthibault commented May 16, 2019

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

  • For issues or feature requests related to the code in this repository
    file a Github issue.
    • If this is a feature request make sure the issue title starts with "FR:".
  • For general technical questions, post a question on StackOverflow
    with the firebase tag.
  • For general Firebase discussion, use the firebase-talk
    google group.
  • For help troubleshooting your application that does not fall under one
    of the above categories, reach out to the personalized
    Firebase support channel.

[REQUIRED] Step 2: Describe your environment

  • Xcode version: 10.2
  • Firebase SDK version: 6.0.0
  • Firebase Component: Core
  • Component version: 6.0.0

[REQUIRED] Step 3: Describe the problem

Getting crash when calling FirebaseApp.configure() in willFinishLaunchingWithOptions

Steps to reproduce:

What happened? How can we make the problem occur?
This is happening when running in iOS simulator.
It occurs after running the app, then deleting app from simulator and running again.
It is intermittently reproducible.

Fatal Exception: NSInternalInconsistencyException
Cannot fetch token invalid checkin state

Fatal Exception: NSInternalInconsistencyException
0 CoreFoundation 0x113e9f1a3 (Missing)
1 libobjc.A.dylib 0x112e0b735 objc_exception_throw
2 CoreFoundation 0x113e9ef42 (Missing)
3 Foundation 0x11158f940 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:]
4 mpdx-ios 0x10f04dd03 -[FIRInstanceIDTokenOperation start] (FIRInstanceIDTokenOperation.m:136)
5 Foundation 0x1115fcc4b __NSOQSchedule_f
6 libdispatch.dylib 0x115a624e1 (Missing)
7 libdispatch.dylib 0x115a6354b (Missing)
8 libdispatch.dylib 0x115a65f70 (Missing)
9 libdispatch.dylib 0x115a655dd (Missing)
10 libdispatch.dylib 0x115a72491 (Missing)
11 libdispatch.dylib 0x115a72cfb (Missing)
12 libsystem_pthread.dylib 0x115e49169 (Missing)
13 libsystem_pthread.dylib 0x115e48be9 (Missing)

Relevant Code:

FirebaseApp.configure()
@paulb777

This comment has been minimized.

Copy link
Member

@paulb777 paulb777 commented May 16, 2019

@chliangGoogle

This comment has been minimized.

Copy link
Contributor

@chliangGoogle chliangGoogle commented May 16, 2019

@deanthibault Thanks for reporting the issue. Can you share with us the debug log?

@deanthibault

This comment has been minimized.

Copy link
Author

@deanthibault deanthibault commented May 16, 2019

Here's the console output
console_output.txt

@chliangGoogle

This comment has been minimized.

Copy link
Contributor

@chliangGoogle chliangGoogle commented May 16, 2019

Can you enable debug mode? -FIRDebugEnabled

In Xcode, select Product > Scheme > Edit scheme...
Select Run from the left menu.
Select the Arguments tab.
In the Arguments Passed On Launch section, add -FIRDebugEnabled

@deanthibault

This comment has been minimized.

Copy link
Author

@deanthibault deanthibault commented May 16, 2019

@realvadim

This comment has been minimized.

Copy link

@realvadim realvadim commented May 17, 2019

Same issue here. Occurs intermittently immediately after launch of a freshly installed app.
Firebase iOS 5.20.2
Xcode 10.1

@chliangGoogle

This comment has been minimized.

Copy link
Contributor

@chliangGoogle chliangGoogle commented May 17, 2019

assertion should only be triggered in debug mode, we should not enable assertion in release build. looks like the release build doesn't include "-DNS_BLOCK_ASSERTIONS=1", we had it in g3 but I guess we need to include it in github version as well.

@paulb777

This comment has been minimized.

Copy link
Member

@paulb777 paulb777 commented May 17, 2019

@chliangGoogle There is no github release build. We release the source. In many cases, we want any developer, whether 1st party or 3rd party, to get the assertion. If that's not the case here, we should change the code.

@paulb777 paulb777 removed their assignment May 17, 2019
@choiks14

This comment has been minimized.

Copy link

@choiks14 choiks14 commented May 25, 2019

same here

@chliangGoogle

This comment has been minimized.

Copy link
Contributor

@chliangGoogle chliangGoogle commented Jun 7, 2019

@deanthibault @choiks14 can you download our newest SDK and see if the issue has been mitigated for you?

@deanthibault

This comment has been minimized.

Copy link
Author

@deanthibault deanthibault commented Jun 11, 2019

This seems to be fixed. I haven't been able to reproduce this issue on v. 6.2.0.

@ryanwilson

This comment has been minimized.

Copy link
Member

@ryanwilson ryanwilson commented Jun 11, 2019

Thanks, closing now. If anyone else has this same issue with 6.2.0, please re-open the issue.

@ryanwilson ryanwilson closed this Jun 11, 2019
@firebase firebase locked and limited conversation to collaborators Oct 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
7 participants
You can’t perform that action at this time.