Fix for camera permissions problems

Some users have reported a problem when trying to take a photo for upload to TwitPic. This was caused by Yatca not requesting the ‘Recording’ permission, though for some reason this problem wasn’t affecting all devices (including my own). This has been fixed in service release 1.1.2 – link on the right in the usual place. Users must now grant the ‘Recording’ permission to Yatca in addition to the ‘Internet’ permission that has always been required.

Another permissions-related fix in this service release is that when granting a permission to Yatca it is no longer necessary to grant full ‘Allow’ acccess – ‘Prompt’ access will be sufficient. This enables Yatca to be used in environments where BES policy prevents users from granting ‘Allow’ access to third-party applications but does allow ‘Prompt’ access.

This service release doesn’t fix any of the other issues raised (such as the “Error accessing camera: Requested format not supported” that 8900 Curve users are getting when taking a photo), nor does it provide any new functionality or performance improvements. In other words, if the problems described above don’t affect you, there’s absolutely no benefit to be gained from installing this service release!

Like this:

LikeLoading...

Related

This entry was posted on Wednesday, 18th March, 2009 at 12:46 am and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.

@Osman I should perhaps have made it explicit in the 1.1.2 post that the camera fix doesn’t address the “Error accessing camera: Requested format not supported” problem that is affecting 8900 Curve users. I’ve now updated the post to make that clear. The 8900 camera doesn’t seem to support the standard 640×480 resolution that I was depending on as a sort of lowest common denominator. So I’ll have to work something out there.

There must be a way to access the photos that we’ve taken to upload those. Also, I noticed that to get the camera to appear in the Photo box, I’ve had to start,then exit the camera. I’m running .109 on 9530.

Hi, first of all, love this app! However, I have run into a small problem. I’m running OS v4.6.0.247 on a BlackBerry Bold.

I installed yatca v1.1.2 yesterday and it worked great! The integration with TwitPic was smooth and worked perfectly. However, I restarted my phone last night and had some kind of error message pop up. I ignored it and then noticed that there were no yatca twitter messages in my inbox. I hit menu and picked “Yatca Refresh Statuses” and it gave me an error: “Uncaught exception: java.lang.IllegalArgumenException”.

I pressed menu again and noticed that the three options had now doubled to 6 (2 of each). I tried the other two options and each time, I would get that error and they would add another set of three Yatca options in the menu.

I tried another battery pull on the phone with the same results. Does anybody have a similar problem on their phone and is there a fix for it? I don’t want to have to delete and reinstall it everytime I restart my phone. Thanks in advance and again, Great App!

@Francis That’s definitely the strangest problem to be reported to date! It seems that Yatca is failing to handle some error and automatically restarting, resulting in its menu items being repeatedly added. I’ll certainly check that out. Thanks. Oh, just to help me out, can you tell me if you’re using a BES?

@Ryan Another user has reported this problem. It seems to be caused by a proxy server (or firewall, or something else like that) which is returning a HTML document when Yatca attempts to invoke twitter.com. Most likely the HTML document is describing an error of some kind and it’s difficult for me to track this down without being able to see what that error is. I’ll think of something though.

@Yatca No I’m using BIS. I’ve got no other twitter application installed. Only other applications I have installed that integrates messages into my mailbox are Beejive IM and the new Facebook application v1.5.

@Yatca Okay, so I wasn’t sure if it had anything to do with me using the TwitPic camera function. So I deleted my yatca and retarted the phone.

Reinstalled yatca 1.1.2 – it ran fine and dandy. This time I did not use the photo function.

Did a battery pull and when the phone restarted, I got the same “Uncaught exception: java.lan.IllegalStateException” message on startup. Needless to say, yatca isn’t working and I’m still getting those new sets of menu items every time I try to run it.

I guess my point is, that it has nothing to do with whether or not I use the photo function or not. I don’t know if this helps you figure it out.

I’m having a problem with the Yatca application. Everytime I do a battery-pull and the phone starts back up it downloads all the tweet’s since the last time I “Refreshed Yatca Status” even though I have it set to NEVER automatically refresh. Anyway to fix this?

@Brian I realise that’s what ping.fm does – I’m just not sure I want Yatca users to have to create yet another account just so that they can cross post to Twitter and, e.g., Facebook. But everything’s up for discussion at this stage so thanks for the suggestion. In answer to the question I missed, yes, Yatca displays the display name by design instead of the screen name. I might make this configurable at some stage but it wouldn’t exactly be top of my list tbh.

Yatca,
I seem to have an issue. I have it set so I will only receive replies to me, but I seem to get all kinds of tweets in a hidden folder and it shows that I have dozens of “messages”
What do you recommend?
Thanks for your help. Other than this issue, I like this very much. Good work. I’m looking forward to your reply and getting this small challenge behind us. Thanks!
Blake

@blake Having one of the ‘Visibility in Message List’ settings at ‘No’ will not prevent receipt of tweets in that particular category. It simply prevents them from being merged into your main message list. Bear with me though. I’m working on a version that provides much greater control and will actually allow you to completely block receipt of tweets in any one of the five categories. Hoping to have it out later in the weekend.