You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the project owner split google-services.json files in sub-directories per flavor, like this:
./app/src/flavor1/google-services.json -> contains id for com.example.app.flavor1 only
./app/src/flavor2/google-services.json -> contains id for com.example.app.flavor2 only
Fastlane action find_firebase_app_id called for 'com.example.app.flavor2' will parse only the first one and ends up with this message: google-services.json file doesn't contain configurations for com.example.app.flavor2 application.
The obvious work-around is to make sure the first google-services.json file found in alphabetic order will at least hold the flavor id of the flavor you want to send to Firebase...
The text was updated successfully, but these errors were encountered:
Of course, a better solution would be to parse all files rather than the first one only. And retain the first match for the package name requested.
But I'm sorry to say I'm not going to spend time to PR this kind of solution. :-/
Actually when you have more than one app in firebase you can use one google-service.json file for both apps as Firebase includes all android apps credentials in same file (only for Android).
I don't think that it is worth to support multiple file in this case.
I might have hit a bug/feature with this line:
fastlane-plugin-find_firebase_app_id/lib/fastlane/plugin/find_firebase_app_id/actions/find_firebase_app_id_action.rb
Line 46 in 5732c67
If the project owner split google-services.json files in sub-directories per flavor, like this:
Fastlane action
find_firebase_app_id
called for 'com.example.app.flavor2' will parse only the first one and ends up with this message:google-services.json file doesn't contain configurations for com.example.app.flavor2 application.
The obvious work-around is to make sure the first google-services.json file found in alphabetic order will at least hold the flavor id of the flavor you want to send to Firebase...
The text was updated successfully, but these errors were encountered: