-
Notifications
You must be signed in to change notification settings - Fork 10
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Download of payment reports is (for me) not working any more. #67
Comments
Is this for the daily reports, or the monthly payments in the Payments section? |
@ddaddy I mean the Payments section, which looks like a calendar. (not Sales and Trends) 'provider selection' means the method name |
Ah ok. Mine have been working, although I have 2 accounts and have to enable/disable to do one at a time as the 2FA doesn't work with 2 at a time. I don't know what's happened to @nicolasgomollon I'm tempted to start my own branch of this is the PR doesn't get approved soon. |
Thank you - I also already using my own branch. I have around 10 accounts with 2FA enabled. |
Oh wow. Does it manage to connect to them all? |
No, I'm using AppSales only for my personal account and not for the customers. But Apple is choosing the first provider after the login randomly and AppSales has to change it every time after login. |
I've added that to my PR #65 When I get time I might add either a Payments toggle per account, or a Disable toggle per account to be able to temporarily halt. You should check out my PR, I love the ability to filter and show how many New Subscriptions I get each day. |
Done it :) |
In my special case the provider selection stops working someday near the end of 2023 which leads to problems in downloading payment reports.
After some investigation of the Apple developer website I found that adding the "X-Request-With" header solves this issue.
[authSessionRequest setValue:@"olympus-ui" forHTTPHeaderField:kITCRXRequestedWithKey];
The text was updated successfully, but these errors were encountered: