New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove deprecated attributes from apps requests #21187
Conversation
@@ -54,12 +54,12 @@ module EducationDiscountType | |||
"contentRightsDeclaration" => "content_rights_declaration", | |||
|
|||
"appStoreVersions" => "app_store_versions", | |||
# This attribute is already deprecated. It will be removed in a future release. | |||
"prices" => "prices" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea whether we can drop this attribute.
We have to migrate for a latest API
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I see, old applications continue working with old attributes, so it is better to leave it, for backward compatibility.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree, this attribute should be removed as with this PR's changes it will always end up being nil
. Part of the code seeing the nil
might think this app has no price even though it might have prices set up in App Store Connect, ending up with confusion like in #21213.
Not having the attribute would catch possible misuses.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I might have misunderstood part of the code, as it seems app data can come from different locations, some with or without prices. The current state is pretty confusing 😅
Is this a pr that can be approved? Apparently fixes the bug mentioned in PR #21187 |
please guys can you speed up this ? 🙏 |
As discussed on #21125, this patch is not enough to support all changed APIs (e.g. This patch works correctly for a specific use case. However, we need to support the latest API to fix all issues. @joshdholtz How do you think about these issues? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix! ❤️
Checklist
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validci/circleci
builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)Motivation and Context
closes #21125
This PR fixes this issue.
Listing apps fails, due to the recent pricing update on App Store? · Issue #21125 · fastlane/fastlane
Description
Since App Store Connect API 2.3(released on March 2023),
App.prices
has been deprecated.https://developer.apple.com/documentation/appstoreconnectapi/app/relationships/prices
After this version, the following 409 error is returned when requested with including
prices
attributes.However,
prices
are always included as an essential attribute.This PR removes
prices
fromESSENTIAL_INCLUDES
.Testing Steps
Discussion
This PR is just a hotfix. We need to support the new price API to fetch prices.
The current response mock is old. So we have to update this to follow the latest API spec.
fastlane/spaceship/spec/connect_api/fixtures/testflight/apps.json
Line 113 in 0c06ab0