RIM have made the decision, in order to make use of the BBM™ APIs (BBM™ connectivity) in an Application, it have need to be installed via RIMs Infrastructure - to be more precise - it have to be installed via AppWorld™.
Since for the BBM™ connection you need to sign in with your BlackBerryID the System have the connection to the installed AppWorld™ applications.
If you sign into a BBM™-Connected Application with your BlackBerryID and there is no corresponding record in AppWorld™ for this BlackBerryID and ApplicationID then the BBM-Connectivity will run into the TEST mode. The TEST-Mode is limited to 100 users (BlackBerryIDs) and is of course for internal testing purpose only.
Each emacberry.com BBM™-Connected app will show in the About Dialog the BBM™Connection status - it should be always "LIVE".
Also important to know is, that the users running in the TEST-Mode does not see the LIVE-Mode users and vice versa. So in order get the full potential of the BBM™-Connectivity make sure that you are running in LIVE-Mode.
So to make a long story short: In order to use the BBM™ functionality of any application you need to install it via AppWorld™.
The good news is, that you do not need to have the application purchased at AppWorld™ - it's sufficient enough to have it installed/updated via AppWorld™.
So if you have already purchased a RegistrationCode for a emacberry.con Application you can install the free TRIAL (or LITE) version of the Application from AppWorld™ and make use of your existing Code.
Updates/Installation via BlackBerryWorld™ (aka AppWorld™)
basically there are two reasons why updating via BlackBerry World could fail:
- Local data caching (or connection) issues
- Currently the application is not available
In very rare circumstances it could happen that the application is currently not available
in BlackBerry World - this can be the case, if the released emacberry.com application version in
BlackBerry World a serious bug have been found and we have decided that it's better to take the
application temporary out of the shelf.
In this situation BlackBerry World reports all different types of errors - but at the buttom
line it's just that the application is currently not available (for your OS and/or device).
When this happens you can be sure that we work with high pressure on a new release of our
emacberry.com application and hopefully the new build will be approved by BlackBerry in a short
perioid of time [but it could take 7 days (rare cases)].
The best way to stay up to day with us is to follow us in Twitter or like us on Facebook -
since there you can be sure to be notified about the latest issues.
Updates/Installations form emacberry.com (OTA)
In 98% of all cases where users have difficulties to update/install an application OTA directly
from the emacberry.com website the root cause is the build in browser cache (or if it's not the cache
of the device - it's another proxy cache in between).
If you have error messages during the installation (like 'Invalid COD' or the installation reports
and old version) then please be so kind and clear your BlackBerry Browser Cache.
First of all we are sorry that you are running into an issue with oneof your applivcations.
n order to trace down the root cause of the issue it might be required that you wil send us a so
called 'StackTrace' - but please don't be afraid this sounds more complicated then it actually is.
Please simply follow the steps below:
- You need to open the System Event Log.
You can open the System Event log from the main screen of your BlackBerry (the one that is
showing you all the applications). Simply hold the ALT key and type the char sequence LGLG.
An alternative would be to simply install the free FileScoutLite application - there you will
find an Entry called 'Show Sytem Event Log' accessible from the applications options.
- So the System Event Log should now be open - fine.
- If you are an advanced user, you can filter the System Event Log by different types of Events:
The events we are currently looking for a 'Java Exceptions'
By default Java Exceptions are also listed in bold in the System Event Log.
- Now you need to find the exception from the emacberry application - they can be identified by
the fact that they include the String 'emacberry' or 'com_emacberry' in some sort.
- You should be able to mark/select this emacberry Exception line in the System Event Log and
open the BlackBerry Menu. This should give you the option to open the StrackTrace.
- Once the StrackTrace of a single Exception have been opened you can copy the text and paste
it into an email to to support team.
- If there are multipe exceptions (containing 'emacberry') then please repeat the open, copy
and paste procedure.
By following this procedure you would help us tremendously in order to analyse the root cause of
© 2010 emacberry.com