For some reason I can't setup Crashlytics with freshly created Xcode 10 project. After installing Fabric and Crashlytics pods and creating "Run script" build phase, Fabric Mac app asks to build the project. I've tried building it, cleaning and building again, building it using older version of Xcode (9.4.1), installing Crashlytics manually (without Cocoapods), but still no result - Fabric Mac app still asks to build the project.
Any ideas on how to fix it?
PS: I've also tried adding input file ($(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)), but still no result
I fixed the problem by going into Build Settings, changing Debug Information Format from "DWARF" to "DWARF with dSYM File" and building the project again.
Related
I integrated Firebase Crashlytics in one of my bitcode disabled iOS project. It's working properly if I remove upload dSYM script(see image 2). But if add it then app building process never get complete same thing happens for app archiving also.
I integrated Firebase Crashlytics in some other projects as well and all are working properly and used same configuration and scripts but only this app have issue.
Project Configuration -
Crashlytics version - 4.6.2
My project minimum deployment target - iOS 12
XCode version - 12.5 and Xcode 13
I checked my app bundle identifier it is proper in GoogleService-Info.plist. And path of GoogleService-Info.plist is also correct in script.
I have following scripts -:
Script 1.
Script 2.
Updated Crashlytics version from 4.6.2 to latest version 8.8.0. It solved the issue. But still I could not find any reason why older 4.6.2 is working in other projects but not working in only one project.
I am currently building a react native app using expo.
However, I needed to use cocoapods, which is why I am now using Xcode.
Since I have switched to Xcode, there has been a difference between my local debugging builds (that I run to a USB connected iPhone) vs the builds that get pushed to TestFlight.
After doing some digging I have found that it may be due to the debug vs release schemes in Xcode.
From what I've see it seems that the difference should really just be in performance, file sizes, and some other aspects, but not what the app actually does and displays like in my case.
To test, I made a change on my app's homepage to simply have the text, UPDATED.
As expected, when ran with the debug scheme, the UPDATED text shows up, but when ran with the release scheme, it does not.
How do I get these to sync up and have the release build recognize the changes I make as I am certain I do not want to push a debug build to the app store?
Things I have tried:
Removing/cleaning Build folder and rebuilding
Updating Xcode
Running on another device
Building/running with expo (this did something, but it just causes the app to crash, assuming it is because of the cocoapods)
Versions:
react-native: 0.61.5
Xcode: 11.4.1
macOS: 10.15.3
Thank you
I have fixed the issue.
I found that by running expo publish in the terminal and then building with the release archive scheme in Xcode, it notices the changes.
Now why that is required (maybe it isn't), I am unsure of.
If anyone has an any additional insight, it would be greatly appreciated.
EDIT: So it looks like when I run expo publish it updates the app.bundle and app.manifest. This must be what the release scheme looks at when building.
I am trying to integrate Crashlytics in my project. I have successfully added Crashlytics using Cocoapods
I have added Fabric run and upload symbols script in Build Phases.
Order of Run scripts are UploadSymbols > Fabric run
Also set Debug information format to DWARF with dSYM File
Enable Bitcode is set to YES
Added FirebaseApp.configure() in AppDelegate.swift
and added Crashlytics.sharedInstance().crash() in code to force a crash.
I can see crash logs in Firebase-Crashlytics console when I run in debug mode > stop > launch app again > force crash.
But when I archive and upload to App Center (Enterprise Build), crashes are not showing in Firebase console.
dSYM required error showing. I can see the version in both cases.
Not sure if I am missing anything.
Enterprise build is created using Fastlane.
IDE: Xcode 11.3.1
Thanks in advance.
Building our Flutter project fails on iOS. The following steps work without problems:
running on the XCode simulator (flutter run)
building in the terminal (flutter build ios)
running on a real device in debug mode (flutter run -d "abcd")
If I open the project in XCode, change the build target to "Generic iOS Device" and hit "Build" or "Archive" I get the following error:
/Users/.../development/testproject/ios/Runner/GeneratedPluginRegistrant.m:6:9: 'flutter_exif_rotation/FlutterExifRotationPlugin.h' file not found
After removing the FlutterExifRotationPlugin, the error reoccurs with the next plugin alphabetically, so I figured that plugins in general don't work at the moment.
I tried:
dev, stable and master channels of flutter
reinstalling XCode
reinstalling Flutter
create a new project and moving the old files there
But nothing worked so far.
Ok the solution was very simple. I had to open the .xcworkspace file instead of the .xcodeproject one.
One WEEK went down the pipe for this error. I hope that you, future reader, will find this comment useful.
I'm having problems archiving an iOS Swift application since the last Xcode update (Xcode 7.3), the application builds and runs correctly in debug mode but as soon as I try to archive it I get the following error:
No such module "RealmSwift"
Although it references RealmSwift it fails randomly importing this or any other pod.
The most strange point is that downgrading to Xcode 7.2.1 and Command Line tools 7.2 doesn't fix the problem.
I've clean Cocoapods cache, completely removed ~/Library/Developer folder, removed my Pods folder within the project folder. Even trying to archive with a different machine doesn't work. I rolled back to a version of the app released on Crashlytics and therefore successfully archived in the past with the same result.
Any thoughts about what could be wrong?