PhilosChen / appdailysales

Automatically exported from code.google.com/p/appdailysales
0 stars 0 forks source link

getheader("content-disposition") returns None, causes script to exit prematurely #33

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
This all started because I downloaded v2.7 of the appdailysales.py script 
earlier in the week and was able to successfully download sales reports from 
itunes connect using the script. As I developed an automated script to pull 
reports daily via the appdailysales.py script I noticed I was unable to pull 
reports using the script around June 29ish.

What steps will reproduce the problem?
1. Pull reports based on specific day
   ./appdailysales.py -v -D 06/26/2011 
   failed

2. Pull reports for the last few days
   ./appdailysales.py -v -d 6
   failed

3.

What is the expected output? What do you see instead?
Expected output is the gzipped sales report from itunes connect. Instead I 
don't see any new output files and receive the error "1 report(s) not available 
- try again later".

What version of the product are you using? On what operating system?
v2.7, on osX leopard, python v2.6.1

Please provide any additional information below.
I'm able to successfully access the sales reports via the itunes connect 
website with a web browser. Prior to June 29ish I was able to pull sales 
reports from itunes connect with appdailysales.py script v2.7

Note:
I figured out the issue by making the following change to v2.7 of 
appdailysales.py...

diff appdailysales.py_orig appdailysales.py 
420c420,425
<                 filename = 
urlHandle.info().getheader('content-disposition').split('=')[1]

---
>                 result = urlHandle.info().getheader('content-disposition', 
default=None)
>                 if result:
>                     filename = 
urlHandle.info().getheader('content-disposition').split('=')[1]
>                 else:
>                     filename = 'default.txt'
> 

Suggest you add that as a condition to know when Apple changes something again?

Look forward to hearing some news regarding this issue soon. Thanks!!

- Andrew

Original issue reported on code.google.com by bigpo...@gmail.com on 2 Jul 2011 at 5:04