I've been able to create and upload one new iOS app and two new Android apps in Fabric however, this particular iOS build will not upload to Fabric. I have gone through all the motions outlined in their tutorials and can run fastlane beta which runs successfully and says
[15:14:12]: Uploading the build to Crashlytics Beta. Time for some ☕️.
[15:14:20]: Build successfully uploaded to Crashlytics Beta 🌷
[15:14:20]: Visit https://fabric.io/_/beta to add release notes and notify testers.
However, this doesn't produce an app in Fabric. When I run through the steps for a Crashlytics upload either using the manual option or using the Mac App, I am unsuccessful. The Fabric app just leaves me with "to continue, build your Xcode project by pressing command-B," which does not do anything, I'm just stuck at that screen. I have tried every answer outlined in the Stack Overflow post here which should have addressed this problem but does not for me.
In short, I have successfully uploaded two Android apps and an iOS app to Fabric using this workflow but cannot get this iOS app to upload regardless of what's indicated by the command line.
If it matters, this is Cordova app.
The answer was tricky and bizarre so I'll post it for future reference. The trick was two steps (as far as I can tell, this is what made it work). First, run:
./Crashlytics.framework/submit *api_key* *build_secret* -ipaPath ./buildname.ipa -emails ***#*** -notifications YES
in the directory which contains your Crashlytics.framework file. This is probably the same folder as your xcodeproj file for your app. You should have this file in that directory after following the steps outlined in my post above.
Then open the xcodeproj and build and run the file (for me I had to run it on an emulator not just the physical iPhone I had connected to my Mac).
This created a new Fabric app. I have not seen any answers like this on Stack Overflow so hopefully this is helps anyone like me. I still have no idea what the root issue really was here.
Related
I am trying to integrate firebase crashlytics into iOS app.
During integration I added run script to upload crashes automatically.
I connected my iPhone_XR to Xcode and ran in release mode. Then I force crashed.I repeated it several times. After few hours of waiting I was able to see the crashes. Confirming that this is working as expected I archived and released this build(DEV) to testflight via xcode.
I did the same force crashed after installing via testflight but this time its not working... Most of the people suggested to upload manually but I am afraid I can't do that as I don't have access to client application(PROD) and also maintaining the crashes report manually is a tidious process to me
Please help me what exactly is happening with Firebase crashlytics. I checked many blogs and github issues for understanding. Most of them are saying to upload manually dSYM files.
Note: GoogleServices file is inside some folder so I gave the path of that in script. I tried to add directly without any sub-folders also but issue still persists.
4-MAR crashes are from my phone which are crashed during testing.
I am supposed to receive some crashes on 5-MAR which are crashed via Testflight but it's saying missing dSYM files
Please help with this issue. I am not unable to find proper solution from past 2 months
Try this script:
${PODS_ROOT}/FirebaseCrashlytics/run
${PODS_ROOT}/FirebaseCrashlytics/upload-symbols -gsp $PROJECT/GoogleService-Info.plist -p ios "${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}"
Also, Firebase recently updated their SDK.
I'm currently making a react native application and need the user_link permission from Facebook. To do so, I have to submit an ios simulator build for app review.
I followed the instructions here https://developers.facebook.com/docs/ios/getting-started/advanced/ but my request got rejected for these two reasons:
Developer Policy 6.1 - Login
Developer Policy 1.9 - Build a Quality Product
Here's what I have done so far:
Ran my .app using ios-sim launch /path/to/.app since I did not do this previously and just directly submitted a ZIP of my DERIVEDDATA folder but
I encounter a "No bundle URL present." error, which I think is because I did not execute npx react-native start before hand (which I would have normally except I didn't becuase I launched the .app directly to the simulator)
I have reached out to Facebook App Review Support and talked to a live agent.
They were very helpful and pointed out that I should also have provided the path where to find my .app in the sea of folders inside the ZIP however, they could not provide a solution to fix the error I have since it's most probably react-native related.
Thank you very much! Any help is greatly appreciated!
The old project of my app used Fabric. (previous to 3.0 version)
I developed a new version (3.0 version and greater) of my app (totally new project) and I tried to implement FirebaseCrashlitycs.
When I look for crashes in Crashlytics dashboard i see an error about dsyms files.
I tried to upload dsyms manually and also including the run script in my project but error still displayed.
How you can see I can see how many crashes attempted but I can't see the details.
The only crash's detail that I can see are about the old project, details migrated from Fabric to Firebase.
Obviously i did something wrong, but i really can't understand what.
The problem is just related to dsyms files?
Installed with testflight the application does appear in the list of target applications to share an image with. When I select my application icon in the list I do get a normal Post dialog. After pressing "Post" in the dialog the application does open but nothing else happens.
When the same version of application is installed with xcode the shared file is delivered and the application displays the shared image.
I am not even sure how to debug such an issue as the application installed by testflight does not appear in the list of installed applications in xcode Devices window. Nothing that I can find in device logs either.
Please suggest any approach to troubleshooting the issue.
Update: I found a way to get much more detailed logs from device than the one provided by xcode's "Devices" window: deviceconsole utility. This gives at least some information to approach troubleshooting.
Update 1: It turns out that the application installed through ad hoc ipa file exported from the same archive that was submitted to testflight shows the same problem. This allows much quicker testing turn around.
This answer indicates that the problem can be caused by "Deployment Target" of extension set above the ios version of test device. I did try different combination of this setting in the application and extension, nothing helped thus far.
Update 2: I created code-level support request with apple for this issue and provided full source of the application to them. After few months of apathetic communications they concluded that the problem is due to a bug and suggested to create report Apple Bug Reporter. I did that and after another few months of more apathetic communications the issue was promptly closed on the basis that the application does not crash. Frustrating, but I still need to resolve the problem, now looks like without help from vendor.
If the deployment target is higher than the version number of the actual phone, your code cannot run. So the only choice is reducing the deployment target of the extension to be the same as the app.
I’d check if you have somehow set different deployment targets for debug and release.
I set you on situation:
I had a project 1.8.10 Objective C App that was without Fabric Crashlytics. So, when I got control of the project they told me that Fabric was already installed. I checked and yes, everything was good. Still, we updated the app to the 1.9.10 (totally different build number) and we set the itunnes connect deployment in 7 days. At first I believed that was something of Apple, but now we are in 100% and there's no data. Actually, I can't see my new app's version (1.9.10) in Fabric's dashboard.
(https://stackoverflow.com/a/41160905/9684719)
Yes: I have checked missing dYSIM, runscript, plist, at Debug information in my project I have DWARF with dSYM File.
Crashlytics not reporting crash in Release mode
Yes: I have my Fabric instantiation in Apps Delegate fine too.
Fabric doesn't update my latest build version
I can see in Itunes Connect that there is people using my app.