Step does not work in bitrise
Closed this issue · 9 comments
The step always fails with bitrise build.
I specify "./AppName/GoogleService-Info.plist" value for the variable Google plist location, but always fails.
You really need to provide more information.
Can you please include any logs from the build process?
Also please include the following:
- the version of Xcode and macOS that you are building against
- the version of the step that you are using
- the version of FirebaseCrashlytics that you are using
- that you can confirm you are using the CocoaPod version of FirebaseCrashlytics
Also have you run the bitrise build process locally to ensure that you have everything setup correctly as that is the best way to debug?
The step checks to make sure that you have entered a file path for the location of your GoogleService-Info.plist, it is a very rudimentary check that makes sure the field is not empty. As if it is not a valid file path for the GoogleService-Info.plist then it will throw an error when it uses Firebase's script.
As you can see here
bitrise-step-firebase-dsym-upload/step.sh
Lines 16 to 20 in 3dcd109
It will only show this error if you haven't filled something in.
As the step is working in my projects and my test projects, I really don't have much more information to give you.
Things to try:
- check the actual YML file to make sure that the variable is set correctly. You can manually edit the YML file to include it. The YML should look like this:
- firebase-dsym-upload@2:
inputs:
- fdu_fabric_location: "./Pods/FirebaseCrashlytics/upload-symbols"
- fdu_google_services_location: "./YOUR-APP-NAME/GoogleService-Info.plist"
- ensure that you have saved your workflow after you have edited it.
- remove the step and re-add it making sure that all of the information is filled in and you have saved the changes in your workflow.
This is what a successful run of the step should look like (I ran this today from one of my test projects)
Both the variable and YML files are correct, and it keeps failing :(
If you have tried all the suggestions that I have made and it is still failing, I really don't have an answer for you.
I am unable to reproduce the error myself.
Closing this as I am unable to reproduce and there has been no further updates.