Java_ME_platform_SDK_3.0_EA won't load .gif?

Question

I've been developing a midp 2.0 program for a couple of months now, in which I'm using both .png and .gif files.
The other day I switched from SWT 2.5.2 to Java_ME_platform_SDK_3.0_EA, and suddenly a new error occured when I started the program.
java.io.IOException nullIt seems that now I can no longer load gif's using:
Image.createImage(fullName);Where fullname is a resouce in the .jar i.e. /org/netbeans/microedition/resources/dir.gif
There is no doubt that the problem is within SDK3.0, because if I switch to Sony Ericsson, Nokia or SWT 2.5.2 the code runs fine.
Does anyone know the reason for this? I suspect that it is an actual
problem that can occur on some devices, as I've seen something similar
happen when testing on a HTC P3300 smartphone. I've tried the
application on lots of different Nokia + Sony Ericsson phones without
problems.
I've solved the problem by converting all my .gif's to .png's. But now my jar-file has grown 100% :(
I've also tried to create the image "manually"
           try {
            byte[] bytes = loadImageData(is);
            for (int i = 0; i < bytes.length; i++) {
                System.out.print(bytes[i] + ",");
            Image img = Image.createImage(bytes, 0, bytes.length);
        } catch (Exception e) {
            System.out.println(e.getMessage());
            e.printStackTrace();
    public byte[] loadImageData(InputStream in) throws IOException {
        ByteArrayOutputStream bout = new ByteArrayOutputStream();
        int bs;
        byte[] buffer = new byte[512];
        while ((bs = in.read(buffer)) != -1) {
            bout.write(buffer, 0, bs);
        return bout.toByteArray();
    }Which gives me an IllegalArgumentException (imageData is incorrectly formatted or otherwise cannot be decoded)
But the bytestream appears to be my gif image:
71,73,70,56,57,97,16,0,16,0,-9,0,0,0,0,0,-1,-83,25,-1,-20,127,127,0,0,-1,-1,-1,-1,-34,25,-27,49,0,-57,-57,-57,71,71,71,-1,-62,-78,-1,-1,0,-1,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,44,0,0,0,0,16,0,16,0,0,8,123,0,9,8,20,8,-96,96,-63,-127,8,9,2,8,-64,-48,32,-128,-124,4,22,50,44,80,48,-128,65,-124,18,5,8,40,-88,81,-128,-59,-121,4,3,8,64,112,-112,-28,-127,-115,32,23,106,60,24,81,1,-127,-107,15,1,104,-92,8,0,65,-60,-102,5,80,70,20,64,115,-32,-63,2,61,101,22,44,-128,-47,97,-52,-115,3,-110,42,85,-70,82,-31,0,3,80,-93,26,24,-80,-47,39,-61,-89,9,-78,78,109,-24,83,-30,-46,1,92,125,-34,100,72,-106,101,87,-93,102,33,-86,-123,24,16,0,59

Answer 1

Did you check Release Notes of the SDK? I've seen it once - if memory serves it lists quite a lot of known bugs.
Maybe the problem you describe is listed there too... and if you're really lucky then description may even mention some workaround for it.