Building both ios and android in a single fastlane run results in context clobbering

[machty]

I have a private helper lane that accepts options, does some shared logic, and then calls out to aws_s3 with something that looks like:

  aws_s3(
    #...
    ipa: options[:ipa],
    apk: options[:apk],
    dsym: options[:dsym],
  )

This gets called multiple times in the course of one fastlane execution, but this causes issues if I'm building both ios and android in one execution, because ipa and apk get defaulted to Actions.lane_context[SharedValues::IPA_OUTPUT_PATH] and Actions.lane_context[SharedValues::GRADLE_APK_OUTPUT_PATH] when passed in as nil, and I get an error telling me to pass ipa or apk, not both.

The solution for me was to add these lines of code before calling aws_s3

  # prevent fastlane from using stale values as default values
  Actions.lane_context[SharedValues::GRADLE_APK_OUTPUT_PATH] = nil
  Actions.lane_context[SharedValues::IPA_OUTPUT_PATH] = nil

Not sure what to suggest as a fix, but at the very least it seems if I'm explicitly passing in values as nil (rather than omitting them), they shouldn't be replaced with their default values.

[JesseScott]

I think this is a larger Fastlane issue with lane context...

[revolter]

Are you using separate platform blocks?