CODEWITHSUNDEEP
iosobjective-cxcodecrashlytics
Ofcourse
Ofcourse

Reputation: 647

Crashlytics Framework doesn't detect the Info plist on iOS

I am trying to add Crashlytics framework in my project, however, when I go through the process and reach the point where I add the framework to the project. The "Fabric" script plugin on the Mac doesn't detect that the frame work has been add to the project, and I think because the it doesn't detect the Info.plist in my project as I have changed the name of the Info.plist to something else. I have tried to change it back to Info.plist but still doesn't work. How can I make the framework to detect the info.plist in my project.

Thanks

Upvotes: 10

Views: 12456

Answers (8)

nibajin
nibajin

Reputation: 1

Xcode 10 only:

Add your app's built Info.plist location to the Build Phase's Input Files field:

$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)

at the same time, Move the runscript to the last row.

Upvotes: -1

Akshay Jadhav
Akshay Jadhav

Reputation: 145

Add your app's built Info.plist location to the Build Phase's Input Files field:

$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)

Note: Put exact same lines as given above to resolve this issue I am using Xcode_10.1 and this is working perfectly fine for me and on Fabric official website they specifically mention the same solution as given abovePlease refer this image to see attached screenshots of Xcode to get more details about where to put this line

Upvotes: 0

sherin s
sherin s

Reputation: 61

Move the RunScript in Target -> Build Phase to the last and give it a try:

enter image description here

Upvotes: 6

Bhavik Modi
Bhavik Modi

Reputation: 1565

Set absolute path of Info.plist in "Input Files"

  • Add/Change "Input Files" value in Run Script added for Fabric under "Build Phases"
  • From "$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)" To "new path*/Info.plist"

*new path: You can also get Info.plist path from Build Settings -> Packaging -> Info.plist File

Plist file path

Upvotes: 2

Kousik
Kousik

Reputation: 22425

Xcode 10 only:

Add your app's built Info.plist location to the Build Phase's Input Files field:

$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)

Upvotes: 8

itinance
itinance

Reputation: 12398

The root cause for me was an empty Bundle Identifier (although the key was set in info.plist).

enter image description here

After setting up a new XCode-project as a copy of another one i copied the info.plist with all keys into the new project. But it uses variables like $(PRODUCT_BUNDLE_IDENTIFIER), which was assigned somewhere else (maybe in the project file, that i haven't copied also)

In the screenshot the field with the round oval was empty then as a result. After applying the correct bundle identifier, everything has built fine.

Upvotes: 8

Eric Internicola
Eric Internicola

Reputation: 301

I'm not sure if what I encountered was the same thing, but when trying to archive my project, I received the following error:

❌ error: Fabric: Info.plist Error

I poked through the output in XCode which mentioned it could be a timing issue and to make sure that I made the "Fabric" build phase one of the last build phases. So I updated the XCode configuration and made the Fabric step run just before the "Upload Symbols to Fabric" step, and this cleared up the issue. See the image below.

XCode Build Phases

Upvotes: 25

Jasper
Jasper

Reputation: 7107

Did you add the Fabric NSDictionary entry to your .plist(s)?

enter image description here

Upvotes: 2

Related Questions