08-04-2009 10:37 PM
uncaught exception articinterface docpos error 3 formatted text equals 46
A user of my app is receving this error message when he tries to run it on his brand new 8330 with 126.96.36.199. In the 8330 simulator running 188.8.131.52, there is no such problem nor on any other simulator. I only use the most vanilla classes in my programs and this error comes as a surprise ot me.
Does this sound like a faulty phone?
Solved! Go to Solution.
08-05-2009 06:20 AM
Perhaps there is faulty device software, not phone.
If it is possible let him update the device software.
If no - use EventLogger to investigate the source line of code and try to find a workaround.
08-05-2009 09:44 PM
Agreed that it could be software. I've asked him to update his software and I will wait to hear if that worked for him or not. Thanks.
08-10-2009 10:22 PM
I'm baffled. I got messages from three 8330 users and one 8130 user that my app produced an error. Two of them mentioned that it was the same error above, and the other two didn't mention the exact error but I assume it is the same. One 8330 user has version 184.108.40.206, which I believe is one of the most recent updates for 4.5. The app runs fine on my Bold, my friend's 8130 and all the trackball and touchscreen simulators I have on my PC.
I have released about six other BB programs with no difficulties like this. The main difference between this program my other programs is that I use FileConnection and can send SMS in this one and I don't use those features in any of my other ones. This program accesses secure APIs (which I have keys for). Otherwise, my programs are very vanilla. Perhaps there is some problem with my program's SMS or file reading and writing processes. Maybe I should have used PersistentStore?
Is there some type of feature that can be toggled on and off in the phone's settings that has to do with file reading/writing or sending SMS that could be producing this error?
09-18-2009 08:15 PM - edited 09-18-2009 09:42 PM
I figured out the solution to the problem.
According to someone at RIM, there is an issue with OS 4.5 and the LabelField class. By using the BasicEditField class to display text rather than LabelField, the exception stopped occuring.
I do not understand why this error occured with my particular program. I have made many programs that implement LabelField and that cause no such error on devices running 4.5.
P.S. the precise error message was "Uncaught exception: ArticInterface:ocPosToCaret: error 3; formatted text length =46"