Open kambala-decapitator opened 3 years ago
I hear your pain point and I would argue that once I also thought that I shouldn't need to pass the version explicitly as well, but
I expected that the version will be picked from the latest uploaded build
this might not be the case for everyone (or in all scenarios), and it's a very obscure and implicit way to make project assumptions. I'll give an example:
The company's release train releases a weekly build to TestFlight automatically, and every 2 weeks they release a new build to the public. If the user omits the app version, the latest (most recently uploaded) binary will be used o assume the app version but that might not be always the case.
IMO it's safer to continue to require the user to tell which app version fastlane should create on behalf of the user, OR have the user offer an editable version of the app on App Store Connect first (which's the error message you're getting).
So, my conclusion is: given how the code is structured, it looks like this was a conscious architecture & product decision rather than an oversight/bug. But I could be wrong, maybe @joshdholtz could shed some light here 🙏
@rogerluan yes, it's definitely not for everyone, but for simple cases when you upload only a single version it'd really help IMO.
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.
Bump
Bump
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.
bump
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.
bump
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.
bump
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.
Bump
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.
Bump
lmao it just fully ignored
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.
bump
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.
bump
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.
bump
New Issue Checklist
Issue Description
New app version isn't created on ASC before trying to "update languages" which results in fastlane error.
I've tried with ASC API Key and username, result was the same.
Expected behavior: when
skip_app_version_update == false
, the version should be created if it doesn't exist, and languages should be updated afterwards.After checking https://github.com/fastlane/fastlane/blob/3870627a2e674c8efd9532e5acc0d1d307c6cf8e/deliver/lib/deliver/runner.rb#L52 I discovered that passing
app_version
fixes/workarounds the issue. Still, I expected that the version will be picked from the latest uploaded build since I passnil
.Note: I'm on 2.180, didn't update to 2.180.1 because it doesn't add any value to me (not using Ruby 3.2).
Command executed
bundle exec fastlane asc
Complete output when running fastlane, including the stack trace and command used
Environment