adding always automatically behavior browser click code data development doesn enough existing file issue javascript link matter problem reproduce request send setting support system tested testing thank-you thread type various waiting web working

I am testing e-jnkie with google checkout
everything is ok

when I browse to download the file from my G1 Android phone and click on the link
it starts downloading the file and then says download unsuccessful

if I do it from IE or Firefox on my PC it downloads OK
I think it has something to do with the javascript, because its not a direct link

any ideas???

I have done more research

it seems that could be the mime type

http://groups.google.com/group/android-developers/browse_thread/ thread/c5ccb8764485d5c9/befea559842c2373?lnk=raot


any ideas??

Our development team is looking in to this issue.

Is this only for .apk files?

The web server needs to send the mime type to the browser...
I have tried it with apk files , if you look at the post above, simply adding the mime type to the web server configuration file will solve the issue


Thanks

We have been able to reproduce the problem using the emulator from the Android SDK (nobody in the office actually has an Android device).

We're now working on figuring out the right way for us to fix this; for various reasons it's not as simple as just setting a mime type on the web server (although the mime type *is* the issue).

Please bear with us while we finish developing, implementing, and testing a solution.

great..

thanks for the quick turn around

waiting to hear form you...


there is a similar thread:

http://groups.google.com/group/android-developers/browse_thread/ thread/759bb05d7d18343e

Thanks much

Thanks for your patience. This is done.

Please note, you will need to re-upload your APK file though.

Thanks much

I tested it and its working perfectly..

I see that you changed the web server location.

for future downloads it should always go there??
and can you tell me if adding the mime type solved the issue

Thanks again

orcking
I see that you changed the web server location.

We have several servers, so file be will initially served from one of those, till we push it to amazon S3 (within 15 minutes or so normally) and then the files gets from there. So we have changed our download code to serve APK files with specific mime type and also our push-to-S3 code to add that mime type to the meta data of the object we put in our s3 bucket.

orcking
and can you tell me if adding the mime type solved the issue
Thanks again

Yes. Thank you!! :)

I'm about to upload some files for BlackBerry devices and wondered if this issue has been resolved for these devices too?

According to our developers, the mime-type for BlackBerry install\application files should be:

.jad files: text/vnd.sun.j2me.app-descriptor

.cod files: application/vnd.rim.cod


Many thanks


David

ok - I can report that the mime types are set incorrectly, so the phone doesn't recognise the file as an install file.

Is it possible to fix this ?

This matter would rests in our Development team's hands, so I've brought your inquiry to their attention and can only wait on a response from them.

After sitting on this for entirely too long (we were waiting to roll it out with some other related code, which hasn't happened), we have finally incorporated it into the existing system.

The system will not automatically assign the new MIME types to existing files--we didn't want to trigger a sudden, unexpected change in behavior. To get the system to assign them the new MIME types, you'll need to do one of two things:
1. re-upload the .jad/.cod files in question
2. (if you have enough files for that to be a pain) send us a support request and we'll tickle the system to make the change.

Sorry for the wait!