-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[Spaceship] You are not allowed to access the document you requested.
in spaceship after moving to ruby 2.6
#16430
Comments
It seems like you have not included the output of |
I'm now seeing this on ruby 2.3 as well without changing anything, so it feels like this is a problem with App Store Connect. Anyone else with the same issue? |
We started seeing a similar issues a couple of days ago, though it isn't 100% repeatable. |
I +1’d the comment above a few days ago, but thought I’d come back with some more info. We’re seeing this sporadically as well, but as a result of running
This is on an older version of fastlane (2.141), but we’ve been able to reproduce it (again, sporadically) on newer versions as well. |
I have same this problem now. Any one can help me, please?. Thank so much. 🚫 fastlane environment 🚫Stack
System Locale
fastlane files:No Fastfile found No Appfile found fastlane gems
Loaded fastlane plugins:No plugins Loaded Loaded gems
generated on: 2020-05-21 |
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 👍 |
New Issue Checklist
Issue Description
We have some code that uses spaceship to create bundle identifiers and other things with the developer portal. Everything was working fine in macOS Mojave and Ruby 2.3, but when moving to Ruby 2.6 and macOS Catalina, the same code started randomly throwing exceptions when handling some responses from App Store Connect:
Command executed
The exception seems to take place in different calls that communicate with the App Store Connect API, one example is when we create a bundle id or find an existing one:
Any idea what the cause could be?
The text was updated successfully, but these errors were encountered: