-
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
Modifying In-App Purchase fails with ITC.response.error.OPERATION_FAILED - spaceship #10743
Comments
Hmmm. @wufire are you familiar with pry? It would be awesome if you could put a breakpoint in the |
Ha, I'll try it out. Haven't used pry before, but no time to learn like the present 👍 |
I wasn't able to get very far, but now every login call is failing on an When I get time, I'll have to figure out this login issue first before I can dive back in to the |
Thank you! |
I was able to put a ruby environment together in a pry-able way. Here's what I see:
|
Interesting. It looks like its a 500. I would like to say that this is an issue on Apple's side of things, but I'm not totally sure. For how long has this been going on? |
Yeah, that 500 is not a great sign... |
Are you able to do this successfully via iTC on the web? |
Yeah, it works through the browser on the same account on the same app. |
Hrmph. Its possible they changed something up on us as far as the API is concerned, if youre familiar with Charles Proxy and want to take a look at the traffic that would be amazing. Otherwise, we will try to handle this in the near future. |
I'm not very familiar with Charles, and I'm not sure how much time I'll have to look, but if this is still open when I get a chance, I'll start digging around. Thanks for your help! |
I get this same response when you don't include both the
I added this ticket to address this issue but never received a response. There should be a way to either bypass the screenshot requirement or access the url to the existing screenshot so you don't need to keep the original screenshots around. |
Looks like a user has created a fix for the issue in this ticket but has not completed a PR for it. |
@kcornbower I tried to do a workaround modify by adding the screenshot (fortunately, I still have the original). I get the same |
@wufire Did you also add the For anyone else experiencing this error, I'm in the process of tracking down the bug and will submit a PR when complete. |
Yeah, I thought the same thing, too. :D Same result, unfortunately. |
That's odd, I'll be done with my PR in the next few days and you can try that and see if it fixes your issue as well. |
blocked on this as well, manually copy/paste over 100 strings is rather painful on the shoulder. |
Just merged @kcornbower's PR, I am going to close this issue for now, let us know if there are still issues! 🚀 |
Hmm, I'm on I'm wondering if mine's is a special case. It's possible the rejection state is causing this problem, but I'm not sure how to go about testing that. Should I file this as a separate issue, or keep this one open? |
@wufire That sounds likely that it has to do with the rejected IAPs. The current code does not work properly unless the IAP is not approved yet. You can still edit approved IAPs and the changes will be uploaded, but it will show an That said I would personally not recommend using Fastlane to edit approved IAPs. There are a lot of parameters that do not match what the real iTunes Connect is currently using, so that code would need to be redone in the future. |
Ah, I see. That makes sense to me. Some changes work! Things like Thanks for the info |
Issue Description
Following the same steps found on this issue: #10216
I still see the OPERATION_FAILED itc response.
Environment
✅ 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: 2017-10-30
The text was updated successfully, but these errors were encountered: