Closed walter-ayala closed 7 months ago
They seem to deployed a fix. But my project is still getting issue.
[10:27:37]: Creating authorization token for App Store Connect API
[10:27:37]: wrong number of arguments (given 2, expected 1)
/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/rubyzip-3.0.0.alpha/lib/zip/file.rb:92:in `open'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/fastlane_core/lib/fastlane_core/ipa_file_analyser.rb:68:in `fetch_info_plist_with_rubyzip'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/fastlane_core/lib/fastlane_core/ipa_file_analyser.rb:41:in `fetch_info_plist_file'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/fastlane_core/lib/fastlane_core/ipa_file_analyser.rb:18:in `fetch_app_version'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/deliver/lib/deliver/detect_values.rb:73:in `find_version'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/deliver/lib/deliver/detect_values.rb:20:in `run!'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/deliver/lib/deliver/runner.rb:25:in `initialize'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/deliver/lib/deliver/commands_generator.rb:82:in `new'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/deliver/lib/deliver/commands_generator.rb:82:in `block (2 levels) in run'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:187:in `call'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:157:in `run'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in `run!'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/deliver/lib/deliver/commands_generator.rb:187:in `run'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/deliver/lib/deliver/commands_generator.rb:18:in `start'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/fastlane/lib/fastlane/cli_tools_distributor.rb:115:in `take_off'\n/Users/vagrant/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/bin/fastlane:23:in `<top (required)>'\n/Users/vagrant/.rbenv/versions/2.7.5/bin/fastlane:23:in `load'\n/Users/vagrant/.rbenv/versions/2.7.5/bin/fastlane:23:in `<main>'
[!] Could not infer your app's version
Deploy failed, error: exit status 1
Not sure if this issue is still on their side or this repo.
@Gambitboy where was the fix deployed? I'm getting the same issue right now also. I didn't see any changes to the Deploy to App Store Connect with Deliver (formerly iTunes Connect)
step.
To fastlane itself. I linked the PR above.
@Gambitboy looking at their release notes now https://github.com/fastlane/fastlane/releases which release were you referring to 🤔 ? I didn't see anything for #21125 yet 😢
Well it was closed because #21187 was merged which fixed the price issue. And I think this step pulls the latest version of fastlane.
This is the issue I'm currently getting.
It can't seem to auto detect my app version.
Could not infer your app's version
Any ideas?
Any help here? I'm still getting this wrong number of arguments given
Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.
To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.
The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".
If no comment left within 21 days, this issue will be closed.
I'm still experiencing the issue.
Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.
To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.
The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".
If no comment left within 21 days, this issue will be closed.
I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.
Troubleshooting
Issue description
I want deploy my React Native app in App Store but the step fails with the message: The request cannot be fulfilled because of the state of another resource. - The resource 'appPrices' cannot be viewed, created or updated. Please view and create 'manualPrices' using the resource 'appPriceSchedules'
And also show a warning/advertisement : Listing apps fails, due to the recent pricing update on App Store?
I don't use fastlane.
The step worked before, but now as App Store changed its price section and when I fill the information in the section with the price in the different countries it started to give this error, probably I have to change something in the step to configure that section of the AppStore.
Bitrise info
The .yml part for this step:
I also talked to bitrise support and they gave me the following solution: https://github.com/fastlane/fastlane/issues/21125#issuecomment-1464684522 but it doesn't apply in my case as I don't use fastlane directly.