fastlane-plugin-get_new_build_number

fastlane-plugin-get_new_build_number copied to clipboard

https://github.com/rubocop/rubocop-rspec

bartekpacia

bartekpacia

Thanks to this, number of arguments that `get_latest_build_number` takes will be reduced. This: ```ruby build_number = get_new_build_number( bundle_identifier: ENV["APP_BUNDLE_ID"], package_name: ENV["APP_PACKAGE_NAME"], google_play_json_key_path: ENV["GOOGLE_PLAY_JSON_KEY_PATH"], firebase_json_key_path: ENV["FIREBASE_JSON_KEY_PATH"], firebase_app_ios: ENV["FIREBASE_APP_IOS"], firebase_app_android: ENV["FIREBASE_APP_ANDROID"], )...

bartekpacia

bartekpacia

Support for disabling checks on one platform

1

I'd like to support this behaviour: ```ruby get_new_build_number( bundle_identifier: ENV["APP_BUNDLE_ID"] ) ``` But that seems to fail with `Both package_name and google_play_json_key_path are nil`

simplenotezy

Disable temporary caching of build number

4

I find my self having to manually delete the .txt file, if I run multiple builds on my machine while testing. Is this on purpose?

simplenotezy

It seemed the wrong build number was fetched; any idea how this could happen? https://github.com/constantsolutions/flutter_fastlane_tutorial/actions/runs/9404492464/job/25903519422

simplenotezy