06-03-2010 08:53 PM - edited 06-03-2010 09:19 PM
Hi, Some of my remote testers are finding it difficult to load my application on their devices. I have been sending them the .alx and .cod files each time so they could use their device manager application to load my application on the phone.
The most frequent error they are reporting is: "Error starting XXXX: Module "XXXX" attempts to access a secure API." This happens when they start the application on their phone.
There are zero secure APIs being used in my application. The Code Signature Tool also tells me that I do not need to sign the application for anything.
All of them have OS 4.6.1 or later on their phones and the application is compiled for 4.6.1.
1. Can a carrier block apps from running on the phone? Such as a carrier signing thing?
2. Are there any other known issues that I should look at?
Solved! Go to Solution.
06-03-2010 09:20 PM
You should ask one of them to send you a device log, it will specifiy where and what is causing the exception.
06-03-2010 09:44 PM - edited 06-03-2010 09:45 PM
What I meant by carrier signing was this: could a carrier block applications from being run on the phone without their permission? I have yet to see such an occurrence myself, but was just wondering if it was possible for them to do that.
I will look into the Device logs to see what's happening and report back. Thanks for the tip!
06-03-2010 10:24 PM
No, from what I remember reading, the only real things a carrier can do is change the language packs and put their splash screen on it. They can also push out links to download certain applications but they don't take any room and can be hidden.
They cannot block apps they don't like unless it is for all phones (Android, BlackBerry, iPhone, WebOS, etc.) in which case it would be a network block, not a application block.
Now as @superdirt brought up, if a business gives you your phone then they can block an app using their policy. This is because network traffic goes through their servers (BES) instead of RIM's.
06-06-2010 05:14 AM
Thanks for the tip about getting the Device Log! That helped me determine that it wasn't my code that was causing the Secure API issue. My tester's desktop manager was screwing stuff up and wasn't installing latest version at all, which didn't require signing.
06-06-2010 09:44 AM
04-11-2013 04:28 AM
Are you a Java developer?
If not, you have come to the wrong forum. I suggest you choose the forum specific to your phone from the list you will see here:
04-11-2013 05:03 AM