<!-- Thanks for helping fastlane! Before you submit your issue, please make sure you followed our checklist and check the appropriate boxes by putting an x in the [ ]: [x] -->

New Issue Checklist

• [2.178.0 currently, but not seeing any changes to screenshot upload] Updated fastlane to the latest version
• [x] I read the Contribution Guidelines
• [x] I read docs.fastlane.tools
• [x] I searched for existing GitHub issues

Issue Description

Hitting rate limit when uploading screenshots

Command executed

bundle exec fastlane deliver run --api_key_path <redacted> --app_identifier <redacted> --overwrite_screenshots true --run_precheck_before_submit false --skip_binary_upload true --app_version <redacted> --phased_release true --force true --submission_information <redacted>

Complete output when running fastlane, including the stack trace and command used

[13:54:30]: Waiting for all the screenshots processed...
#<Thread:0x00007f8c33955800 /<home_path>/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/fastlane-2.178.0/deliver/lib/deliver/app_screenshot_iterator.rb:24 run> terminated with exception (report_on_exception is true):
/<home_path>/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/fastlane-2.178.0/spaceship/lib/spaceship/connect_api/api_client.rb:199:in `handle_response': The request rate limit has been reached. - We’ve received too many API requests for this API key in the past 60 seconds. Please wait and try again. (Spaceship::UnexpectedResponse)
	from /<home_path>/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/fastlane-2.178.0/spaceship/lib/spaceship/connect_api/api_client.rb:113:in `get'
	from /<home_path>/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/fastlane-2.178.0/spaceship/lib/spaceship/connect_api/tunes/tunes.rb:481:in `get_app_screenshot_sets'
	from /<home_path>/.rbenv/versions/2.7.1/lib/ruby/2.7.0/forwardable.rb:235:in `get_app_screenshot_sets'
	from /<home_path>/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/fastlane-2.178.0/spaceship/lib/spaceship/connect_api/models/app_screenshot_set.rb:117:in `all'
	from /<home_path>/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/fastlane-2.178.0/spaceship/lib/spaceship/connect_api/models/app_store_version_localization.rb:88:in `get_app_screenshot_sets'
	from /<home_path>/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/fastlane-2.178.0/deliver/lib/deliver/app_screenshot_iterator.rb:25:in `block (3 levels) in each_app_screenshot_set'

I haven't dug into this yet, it looks like fastlane is making a call in a loop, maybe that can be batched. Also maybe it's hitting the api too often while waiting for the screenshots to be processed.

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem :+1:

<!-- Thanks for helping fastlane! Before you submit your issue, please make sure you followed our checklist and check the appropriate boxes by putting an x in the [ ]: [x] -->

New Issue Checklist

• [x] Updated fastlane to the latest version
• [x] I read the Contribution Guidelines
• [x] I read docs.fastlane.tools
• [x] I searched for existing GitHub issues

Issue Description

Few things I've noticed:

• create_keychain is required for fully hands off automated build.
• create_keychain(unlock: true, name: 'cicd') doesn't actually unlock the keychain created.
• even when unlocked manually by myself clicking around OSX, xcode still can't see the certs described in the profiles.

This is our "codesigning prep" step before our build step to ensure we have all the bits in place (we're also using ruby-config)...

desc "Fetch the codesigning assets for IOS

Match will handle the creation of the filenames, which we control
via the application_id.
"
lane :keystore_get do |options|
  application_id = options[:application_id] || Settings.application.id
  team_id = options[:team_id] || Settings.apple.team_id
  git_branch = options[:git_branch] || Settings.codesigning.branch
  git_url = options[:git_url] || Settings.codesigning.git_url
  output_path = Settings.codesigning.store_path
  keychain_name = Settings.codesigning.keychain_name

  create_keychain(
    name: keychain_name,
    password: '',
    default_keychain: true,
    lock_when_sleeps: false,
    add_to_search_list: true,
    unlock: true,
    timeout: 3600
  )

  match(
    keychain_name: keychain_name,
    keychain_password: '',
    git_url: git_url,
    git_branch: git_branch,
    storage_mode: 'git',
    type: 'appstore',
    team_name: team_id,
    readonly: true,
    output_path: output_path,
    app_identifier: application_id
  )
end

Command executed

I ran the lane. bundle exec fastlane ios keystore_get

Complete output when running fastlane, including the stack trace and command used

<!-- You can use --capture_output as the last command line argument for many commands to get that collected for you. Otherwise, please do it manually. Caution: The output of --capture_output could contain sensitive data such as application ids, certificate ids, or email addresses. Please make sure you double check the output and replace anything sensitive you don't wish to submit in the issue -->

<details> <pre>

--- Step: create_keychain ---

Found keychain '~/Library/Keychains/cicd', creation skipped If creating a new Keychain DB is required please set the require_create option true to cause the action to fail $ security list-keychains -d user "~/Library/Keychains/login.keychain-db" "~/Library/Keychains/cicd-db" Found keychain '~/Library/Keychains/cicd-db' in list-keychains, adding to search list skipped </pre> </details>

Environment

<!-- Please run fastlane env and copy the output below. This will help us help you. If you used the --capture_output option, please remove this block as it is already included there. -->

<details><summary>🚫 fastlane environment 🚫</summary>

Stack

System Locale

fastlane files:

<details><summary>./fastlane/Fastfile</summary>

$VERBOSE = nil

import '../../../tools/fastlane/Fastfile'

</details>

No Appfile found

fastlane gems

Loaded fastlane plugins:

<details><summary><b>Loaded gems</b></summary>

</details>

generated on: 2021-04-13 </details>

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem :+1:

<!-- Thanks for helping fastlane! Before you submit your issue, please make sure you followed our checklist and check the appropriate boxes by putting an x in the [ ]: [x] -->

New Issue Checklist

• [x] Updated fastlane to the latest version
• [x] I read the Contribution Guidelines
• [x] I read docs.fastlane.tools
• [x] I searched for existing GitHub issues

Issue Description

As you can see in the fastfile, I just build an aab file and want to upload it to GG Internal app sharing, but action upload_to_play_store_internal_app_sharing auto fill all apk path and cause the error that the package name mismatch. After I take a look on the source code of upload_to_play_store_internal_app_sharing https://github.com/fastlane/fastlane/blob/master/fastlane/lib/fastlane/actions/upload_to_play_store_internal_app_sharing.rb, it put all apks from fastlane context (attached below)

 # If no APK params were provided, try to fill in the values from lane context, preferring
        # the multiple APKs over the single APK if set.
        if params[:apk_paths].nil? && params[:apk].nil?
          all_apk_paths = Actions.lane_context[SharedValues::GRADLE_ALL_APK_OUTPUT_PATHS] || []
          if all_apk_paths.size > 1
            params[:apk_paths] = all_apk_paths
          else
            params[:apk] = Actions.lane_context[SharedValues::GRADLE_APK_OUTPUT_PATH]
          end
        end

The workaround for me is just delete the android/app/builds folder before release a new build, but it's not a long term solution since I want to store the history of releases.

Command executed

fastlane qa_store

Environment

<details><summary>🚫 fastlane environment 🚫</summary>

Stack

System Locale

fastlane files:

<details><summary>./fastlane/Fastfile</summary>

default_platform(:android)

platform :android do

  desc "Submit a new Internal Build to Google PlayStore"
  lane :qa_store do
    gradle(task: "bundleQaRelease")
    version = get_version_name(
        gradle_file_path:"app/build.gradle",
        ext_constant_name:"versionName"
    )
    build_number = get_version_name(
        gradle_file_path:"app/build.gradle",
        ext_constant_name:"versionCode"
    )
    fileName = "qa-v#{build_number}.aab"
    sh("pwd")
    destination = "../app/build/outputs/bundle/qaRelease/#{fileName}"
    sh("mv", "../app/build/outputs/bundle/qaRelease/app-qa-release.aab", destination)
    path = upload_to_play_store_internal_app_sharing(
        package_name: '*******',
        json_key: 'secret.json',
        aab: "./app/build/outputs/bundle/qaRelease/#{fileName}",
    )
    slack(
      message: "Successfully upload a new build to Google Play Store",
      slack_url: '***,
      payload: {  
        "Version" => "#{version}(#{build_number})",
        "Commit" => "#{last_git_commit()[:abbreviated_commit_hash]}",
        "Url" => path,
      },
      default_payloads: [],
    )
  end

end

</details>

No Appfile found

fastlane gems

Loaded fastlane plugins:

<details><summary><b>Loaded gems</b></summary>

</details>

generated on: 2021-04-15 </details>

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem :+1:

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself :muscle:

This issue will be auto-closed if there is no reply within 1 month.

New Issue Checklist

• [x] Updated fastlane to the latest version
• [x] I read the Contribution Guidelines
• [x] I read docs.fastlane.tools
• [x] I searched for existing GitHub issues

Issue Description

Running upload_symbols_to_crashlytics fails with Shell command exited with exit status instead of 0..

We have four targets, and this command only fails against one of them. I've downloaded the latest GoogleService-Info.plist file and spent a couple of hours searching through the Fastlane GitHub issues and Stack Overflow. Others have experienced this same issue in the past, but none of the possible solutions laid out have resolved my issue.

Command executed

bundle exec fastlane debug_upload_symbols --verbose

Complete output when running fastlane, including the stack trace and command used

<details> <pre> ➜ xxxxx-ios git:(dev) ✗ bundle exec fastlane debug_upload_symbols --verbose [✔] 🚀 DEBUG [2021-04-17 12:04:08.67]: Checking if there are any plugins that should be loaded... INFO [2021-04-17 12:04:09.67]: ----------------------------- INFO [2021-04-17 12:04:09.67]: --- Step: update_fastlane --- INFO [2021-04-17 12:04:09.67]: ----------------------------- INFO [2021-04-17 12:04:09.67]: Looking for updates for fastlane... INFO [2021-04-17 12:04:11.68]: Nothing to update ✅ INFO [2021-04-17 12:04:11.68]: ------------------------------ INFO [2021-04-17 12:04:11.68]: --- Step: default_platform --- INFO [2021-04-17 12:04:11.68]: ------------------------------ INFO [2021-04-17 12:04:11.68]: Driving the lane 'ios debug_upload_symbols' 🚀 INFO [2021-04-17 12:04:12.05]: ------------------------------------------- INFO [2021-04-17 12:04:12.05]: --- Step: upload_symbols_to_crashlytics --- INFO [2021-04-17 12:04:12.05]: ------------------------------------------- INFO [2021-04-17 12:04:12.05]: Uploading '/xxxxx/xxxxx.app.dSYM.zip'... DEBUG [2021-04-17 12:04:12.05]: upload_dsym using command: /xxxxx/Pods/FirebaseCrashlytics/upload-symbols -gsp /xxxxx/GoogleService-Info.plist -p ios /xxxxx/xxxxx.app.dSYM.zip ERROR [2021-04-17 12:07:10.14]: Shell command exited with exit status instead of 0. INFO [2021-04-17 12:07:10.14]: Successfully uploaded dSYM files to Crashlytics 💯 INFO [2021-04-17 12:07:10.14]: Successfully generated documentation at path '/xxxxx/fastlane/README.md'

+------+-------------------------------+-------------+ | fastlane summary | +------+-------------------------------+-------------+ | Step | Action | Time (in s) | +------+-------------------------------+-------------+ | 1 | update_fastlane | 2 | | 2 | default_platform | 0 | | 3 | upload_symbols_to_crashlytics | 178 | +------+-------------------------------+-------------+

INFO [2021-04-17 12:07:10.15]: fastlane.tools finished successfully 🎉 </pre> </details>

Environment

<!-- Please run fastlane env and copy the output below. This will help us help you. If you used the --capture_output option, please remove this block as it is already included there. -->

<details> <pre> <details><summary>✅ fastlane environment ✅</summary>

Stack

System Locale

fastlane files:

<details><summary>./fastlane/Fastfile</summary>

update_fastlane

default_platform :ios

platform :ios do
  lane :debug_upload_symbols do |options|
    upload_symbols_to_crashlytics(
      # api_token: "xxxxx",
      dsym_path: "./xxxxx.app.dSYM.zip",
      # dsym_worker_threads: 2,
      gsp_path: "./xxxxx/GoogleService-Info.plist"
    )
  end
end

</details>

No Appfile found

fastlane gems

Loaded fastlane plugins:

No plugins Loaded

<details><summary><b>Loaded gems</b></summary>

</details>

generated on: 2021-04-17 </details> </pre> </details>

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem :+1:

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself :muscle:

This issue will be auto-closed if there is no reply within 1 month.

One of the most common mistakes surfaced by these errors is providing only the mutation field's value (carData), rather than the field itself ({ addCar: carData }), when providing an optimisticResponse.

@Attimo91 JCenter is actually not that important right now:

https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

UPDATE 4/27/2021: We listened to the community and will keep JCenter as a read-only repository indefinitely. Our customers and the community can continue to rely on JCenter as a reliable mirror for Java packages.

...slowly exhale on that one. It should be removed, but zero need for cherry-picking anywhere I think.

Description

i want to build a simulator build for sending to facebook review, but whatever i did , did not do the trick , how should i build a simulator build which will work ?

React Native version:

OS: macOS 11.4 CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz Memory: 707.47 MB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 16.3.0 - /usr/local/bin/node Yarn: 1.22.10 - /usr/local/bin/yarn npm: 7.15.1 - /usr/local/bin/npm Watchman: 2021.06.07.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4 Android SDK: API Levels: 23, 25, 26, 27, 28, 29, 30 Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.2, 31.0.0 System Images: android-27 | Google APIs Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom Android NDK: 23.0.7272597-beta3 IDEs: Android Studio: 4.1 AI-201.8743.12.41.6953283 Xcode: 12.5/12E262 - /usr/bin/xcodebuild Languages: Java: 1.8.0_291 - /usr/bin/javac npmPackages:

Steps To Reproduce

Provide a detailed list of steps that reproduce the issue.

1. go to schema and edit it to release then build
2. go to the build folder and try run it through ios-sim launch /path/to/app.app

Expected Results

run smoothly on emulator

Description:

i tried to convert the plist to binary and still i got the same problem and app stopped on launch and got the same error:

An error was encountered processing the command (domain=FBSOpenApplicationServiceErrorDomain, code=1):
The request to open "app.app.co" failed.
The request was denied by service delegate (SBMainWorkspace) for reason: Unspecified ("null").
Underlying error (domain=FBSOpenApplicationErrorDomain, code=1):
	The operation couldn’t be completed. (null)
	(null)
app.app.co: -1
/usr/local/Cellar/ios-sim/9.0.0/libexec/lib/node_modules/ios-sim/node_modules/bplist-parser/bplistParser.js:55
    throw new Error("Invalid binary plist. Expected 'bplist' at offset 0.");
          ^

Error: Invalid binary plist. Expected 'bplist' at offset 0.
    at exports.parseBuffer (/usr/local/Cellar/ios-sim/9.0.0/libexec/lib/node_modules/ios-sim/node_modules/bplist-parser/bplistParser.js:55:11)
    at tryParseBuffer (/usr/local/Cellar/ios-sim/9.0.0/libexec/lib/node_modules/ios-sim/node_modules/bplist-parser/bplistParser.js:28:18)
    at /usr/local/Cellar/ios-sim/9.0.0/libexec/lib/node_modules/ios-sim/node_modules/bplist-parser/bplistParser.js:46:7

Few issues I saw when profiling RNTester:

• Repeatedly calling -lowercaseString during weightOfFont causes a TON of extra memory traffic, for no reason.
• NSCache is thread-safe, so no need for a mutex.
• Using stringWithFormat: for the cache key is slow. Use NSValue to store the data directly instead.

From scrolling around on the TextView tester, before the change:

Thank you for your review! It will allow and it will not crash, please see this https://github.com/fastlane/fastlane/blob/master/fastlane/lib/fastlane/actions/create_keychain.rb#L50

• timeout: "5000" & timeout: 5000 both are equalivent and valid without any crash!
• timeout: false then it will ignore -t param

Fixes #8331 and #6915 by relaxing an overzealous exception to be merely an invariant.error message, which should also help with the underlying cause of https://github.com/apollographql/apollo-client/issues/7436#issuecomment-860631219.

Although this change is likely to trigger a number of new missing field error messages for existing applications, these errors are almost always worth investigating, because they can hide gaps in the incoming data that manifest themselves as missing fields later, when the original cause of the error is much less obvious.

Because this error was an exception before, we had to be very careful about when we threw it, since it would abort the entire write. Unfortunately, this carefulness led to some dodgy decisions about when to hide exceptions that really should have been surfaced (see #8331 for one example, where merely using possibleTypes would enable the exception). Now that we're just logging an error message using invariant.log, those messages can be a little noisier without disrupting the overall work of the client/cache.

I hope developers find these error messages useful, though of course we can continue to refine the preconditions/frequency of the messages, and/or ways to capture/redirect errors for certain writes, where the errors are (hypothetically) known to be harmless, or need to be programmatically processed in some way.

I’m taking a look. The test suite is finicky. Thanks for the help!

Would it allow String values that are converted into int values or it will crash unexpectedly?

has anyone resolved this ??

I am getting this issue also

@penn5 This signing was added for the release process of the library to maven central. This doesn't effect anything with the users using this library, right? This will only get used when I'm building/releasing a new version of the lib? 😇

It happens. There are 2 ways of dealing with it for now:

• you could temporarily use an older version of Fastlane before a fix is released
• use a workaround described in comments of https://github.com/fastlane/fastlane/issues/18892 (It has a linked PR that is pending review with a fix for create_keychain)

And please remember it's an open source project, people are improving the tool in their free time.

Please reopen this issue

I've opened PRs to add this information in getting-started docs: https://github.com/fastlane/docs/pull/1066 and create_app_online action docs: https://github.com/fastlane/fastlane/pull/18934

I'm still facing the same problem( I'm using a custom font ). the issue happening when the text input has font size style when I removed the font size the scroll disappeared so I think the problem is related to the text input height which affected by the font size. I hope you can fix this issue soon.

@crazymanish thanks for taking the time to walk me through that!

Intended outcome: Component should be re-rendered when cache changes.

Actual outcome: Component is not re-rendered when cache changes.

How to reproduce the issue:

1. has custom key for some entities (in my case it is "name" for ProductItem type) [not sure this is needed]
2. use useQuery with fetchPolicy: 'cache-first'
3. get some item updated with mutation (in my case updated ProductItem is returned) [not sure this is needed]
4. additionally call query that returns udpated entities (in my case getUserProducts that returns [ProductItem!]!)
5. component that uses useQuery is not re-rendered until you set 'cache-and-network'

Versions System: OS: macOS 11.4 Binaries: Node: 14.17.0 - /usr/local/bin/node Yarn: 1.19.1 - ~/.yarn/bin/yarn npm: 6.14.13 - /usr/local/bin/npm Browsers: Chrome: 91.0.4472.114 Firefox: 72.0.2 Safari: 14.1.1 npmPackages: @apollo/client: ^3.3.6 => 3.3.20 apollo-upload-client: ^14.1.3 => 14.1.3 apollo3-cache-persist: ^0.9.1 => 0.9.1 npmGlobalPackages: apollo: 2.33.4