Anybody have a working attachment handler?

[skicson]

Sorry for the double post, but my attachment code is dead in the water since this weekend and it's holding me back from a code release. I really need some help.

If you have a working attachment handler, can you *please* share?

My code was working for months but stopped working this weekend. It appears that the contents of the attachment are not getting sent to the device. It still works properly in the outbox if the attachment is sent from the device.

I am using the x-rimdevice prefix (as I have for the last several months) but the size of the attachment, when received on the device is now always 0, however the supportedAttachmentPart.getSize() returns 2K.

Any help would be GREATLY appreciated.

[skicson]

bump. Anybody?

[holy3daps]

Hi!

Couple of questions, first.

Which device OS version(s) are you testing with?

Which development JDE version are you developing with?

Cheers,

karl

[skicson]

my device OS is 4.3.0. Develop with 4.2.1 and 4.3.0. Also see the same problem on 4.2.2 device.

Originally Posted by holy3daps

Hi!

Couple of questions, first.

Which device OS version(s) are you testing with?

Which development JDE version are you developing with?

Cheers,

karl

[holy3daps]

Hi!

Okay, so the first issue is 4.3: I have not yet worked with a version of RIM device OS 4.3.a.b that correctly executes third-party application email attachment handlers. Inserting an email attachment handler object into the OS via Alternate Entry Point execution is successful, however the OS does not execute any of the methods the object implements (supports(), menuString(), run(), etc.). All OS 4.3 versions that I have executed my testbed application on fail to execute the supports() method, which is what tells the OS that the handler can or cannot handle a particular attachment.

I have attached the bare-bones attachment handler testbed. You'll have to recompile and build and sign it. I have executed it successfully on simulators and real devices running 4.1 through 4.2.2. Nothing later than 4.2.2.X seems to work correctly. The attachment contains a folder that contains two files with filename extensions that match what the attachment handler is interested in. I have built the testbed application with JDE 4.1.0, 4.2.1, and 4.3.0 - all succeed on pre-4.3 OSes, and fail on 4.3+.

Good luck, and let me know if you run into any issues.

Cheers,

karl

[skicson]

Hi Karl -

First, thanks very much for the code. I will test it out to see if it produces different results from what I've been seeing. I haven't produced a standalone test like you've been using - I've just been testing the code within the program. (I'll have to start looking at it standalone to see if I can isolate the issue).

In my case, I haven't seen a problem with the 4.3 attachment handler working... the supports() et. al. methods are being called. The problem I see is that the attachment is of zero length with no matter what extension or MIME type I attempt to use. What is particularly frustrating is that it worked fine until a few days ago. This *seems* to be some kind of BIS issue, or something I'm sending/not-sending to BIS.

Anyways, thanks again - this will help me get closer to what the issue is (I hope!)

[holy3daps]

Hi!

The failure of the 4.3 OS to handle email attachments can manifest in a variety of ways. Basically, Research In Motion changed the game - they made some improvements to how the device handles email attachments, and as a result, the code implemented to handle email attachments no longer works for me. The standalone app I put together was to do just as you mentioned, and isolate the issue (twas easier than putting a whole lot of EventLog statements all over production code).

If you don't mind my asking, since you mention that email attachments were working for you until only a few days ago (I haven't seen them working since I first started using 4.3 back in March!), what are the file types (extensions) of the attachments you're working with? I'm wondering if the issue I'm experiencing is related to the fact that the file types I'm using are "special" and not things like ".doc" or ".txt".

Cheers,

karl

[skicson]

My file attachment is of type octet-stream and has an extension of ".gts".

Originally Posted by holy3daps

Hi!

The failure of the 4.3 OS to handle email attachments can manifest in a variety of ways. Basically, Research In Motion changed the game - they made some improvements to how the device handles email attachments, and as a result, the code implemented to handle email attachments no longer works for me. The standalone app I put together was to do just as you mentioned, and isolate the issue (twas easier than putting a whole lot of EventLog statements all over production code).

If you don't mind my asking, since you mention that email attachments were working for you until only a few days ago (I haven't seen them working since I first started using 4.3 back in March!), what are the file types (extensions) of the attachments you're working with? I'm wondering if the issue I'm experiencing is related to the fact that the file types I'm using are "special" and not things like ".doc" or ".txt".

Cheers,

karl

[holy3daps]

Hi!

I went and tried my testbed app for .doc and .txt and they failed equally well. Sorry, man.

Cheers,

karl