11-09-2012 04:01 AM
Following up on this one. I read JSanders post on the new version of Bridge, .32 this time.
So I went to app world on my Torch 9800. There was no icon on the top screen of the phone saying AppWorld had an update available. Therefore I opened AppWorld directly, using the App icon. This time I was first prompted to update my BB ID, before I was able to do anything in the AppWorld app. After that, I updated Bridge from .24 to .32 and it worked instantly and without problems.
When I updated to .24 a couple of weeks ago, I was never first prompted to update the Blackberry ID. The difference is that for the update to .24 the top screen of the smartphone did show the AppWorld icon telling me there is an update for an app. And I used that notification to access app world, where after I was not first prompted to update my BB ID and after the usual reboot, Bridge did not work (as I reported earlier).
This appears inconsistent and confusing for the usage of the update service?
11-09-2012 08:44 AM
It was coincidental that one upgrade required the BlackBerryID update, and the other did not.
The BlackBerryID update was separate from and not related the Bridge update.
11-09-2012 10:18 AM
I'm not entirely satisfied with the answer.
"It was coincidental that one upgrade required the
So it is said that BB Bridge updates may require a
"The BlackBerryID update was separate from and not related the Bridge update."
This could apply very well for the situation of the .32 BB bridge update, but not to the .24 update.
Because, after having updated to .24 of BB Bridge before having done the BBID update, the bridge function consistently refused to work properly and after the BBID update, the BB Bridge .24 worked perfect and consistent.
This observation is therefore not a coincidence, but a consistent pattern in my opinion. The only difference I see, is how I approached the trigger to get to the update of .24 and .32. Perhaps different parameters were passed?
11-09-2012 10:24 AM
Ok, I'm fine with you being "not entirely satisfied" with my response (it wasn't an actual "answer", just a response to your post).
I don't believe the two were connected. I haven't had a BlackBerryID update, and since we're on different device models and OS releases, that could be the reason.