Comments (90)
Just use this in Fastfile
. It will give you warning, that the constant is redefined, but you don't need to maintain diffs and patches
Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')
from fastlane.
Ok I'm able to run pilot
successfully after commenting out the "prices" array element. I have the following patchfile (fastlane-prices-fix.patch
) in the root folder of my fastlane-related code (where I install my gems):
--- vendor/bundle/ruby/3.2.0/gems/fastlane-2.211.0/spaceship/lib/spaceship/connect_api/models/app-original.rb 2023-03-10 18:42:18.000000000 -0500
+++ vendor/bundle/ruby/3.2.0/gems/fastlane-2.211.0/spaceship/lib/spaceship/connect_api/models/app.rb 2023-03-10 18:42:39.000000000 -0500
@@ -59,7 +59,7 @@
ESSENTIAL_INCLUDES = [
"appStoreVersions",
- "prices"
+# "prices"
].join(",")
def self.type
And I added the following to my GH Actions workflow:
- name: Patch Fastlane
run: |
patch vendor/bundle/ruby/3.2.0/gems/fastlane-2.211.0/spaceship/lib/spaceship/connect_api/models/app.rb fastlane-prices-fix.patch
Obviously this only works if you use ruby 3.2.0 and fastlane 2.11.0 but the basic idea should work for any version of either.
I created the patch by starting in root of my project (after I copied app.rb
to app-original.rb
and commented out the "prices"
line in app.rb
) and running:
diff -Naur vendor/bundle/ruby/3.2.0/gems/fastlane-2.211.0/spaceship/lib/spaceship/connect_api/models/app-original.rb vendor/bundle/ruby/3.2.0/gems/fastlane-2.211.0/spaceship/lib/spaceship/connect_api/models/app.rb > fastlane-prices-fix.patch
(Again, adjust for ruby/fastlane version).
Nothing I did here is setting the world on fire but it unblocked me and so I wanted to share in case it helps someone else who was planning on using fastlane until this is fixed.
from fastlane.
I fixed this issue on #21187.
It will be released on the next release π
from fastlane.
Just use this in
Fastfile
. It will give you warning, that the constant is redefined, but you don't need to maintain diffs and patchesSpaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')
base on our test this solution works,
require 'spaceship'
Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')
add these 2 lines in the top of Fastline file
# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane
require 'spaceship'
Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')
// THE OTHER CONTENT
from fastlane.
I fixed this issue on #21187.
It will be released on the next release π
Any timescale on when this fix will be released? Unfortunately we can't patch our CI/CD and it is breaking some of our builds.
from fastlane.
Ahhh, not sure how I missed this issue π± Will try to look into later today! So so sorry, everyone π
from fastlane.
Still getting this error in 2.212.2
bundler: failed to load command: fastlane (/Users/xx/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/bin/fastlane)
/Users/xx/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/fastlane-2.212.2/deliver/lib/deliver/upload_price_tier.rb:24:in upload': \e[31m[!] undefined method
first' for nil:NilClass (NoMethodError)
if app_prices.first
^^^^^^\e[0m
from fastlane.
require 'spaceship' Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')
this fixes the issue for me, though I believe Fastlane team should also put an update fix for this as this is breaking the flow.
from fastlane.
I fixed this issue on #21187.
It will be released on the next release π
Hi guys!
When this issue is going to be reviewed and merged? I've been seeing a lot of people still facing the same problem, even me and my teammates.
Specially those who can't use a patched version of fastlane due to some CI's behavior
from fastlane.
Just use this in
Fastfile
. It will give you warning, that the constant is redefined, but you don't need to maintain diffs and patchesSpaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')base on our test this solution works,
require 'spaceship' Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')add these 2 lines in the top of Fastline file
# Uncomment the line if you want fastlane to automatically update itself # update_fastlane require 'spaceship' Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions') // THE OTHER CONTENT
We tried this but are now getting this error:
bundler: failed to load command: fastlane (/usr/local/bin/fastlane)
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/deliver/lib/deliver/upload_price_tier.rb:22:in `upload': [31m[!] undefined method `first' for nil:NilClass[0m (NoMethodError)
from fastlane.
Any updates?
from fastlane.
We're still seeing this in 2.212.2:
upload_price_tier.rb:24:in `upload': \e[31m[!] undefined method `first' for nil:NilClass\e[0m (NoMethodError)
from fastlane.
Not sure if I'm the only one?
I tried multiple monkey patching but always end up with some error
Latest try, based on @giginet https://github.com/giginet/fastlane/pull/1/commits
Results in an API error :
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'
fastlane code runs though, but do not send the right info.
Quite hard to debug as this inside a CI job and i can not really do trials and errors easily. In the end the API connector must be fixed and monkey patching will not be enough.
To add more context, this happens only with apps that have been just created, with the pricing config done manually. We are able to update app that have been untouched since apple change.
from fastlane.
Not sure if anyone pointed it out, but this method also has a problem caused by this same issue (deprecation of App <-> Prices relationship on App Store Connect API).
Specifically, these two lines will produce a nil pointer error because apps do not have the price property anymore.
from fastlane.
Same here. We cannot upload using Fastlane.
from fastlane.
Thanks @joshstrange - that worked for me too. I forked the repo, committed the change, and updated Gemfile
to use my forked repo.
from fastlane.
I'm having this problem when trying to setup Fastlane to a new app. Fastlane init fails with this error.
from fastlane.
ESSENTIAL_INCLUDES = [ "appStoreVersions", - "prices" +# "prices" ].join(",") def self.type
This is awesome, worked as a charm!
But what I found interesting is that it happened two cases with me
The first one I've just created an app in the app store
And without any further configuration made the upload with fastlane
It worked normally, as usual
Notice that in this case I hadn't configured the price yet
In the second app, I've created the app in the app store
But this time I started to configure the store with necessary information, including the prices
Only then I proceed to submit the app with fastlane, and in this case it showed the above error
So it seems that if you set the prices before submiting the app this error occurs, but if you skip the prices fastlane can upload the app without any issues. After that you can set the prices with no problem
from fastlane.
Yep, we ran into the same issue when uploading to the AppStore with Fastlane.
Edit: Also verified we can manually archive and distribute. So doesn't seem to be a code issue or even an Apple issue. But something with the pricing updates has caused an issue with Fastlane specifically.
from fastlane.
Same for me. Azure DevOps
from fastlane.
This item seems like a complete show stopper for any CI/CD process using Fastlane to deploy to Apple.
None of the workarounds suggested up to this point work any more.
from fastlane.
For me using version 2.213.0 fixed the issue.
Make sure you are using that version if you have different ones installed.
I used the following line in the Gemfile:
gem "fastlane", "2.213.0"
from fastlane.
Just ran into this issue as well.
I sort of need my CI to be building my apps (secrets, config steps that run, etc) so I started testing locally and just commenting out "prices" fixes the problem (unsurprisingly):
ESSENTIAL_INCLUDES = [
"appStoreVersions",
# "prices"
].join(",")
Of course if you make use of prices via fastlane it will probably break but I don't. I'm going to look into patching this file on the fly in my CI to comment out that line to see if I can successfully get pilot
to complete.
from fastlane.
@sck-v @joshstrange any idea how can I try that solution on azure devops?
I create all these steps in the pipeline
from fastlane.
Just use this in
Fastfile
. It will give you warning, that the constant is redefined, but you don't need to maintain diffs and patchesSpaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')base on our test this solution works,
require 'spaceship' Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')add these 2 lines in the top of Fastline file
# Uncomment the line if you want fastlane to automatically update itself # update_fastlane require 'spaceship' Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions') // THE OTHER CONTENT
We tried this but are now getting this error:
bundler: failed to load command: fastlane (/usr/local/bin/fastlane) /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/deliver/lib/deliver/upload_price_tier.rb:22:in `upload': [31m[!] undefined method `first' for nil:NilClass[0m (NoMethodError)
fastlane/deliver/lib/deliver/upload_price_tier.rb
Lines 19 to 32 in e55138d
I have a similar issue for a completely new app we're building where prices haven't been set before. I edited the code to return early and seems to have fixed the issue. The correct solution is to update fastlane to handle the new price App Store Connect API updates.
if app_prices.nil? UI.message("App has no prices yet... No changes required." return end
from fastlane.
Same problem for me.
from fastlane.
Any workaround for bitrise or fix being deployed?
We're using https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver step. And it started failing about a week or 2 ago.
from fastlane.
Got around it by commenting out price tier from our
deliver
call and setting it manually in ASC. If you are just releasing a new version of your app it should use the existing pricing.Sorry, just to confirm. You're saying that if the price is set in app store connect, and not in fastlane, it will not overwrite the price and the publish will work?
Because that's good enough for me at the moment.
Seems to work that way for us. Give it a shot and check the listing before submitting for review
from fastlane.
FYI: we experienced this same problem and updated to fastlane 2.212.2 and that fixed the issue without any other changes.
from fastlane.
I am still seeing this issue on the new fastlane update 2.213.0:
from fastlane.
Edit: removing price_tier: 0
from deliver
's parameters fixed the issue.
We are also seeing this error and forcing us not to use Fastlane for app updates. Using version 2.214.0
and attempting to update a free app.
from fastlane.
I just hit this. If you comment out
price_tier: 0
as suggested above, you get past this point, but then at the very end of submission you getappStoreVersions with id 'XXX' is not in valid state. - This resource cannot be reviewed, please check associated errors to see why.
App is missing required pricing. - App is not eligible for submission until pricing has been set.I then manually went into App Store Connect, selected free, all countries, and then everything went through ok.
then what's the use of using fastlane for automation.
Isn't there any other solution for this.
from fastlane.
We are getting the same error today β
from fastlane.
but no changes, still issue
Maybe you would also need to require 'spaceship'
before that line. We have quite complex fastlane setup, so this may be the key as well
from fastlane.
I also had the nil app_prices issue and included that patch in my fork.
The monkey patching didn't work for me. I am not sure why, but I will comment that we are pulling in our own fastlane plugin to iterate on our custom logic and share across our organization. When I attempted the monkey patching, I did it in the main Fastfile and not in the plugin.
from fastlane.
Guys I confirm it's worked fine with me once I added Apple ID (You can find it in app information from Apple Store Connect)
from fastlane.
I am facing the same error with the version 2.211.0
. Any news?
Using a patched fastlane version is not practicable in my case
from fastlane.
Same problem here, using bitrise :c
from fastlane.
For Azure DevOps, with Πzure hosted macOS agent seems to fix that with shell exec step, after installation on fastlane
sudo sed -i ' ' '61d' /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.212.1/spaceship/lib/spaceship/connect_api/models/app.rb
sudo sed -i ' ' '61s/.*/"appStoreVersions"/' /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.212.1/spaceship/lib/spaceship/connect_api/models/app.rb
Πdd PowerShell task to install sudo gem install fastlane -NV
Add Shell Exec Task
with the following code above.If you receive any errors related with Permissions Denied add this line at the first line
sudo chmod 777 /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.212.1/spaceship/lib/spaceship/connect_api/models/app.rb
running fastlane ios test flight track successfully
from fastlane.
Tried to apply the changes from the PR above but getting this error:
bundler: failed to load command: fastlane (/app/ios/vendor/bundle/ruby/2.6.0/bin/fastlane)
NoMethodError: [!] undefined method `first' for nil:NilClass
/app/ios/vendor/bundle/ruby/2.6.0/gems/fastlane-2.212.1/deliver/lib/deliver/upload_price_tier.rb:24:in `upload'
/app/ios/vendor/bundle/ruby/2.6.0/gems/fastlane-2.212.1/deliver/lib/deliver/runner.rb:161:in `upload_metadata'
/app/ios/vendor/bundle/ruby/2.6.0/gems/fastlane-2.212.1/deliver/lib/deliver/runner.rb:61:in `run'
/app/ios/vendor/bundle/ruby/2.6.0/gems/fastlane-2.212.1/fastlane/lib/fastlane/actions/upload_to_app_store.rb:22:in `run'
Not sure if I'm the only one?
from fastlane.
My app was already created but I did do a manual change when apple brought these changes. So I guess it's not so much "just created" but "updated manually" that could be causing the problem, maybe?
from fastlane.
@MiguelSOliveira - I have the same issue. The app where I did a manual change has the same issue.
from fastlane.
We use @joshstrange's script above to patch Fastlane, which we install through a Gemfile
and bundle install --deployment
, to find the right file and patch it. Maybe someone can improve on it, but it works great for us.
#!/bin/sh
FASTLANE_DIR=`find vendor -type d -regex ".*/fastlane-[0-9]*\.[0-9]*\.[0-9]*"`
echo "Patching fastlane in $FASTLANE_DIR"
# https://github.com/fastlane/fastlane/issues/21125#issuecomment-1464684522
cat << EOF > .fastlane-prices-fix.patch
--- $FASTLANE_DIR/spaceship/lib/spaceship/connect_api/models/app-original.rb 2023-03-10 18:42:18.000000000 -0500
+++ $FASTLANE_DIR/spaceship/lib/spaceship/connect_api/models/app.rb 2023-03-10 18:42:39.000000000 -0500
@@ -59,7 +59,7 @@
ESSENTIAL_INCLUDES = [
"appStoreVersions",
- "prices"
+# "prices"
].join(",")
def self.type
EOF
patch -N $FASTLANE_DIR/spaceship/lib/spaceship/connect_api/models/app.rb .fastlane-prices-fix.patch
rm .fastlane-prices-fix.patch
from fastlane.
I'm using a bitrise step that uses fastlane and I'm still getting a crash.
Not sure if its a bug in fastlane or in the bitrise step
[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
from fastlane.
i have just update my fastlane version and it's done
from fastlane.
Hello!
Based on the comments above, I can't get a clear answer as to if this issue has been fixed on a recent fastlane release or not. We don't have explicit pricing set on our products as they are free apps and nowhere in our fastfile is "prices" mentioned. Yet the error remains. I updated our project to version 2.112.2 and we will be pushing a new version out next week after regression. Based on the comments, I don't feel very confident that 2.112.2 will fix the issue. Can someone give me a more solid answer please?
from fastlane.
I'm experiencing this issue on the lastest version of fastlane.
I tried adding Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')
to the fastfile but didn't have any luck.
from fastlane.
I'm also having the same problem. Is there a fix yet? I tried adding the Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')
but still not able to set the price
from fastlane.
I have the same problem since I sent the app for review (not sure if it's related, but it's the 1st time I've sent a new build since).
EDIT: I was on fastlane 2.211.0 but it's working with 2.214.0
from fastlane.
I just hit this. If you comment out price_tier: 0
as suggested above, you get past this point, but then at the very end of submission you get
appStoreVersions with id 'XXX' is not in valid state. - This resource cannot be reviewed, please check associated errors to see why.
App is missing required pricing. - App is not eligible for submission until pricing has been set.
I then manually went into App Store Connect, selected free, all countries, and then everything went through ok.
from fastlane.
It seems like you have not included the output of fastlane env
To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env
π
from fastlane.
Same issue here
from fastlane.
Same here, im using fastlane with my CI environment and i cannot upload versions
from fastlane.
Same error on 2.212.1 too.
@joshstrange's workaround helps out.
from fastlane.
Same here with ruby 3.0.0 and fastlane 2.212.1. @joshstrange's workaround helps out. π
from fastlane.
@sck-v could you provide more details please? i put this into Fastfile, but no changes, still issue
from fastlane.
For me, this was working only from Appfile
from fastlane.
Just use this in
Fastfile
. It will give you warning, that the constant is redefined, but you don't need to maintain diffs and patchesSpaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')base on our test this solution works,
require 'spaceship' Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions')add these 2 lines in the top of Fastline file
# Uncomment the line if you want fastlane to automatically update itself # update_fastlane require 'spaceship' Spaceship::ConnectAPI::App.const_set('ESSENTIAL_INCLUDES', 'appStoreVersions') // THE OTHER CONTENT
We tried this but are now getting this error:
bundler: failed to load command: fastlane (/usr/local/bin/fastlane) /Library/Ruby/Gems/2.6.0/gems/fastlane-2.205.2/deliver/lib/deliver/upload_price_tier.rb:22:in `upload': [31m[!] undefined method `first' for nil:NilClass[0m (NoMethodError)
not sure, maybe the version? we are on 2.211.0, maybe you can try upgrade
# fastlane 2.212.1 is available. You are on 2.211.0.
from fastlane.
I have a similar issue for a completely new app we're building where prices haven't been set before. I edited the code to return early and seems to have fixed the issue. The correct solution is to update fastlane to handle the new price App Store Connect API updates.
I bet monkeypatch may help here as well. Something like this should fix the exception
Spaceship::ConnectAPI::App.class_eval do
def prices
[]
end
end
from fastlane.
Nothing worked for us and we were only seeing the issue on new apps.
HOWEVER we then manually modified the gem package code is the system files for now (as per this) as we only have one build machine. (NASTY WE KNOW!)
Hope to see a fix in the next Fastlane update and then will go from there :)
from fastlane.
The first one I've just created an app in the app store
And without any further configuration made the upload with fastlane
It worked normally, as usual
Notice that in this case I hadn't configured the price yet
Yep, I saw the exact same behavior. My unreleased app (with no price configured) had no issues while my other apps did. Once I set a price it started having the issue.
from fastlane.
Hi,
I was facing the same issue while i was trying to upload apps threw "Azure Devops", some succeeded and some failed with the error above.
i have succeeded to overcome this by doing the following:
- first upload the package to test-flight using the altool (manually or by cicd):
xcrun altool --upload-app -f "{ipaPath}" -t ios --apiKey {Key} --apiIssuer {IssuerId} - then you will see the bundle assigned to the test-flight
- next uploads can be done using the regular cicd job "AppStoreRelease@1" with your properties.
hope it will help somebody...
from fastlane.
In case you are using bundle
, this command will apply the patch without having to specify Ruby and/or Fastlane versions:
echo -e "import sys\nv=open(sys.argv[1]).read()\nv=v.replace(',\\\n \"prices\"\\\n', '\\\n')\nwith open(sys.argv[1], 'w') as f:\n f.write(v)" | python3 - $(bundle show fastlane)/spaceship/lib/spaceship/connect_api/models/app.rb
The command above runs both on Linux and on MacOS. In case you need a Linux-only command that does not use python3
, here it is:
cat <<< $(cat $(bundle show fastlane)/spaceship/lib/spaceship/connect_api/models/app.rb | tr '\n' '\r' | sed -E 's/,\r "prices"\r/\r/' | tr '\r' '\n') > $(bundle show fastlane)/spaceship/lib/spaceship/connect_api/models/app.rb
from fastlane.
I am pleased to report that the ipa file has been successfully uploaded to the app store (TestFlight) via iTMSTransporter, utilizing the 'new' Transporter app. The following PowerShell script was employed:
$iTMSTransporter = "/Applications/Transporter.app/Contents/itms/bin/iTMSTransporter"
$login = "[email protected]";
$pwd = "application-specific-pwd";
$pkg = "./path.to.the.ipa";
$provider = "my team id";
# & $iTMSTransporter -m provider -u $login -p $pwd <- use this command to get your team id
& $iTMSTransporter -m upload -u $login -p $pwd -asc_provider $provider -assetFile $pkg
from fastlane.
Any update here guys? I'm facing same problem on Azure DevOps
from fastlane.
Applying the patch from @joshstrange, problem resolved.
Does anybody know if this has been pushed to the main release?
from fastlane.
@MomenYasser check my comment, it's working.
from fastlane.
I am facing the same issue while uploading to Testflight using Azure DevOps + Fastlane
from fastlane.
In my case, I was able to temporarily solve it by commenting out using sed as follows.
find /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.212.1/spaceship/lib/spaceship/connect_api/models/ -name app.rb | grep connect_api | xargs sed -i -e 's/\"prices/#\"prices/g'
from fastlane.
Tried to apply the changes from the PR above but getting this error:
bundler: failed to load command: fastlane (/app/ios/vendor/bundle/ruby/2.6.0/bin/fastlane) NoMethodError: [!] undefined method `first' for nil:NilClass /app/ios/vendor/bundle/ruby/2.6.0/gems/fastlane-2.212.1/deliver/lib/deliver/upload_price_tier.rb:24:in `upload' /app/ios/vendor/bundle/ruby/2.6.0/gems/fastlane-2.212.1/deliver/lib/deliver/runner.rb:161:in `upload_metadata' /app/ios/vendor/bundle/ruby/2.6.0/gems/fastlane-2.212.1/deliver/lib/deliver/runner.rb:61:in `run' /app/ios/vendor/bundle/ruby/2.6.0/gems/fastlane-2.212.1/fastlane/lib/fastlane/actions/upload_to_app_store.rb:22:in `run'
Not sure if I'm the only one?
Same here
from fastlane.
Is this closed because of the merged PR? Will the other issue be handled in a new issue? How can we track it? @joshdholtz
from fastlane.
Our builds are building OK now, Thanks!
from fastlane.
Just if somebody is about to try the latest release: As the bug is closed and version 2.212.2 was released yesterday, thought it is fixed. Unfortunately deployment still fails with the
appPrices
error.
Retested and it seem to work now
from fastlane.
Also still getting this in 2.212.2.
Got around it by commenting out price tier from our deliver
call and setting it manually in ASC. If you are just releasing a new version of your app it should use the existing pricing.
deliver (
# price_tier: 0,
...
)
from fastlane.
Got around it by commenting out price tier from our
deliver
call and setting it manually in ASC. If you are just releasing a new version of your app it should use the existing pricing.
Sorry, just to confirm. You're saying that if the price is set in app store connect, and not in fastlane, it will not overwrite the price and the publish will work?
Because that's good enough for me at the moment.
from fastlane.
Still getting this error in 2.212.2
/usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/fastlane/lib/fastlane/cli_tools_distributor.rb:126:in `ensure in take_off': uninitialized constant FastlaneCore::UpdateChecker (NameError)
from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/fastlane/lib/fastlane/cli_tools_distributor.rb:126:in `take_off'
from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.212.2/bin/fastlane:23:in `<top from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:25:in `load'
from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:25:in `<main>'
/usr/local/lib/ruby/site_ruby/2.7.0/rubygems/core_ext/kernel_require.
from fastlane.
Hello!
Based on the comments above, I can't get a clear answer as to if this issue has been fixed on a recent fastlane release or not. We don't have explicit pricing set on our products as they are free apps and nowhere in our fastfile is "prices" mentioned. Yet the error remains. I updated our project to version 2.112.2 and we will be pushing a new version out next week after regression. Based on the comments, I don't feel very confident that 2.112.2 will fix the issue. Can someone give me a more solid answer please?
IIRC it did not work for me with 2.212.2. However, removing the app prices from my flow did fix it. I suggest you look again, as you probably are setting the price somewhere in your workflow.
from fastlane.
Thank you for your response. There is no mention of prices in our project including fastfile and related scripts. I'm concerned this issue will require a fastlane release. As I mentioned earlier, we are planning an attempted release with the update and I will reply on this thread with my findings. I really hope I don't have to result in a forked version for a fix as mentioned above.
Best
from fastlane.
@here
i am also facing the below issue
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'.
but i am facing this issue only for one app rest of my app uploaded successfully.
can anyone suggest any solution this will helpful for me?
Thanks! in advance.
from fastlane.
Updating to the latest version has fixed the issue for us
from fastlane.
@sonic555gr
Thanks for your response,
but i faced this issue only with one client's app rest of my app uploaded successfully.
there are same code and same fastlane and xcode version.
fastlane version- 2.211.0
xcode version-14.2
from fastlane.
Latest working fastlane version is 2.212.0 please try it that one.
from fastlane.
i did update fastlane version 2.212.2 instead of 2.211.0 but the issue is still persist.
from fastlane.
it's working after updating fastlane to 2.213.0
from fastlane.
This is till causing issues with version 2.214.0. As our app was free, we just ignored the price updates but please look into a proper fix for this. π
from fastlane.
i am using fastlane version 2.214.0. and my app was free app but we are are still facing the issue. please suggest any proper solution
from fastlane.
im also having this issue for 13 out of 62 apps released with fastlane, they use the exact same fastlane file, app file and deliver file, its the same app project released to 62 different accounts so its very weird that it would work for some of them and not others.
from fastlane.
This issue occurs when we change the Base country or Region in pricing and availability section and select he base price for the app. For example by default base country or region is United States and if we change it to United Kingdom and choose the price as Β£0.00 or any other price, this issue occurs.
from fastlane.
We are still having this issue, and reading the comments it looks like alot of other people are also still facing this, why has it be changed to closed?
from fastlane.
@assembleMHN Make sure you are using a newer version of fastlane
#21125 (comment)
Check your output to make sure you are using that version as well!
from fastlane.
Related Issues (20)
- Apple changed AppStatus 'Ready for Sales' to 'Ready for Distribution' HOT 2
- `match init` assumes a default branch of `master` when using git storage, which is no longer the Github default HOT 1
- upload_to_app_store does not upload release_notes.txt. No error thrown. All other metadata files are uploaded HOT 1
- Unable to upload to app store " Could not find action, lane or variable 'id'" HOT 1
- No ipa or pkg file given while uploading to app store HOT 7
- [spaceship] incomplete support for tvOS platform HOT 2
- Fastlane could not find action or lane 'get_certificates' HOT 1
- The version number has been previously used.
- `fastlane build_app` is trying to access Development provisioning profiles when run for `appstore` only with Github Actions HOT 5
- Fastlane run_tests fails when attempting to get runtimes
- Generated error ENV HOT 2
- Fastlane `2.219.0` was published without changes. HOT 2
- "ar-SA - Invalid request" when uploading metadata to Play Store with a locale it does not support HOT 1
- gym export_options : {method} resolves into empty string HOT 2
- Documentation for iOS screenshots on Xcode is outdated.
- TestFairy Action Fails with NoMethodError for key? Method on String
- Unable to ^C in response to 'Could not find fastlane ... Would you like to set fastlane up?'
- Match CLI Doc wrong? HOT 1
- [Sigh] Creating tvos provisioning profile fails when fetching devices.
- `fastlane build_app` does not apply Flutter Flavor / Xcode Scheme HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fastlane.