fastlane: Cannot update languages - could not find an editable version for 'IOS'

Hey fam! I wasn’t able to reproduce this exact case when running in my test projects but I think I have a fix for this in #17235 👇

If somebody is able to test this out and see if it works that would be ❤️

Testing Steps

Update Gemfile and run bundle install, bundle update fastlane, or bundle update

gem "fastlane", :git => "https://github.com/fastlane/fastlane.git", :branch => "joshdholtz-deliver-add-retry-fetching-edit-versions"

I think I will update the description to read as Don’t created or update the app version that is being prepared for submission

That reads much better 😇

I’m having the same issue. I have over 300+ apps to update and fastlane is stopping with this error after a few apps. Very frustrating.

I’m getting the same issue here. I confirmed that the error is intermittent, but it’s causing about 50% of all of my builds to occasionally fail on this step, so it’s really slowing down our build process. Does anyone have a fix for this?

For the record, we’re also experiencing the same behavior on the same version even with an explicit app version being specified. For us, a follow-up attempt resulted in success without the need for manual intervention.

I am having the same issue on 2.156.1

I tried adding the following to the deliver action but both failed:

• app_version: lane_context[SharedValues::LATEST_VERSION]
• app_version: get_version_number(target: target)

Neither of the above worked for me. However, whenever I get this error, a rerun usually fixes the error. This happens on about 30% of our builds.

Having the same issue with 2.156.1.

confirmed. having same issue with v2.152.0

The pull request #17235 that closed this issue was merged and released as part of fastlane 2.160.0 🚀 Please let us know if the functionality works as expected as a reply here. If it does not, please open a new issue. Thanks!

@joshdholtz It’s not clear what skip_app_version_update does. I suspect it’s there to prevent the change of an already set value at the store, should be this?

@ppamorim Thanks for the feedback! It looks like you have skip_app_version_update: true… I think that is the reason its not creating the new version for you 🤔

@joshdholtz Feels like this is not working, take a look:

Fastlane:

Build:

No build 1.3.4 created:

My script to request the review is:

desc "Send to review"
lane :review do

  submit_for_review = UI.confirm("Submit for review?") # Y
  skip_screenshots = UI.confirm("Skip screenshots?") # Y
  automatic_release = UI.confirm("Automatic release?") # Y
  phased_release = UI.confirm("Phased release?") # N

  IDENTIFIER_ARRAY.each_with_index do |identifier, index|

    infoPlistPath = "./MyApp/#{PLIST_ARRAY[index]}.plist"
    scheme = SCHEME_ARRAY[index]

    versionNumber = get_version_number_from_xcodeproj(
      xcodeproj: "./MyApp.xcodeproj",
      target: scheme)

    buildNumber = get_build_number_from_xcodeproj(
      xcodeproj: "./MyApp.xcodeproj",
      target: scheme)

    begin
      schemeNickname = SCHEME_NICKNAME_ARRAY[index]
      deliver(
        username: "XXX@XXXX.XX",
        app_identifier: identifier,
        submit_for_review: submit_for_review,
        force: true,
        automatic_release: automatic_release,
        phased_release: phased_release,
        skip_binary_upload: true,
        skip_app_version_update: true,
        metadata_path: "./fastlane/metadata/#{schemeNickname}",
        screenshots_path: "./fastlane/screenshots/#{schemeNickname}",
        app_version: versionNumber,
        build_number: buildNumber,
        skip_screenshots: skip_screenshots,
        precheck_include_in_app_purchases: false,
        languages: ['en-US', 'en-GB'],
        submission_information: $submission_info)
    rescue => ex
      puts ex
    end
  end
end

On App Store Connect, there is no 1.3.4 version created (as it used in the past), seems like Fastlane is not creating the release anymore.

EDIT:

Found a workaround, seems that Fastlane is not doing this anymore:

I had to create the versions manually and then run the script. Now all the apps are being sent to review. Not nice since I need to do a bit of manual work.

@rogerluan Everything is sync but the data on the App Store Connect API backend needs some time to process (from what I’ve experienced) so that could be what is happening here.

Hello, I’m here starting my workday now! It seems like there could be a race condition. I’ve experience a few things like this before with our latest App Store Connect API migrations. I fixed it in another place but I will add in a retry loop that this morning that hopefully fixes this!

I’ll work on the fix now and get a branch out for you all to try!

@rogerluan Thanks for the ping! ❤️

@joshdholtz I quickly debugged this and my guts tell me this is a race condition between “new app version creation” and “reading the app versions” - either on our end or Apple’s. Hopefully it’s on our end. Do you know if this line executes synchronously or async? https://github.com/rogerluan/fastlane/blame/master/spaceship/lib/spaceship/connect_api/tunes/tunes.rb#L760

A next testing step would be to create a standalone script that simply creates a new app version and then subsequently reads “latest editable app version” to see if they match. If the call above happens sync, then maybe Apple’s API doesn’t refresh the results when a new version is created in a timely manner. Or there’s caching involved - I don’t know enough about fastlane’s architecture to know what it does under the hood to perform those web requests.

This seems to be affecting many people, we’d all appreciate if you could take a deeper dive into this 🙏 count me in to help debugging or testing, I’ll help as much as I can 💪

I faced this error too. Simply retrying worked just fine, with no changes.

Got this error too. Working fine by creating manually the new version on iTunes Connect.