Firebase Crashlytics setup on iOS?

六眼飞鱼酱① 提交于 2020-11-30 06:24:52

问题


I'm trying to integrate Firebase Crashlytics into iOS my app, which has Firebase Crash Reporting enabled. I've followed the documentation here, but my build always fails when running the custom build phase:

"${PODS_ROOT}/Fabric/run"

The error in Xcode is the following:

error: Fabric: Configuration Issue

Fabric API key not valid. Your Fabric run script build phase should contain your API key: ./Fabric.framework/run INSERT_YOUR_API_KEY INSERT_YOUR_BUILD_SECRET

I do not have a Fabric API key and I suppose that they fabric keys should be taken care by the Firebase library. I have the Info.plist in my project, Firebase is fully functional, but I cannot get past the Fabric run phase. Any help on how to fix this is greatly appreciated!


回答1:


Finally figured it out, posting for anyone that might be baffled by the same problem.

If you've tried to install fabric via the OSX Fabric.app, or you were using Fabric Crashlytics in the past, then it will have added your Fabric API key to your Info.plist, which the Fabric initialization build script is trying to read (I guess).

After deleting the Fabric keys form the Info.plist the script works, without the need of any keys/params.

The Firebase docs should include a snippet warning on this.




回答2:


If you follow closely the Getting Started documentation, you might be in for some frustrations. Trust me. I had my share of that.

Now here's what I can share with you.

  1. If you previously had Fabric RunScript for that Target, then it's best if you delete that and create a new one, apply the GettingStarted instruction, and replace the $(INFOPLIST_PATH) with GoogleService-Info.plist.

  2. There should be no Fabric configuration on your Info.plist file anymore. It's this thing: <key>Fabric</key><dict>...</dict>. If you still have that, time to say goodbye and let go of those feelings or face this issue.

  3. If you keep seeing this in your Xcode console, [Fabric] failed to download settings Error Domain=FABNetworkError Code=-5... blah blah blah, then go clean that Build Folder first (shift + cmd + k).

If your next build works, try force crashing your app and check out the crash logs on Firebase.

Here's my stack: Xcode 10.2.1 | Fabric 1.9 | Crashlytics 3.12




回答3:


The issue for me was I was using the old Fabric before and I had to remove the key from my info.plist




回答4:


I followed the https://fabric.io/kits/ios/crashlytics/install documentation and added the Run Script and updated Info.plist but still got the above issue.

Apparently, I had accidentally added twice 'New Run Script Phase'. After removing the unnecessary 'Run Script's the project compiled successfully.

Xcode 10.1 Fabric 1.7.5 Crashlytics 3.10.4




回答5:


Documentation

  • if crashlytics is already set up in your project (in case of migration),

    1. Remove the fabric key from Info.plist (need to remove the dictionary and the key for Fabric)
    2. Follow the documentation.(just need to use "${PODS_ROOT}/Fabric/run", instead of "${PODS_ROOT}/Fabric/run" key1 key2 in the Run script under build phase)
  • if crashlytics is not setup in your project already(starting a fresh integration with firebase crashlytics), simply follow the documentation.




回答6:


If you're using Crashlytics, you might have to go into your Build Phases -> Crashlytics configuration and add it into the shell/bin/sh section like this: `set -e

if [[ ${PODS_ROOT} ]]; then echo "info: Exec Fabric Run from Pods" "${PODS_ROOT}/Fabric/run" YOUR KEY HERE else echo "info: Exec Fabric Run from framework" "${PROJECT_DIR}/Fabric.framework/run" YOUR KEY HERE fi`



来源:https://stackoverflow.com/questions/47867184/firebase-crashlytics-setup-on-ios

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!