Release app version using new AppStoreConnect API fails for phased release ( The URL path is not valid - The resource 'appStoreVersionReleaseRequests' does not exist ) #17283
Comments
|
I literally just used the following and it worked just fine: The only key differences are the older style I don't know why my code would work when yours do not, but hope it helps in debugging yours |
|
I run into this too here is my code and I got this error I can't find appStoreVersionReleaseRequests in official App Store Connect API docs and open API spec(download), I'm not sure whether it is a private API. |
Hi @TragedyStar , |
Hi @mmdock, thanks for your comment. Which version of Fastlane are you using? Also, I wonder if by logging in using the old Tunes way you still get to work with the AppConnect API. According to the fastlane docs you need to log in a different way for it to work: https://docs.fastlane.tools/app-store-connect-api/ Regarding the find-get difference, I've been checking the source and under the hood both are calling the same endpoint, so that should not make a difference. Out of curiosity, your app has a phased release? Or it gets automatically released to all users? |
Yes, me too. Maybe, it is a private API which is captured by fastlane authors using Charles and App Store Connect API team refactor it recently. |
|
I have been looking and this was introduced in: |
|
This is maybe related to this: #17140 |
|
@TragedyStar does your app have a phased release configured? Or you release to 100% of the users? |
Yes, phased release configured and app in pending developer release state |
@valerio-castelli we need help 🥺 |
|
So, I have the same issue after migrating to ASC token. The only endpoint I see in the docs that may work is Modify Phased Release: https://developer.apple.com/documentation/appstoreconnectapi/modify_an_app_store_version_phased_release My guess is creating a phased release and moving it to |
Hi @rabbitinspace , I have attempted that, but it does not work.
So apparently you can not change the state of a phased release when the app is in PENDING_DEVELOPER_RELEASE. I also attempted to create a new phased release object by calling |
|
@dcacenabes thanks for checking it! That's really unfortunate. I hope it's possible to change manual release to automatic one after a review. If so, then there's this API to set an automatic release date (now + 1h). If not, looks like going back to Apple ID auth is the only way :( |
That is actually a good idea. My next release is scheduled in 2 weeks, so I can't test this right away. I'll give it a shot and update this thread. |
Ok so this actually worked. It scheduled the release to happen not earlier than the given date (which is actually a date in the past). After a couple of minutes waiting the phased release started!!! |
dcacenabes
changed the title
|
Having the same issue too. [EDIT] Unfortunately the workaround still fails for me with an error of |
|
@dcacenabes's workaround works for me too, thanks. I wonder if it's worth adopting this as the solution within |
Could you share that code, please? |
|
Might not be the most elegant but assuming you're logged in with your App Store Connect key and have the pending developer version: # Round to the current hour, trimming minutes, seconds
now = Time.now
seconds = now.sec
minutes_in_seconds = (now.min * 60)
release_date = (now - minutes_in_seconds - seconds)
release_date_string = release_date.strftime('%Y-%m-%dT%H:%M:%S%:z')
version.update(attributes: {
earliest_release_date: release_date_string,
release_type: Spaceship::ConnectAPI::AppStoreVersion::ReleaseType::SCHEDULED
})One thing worth noting is that the App Store Connect APIs rejected my request if I tried to send in a I haven't been able to test this more than once though due to our release cycle. There may be edge cases where this might not work? I'll report back if I find any. |
|
Thanks - I'll give that a try :) |
You can make it simpler: Seconds are not necessary. |
|
Nice! 👍 I thought that there might be a more elegant way. I was just using the same format that was provided in the fastlane code when they set |
Makes sense. I just updated my original workaround comment with my latest comment so that all the info is in 1 single comment. |
|
Apple changed the API address, the new one is:
|
|
my bad, that's for version 1.2. Version 1.0 throws the error when you try to log in using ConnectAPI.Auth(key_id...). Logging in using ConnectAPI.login(username,password) then using post_app_store_veresion_release_request works just fine though... but obviously I don't want to leave my username and password in a ruby file... |
|
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 Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with |
|
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 👍 |
|
This is still an issue. The workaround still works. |
|
@max-ott this appears to be an issue after I recently switched to the AppStore Connect API for authentication. do we have any plans to support this with ASC? |
|
It’s probably not supported by Apple at this point. If it is, please check out the official docs from Apple and link it here so we have a reference. |
|
@max-ott no. last time I checked, it's not in the apple api spec. so only the ones in the spec are supported when authenticated via ASC? |
|
Yes when using the API key for authentication, only the official resources / endpoints are allowed. |
|
As discussed here: Seems like the workaround is not working anymore. The app will not get automatically released, it will remain as scheduled. |
|
|
|
@dcacenabes don't feel sorry, tag away! 😊 glad Max helped you out quickly 🙌 |
|
I confirmed that the workaround started working again as of today. We need more people to confirm it but I added "workaround available" label to clarify the current status (more people would try it if they see the label) |
|
Worked for me just now - there was a few minutes of lag however that I don't recall happening previously. |
|
Confirmed also on my end. It working once again! |
|
Confirmed on my end. Great!! |
New Issue Checklist
Issue Description
We are trying to release a new version of the app using the new AppStoreConnect API support introduced recently in Fastlane. When trying to do so, we get the following error:
The URL path is not valid - The resource 'appStoreVersionReleaseRequests' does not existThe app was in a "Pending developer release" state. We had configured a phased release. The app was configured for manual release.
This only happens for phased releases.
We currently have a workaround: #17283 (comment)
Command executed
Complete output when running fastlane, including the stack trace and command used
Environment
The text was updated successfully, but these errors were encountered: