One of the user dunn reported a bug to us:
Hi,
I love your app.
But some bugs found. FC happened when trying attaching picture;.......... Hope these will be fixed in next release.
After all, plurq is an excellent app, the approach is correct. I will follow you.
Thanks
dunn
It's odd since the upload action always succeeded during development stage, and no other similar issues was reported. However, we can't ignore this issue just because it couldn't be reproduced, thus we replied to dunn to obtain more information.
Hi,
..........., my G1 is running cyanogen 4-2-8-1 .
Yes, it happened every time i try to attach picture........ Please help.
Thanks
dunn
So it all comes clear now....during development stage, we used Android SDK 1.5/1.6 as the platform, thus some points may not be taken into consideration to fit an altered environment like CyanogenMod.
However, we still can't catch what's wrong, and need more feedback and help from dunn.
dunn is very active, friendly, and responsive. He not only answered all the questions we asked to gather information, but also helped to capture the screenshot and log (Tell you what, we even used GTalk to chat with dunn, and he is soooo nice~). The information is quite useful, and with it, we finally narrowed down the problem to memory issue.
we found out that on version 4.2.8.1 of CyanogenMod, the memory management is a bit different from std Android SDK. Low memory scenario occurs very easily, and under this scenario, many processes will be killed for sure; unfortunately, PlurQ is always the victim since it's the most recent activity :( After restarting the activity, some login info and API info will be missed, and thus the picture uploading behavior always fails.
Therefore, We made some memory protection on the PlurQ to prevent from this situation. Then we released a test apk to our beloved dunn, and ...hurray!! It works!!
Hi Qiss,
After testings, i think the issue of attaching picture should be fixed.
This is what i've done with your new trail version of plurq
http://www.plurk.com/p/334qm0
Thanks for your hard working.
...............
regards,
dunn
We're soooo glad that we can solve this issue with the cooperation of our supportive user, and also thanks for our hard-working developer Shaka Huang, who poured all his effrots into PlurQ to make it better.
The memory protection mechanism will be integrated to our next release with other new features, please have patience and wait for us.
If you've encoutered the same problem as dunn did, do not hesitate to contact us, and we'll see if we can release some UN-official version to you. And of course, if you have any other problems about PlurQ, just mail us or leave some message, we will reach you soon!!
沒有留言:
張貼留言