[PsihoKey2]

Yes, there is issue. It is because iOS13 has some new rules about how IM apps work in background. Untill April 2020 ALL apps would have to implement this way of functionality on iOS13. BBMe did it already, and hence it works differently now. Viber , WhatsApp and rest of IM apps have untill April to also play by new iOS13 rules. So, on BBMe at this moment, Senders don't receive Delivery reports unless iOS13 user who received message enters app (click on notification or click on app icon).
On the other hand, iOS13 user has to enter app, and JUST THEN, messages start to arrive and load one by one....
I talked to BBMe chief developer, they will look on how to solve this problem, but it is also iOS13 side problem, so they would maybe have to also try to fix this issue.
I cannot imagine that Viber and WhatsApp will allow their apps to function this way....also iOS I think will not allow IM apps to fuction wrongly... it is in interest of both IM apps like Viber WhatsApp BBMe etc, and also iOS to solve this....
So, someone has to fix this...by April....
There is info from BBMe people that they are looking into this problem...
Here is article about this issue.

https://iphone.appleinsider.com/arti...n-of-voip-apps

[Ben xfg]

Here's hoping for a fix soon! Thanks for the info Psiho.

[conite]

Why was it working ok last week before the latest BBMe update?

Why has BBMe struggled on and off with iOS even prior to the new rules?

Why do other IMs seem to have this working fine?

[Chuck Finley69]

Why was it working ok last week before the latest BBMe update?

Why has BBMe struggled on and off with iOS even prior to the new rules?

Why do other IMs seem to have this working fine?

I’m wondering this also now that you’ve mentioned it.

Since production release publicly available, I’ve been running iOS 13 and I’ve been running iOS 13.3 since released over 30 days ago. I wasn’t having any problems with BBMe until it received update last week.

[app_Developer]

Slack and WhatsApp do not have this problem. I get more than a hundred notifications a day from both. I understand the changes made in 13, but there is something much more fundamental here.

This has been a problem with BBM since the first time i tried it, before iOS13.

[PsihoKey2]

Why was it working ok last week before the latest BBMe update?

Why has BBMe struggled on and off with iOS even prior to the new rules?

Why do other IMs seem to have this working fine?

Conite read my post in detail. All IM apps will have to implement this 'rule' that iOS13.3 requires.
Bbme did it first. Viber whats and rest have time to do it by April.
Pay attention, don't immideately go to negativity

[Dunt Dunt Dunt]

Maybe they tried to comply with the April 2020 requirements... and just muffed it?

I wonder if the iOS version is even viable at this point. Since the change early last year, there have only been 30 reviews and those are hit and miss.

[PsihoKey2]

Slack and WhatsApp do not have this problem. I get more than a hundred notifications a day from both. I understand the changes made in 13, but there is something much more fundamental here.

This has been a problem with BBM since the first time i tried it, before iOS13.

Its because only BBMe so far implemented this rule required by iOS13. Rest app will have to do it by April.

[PsihoKey2]

I’m wondering this also now that you’ve mentioned it.

Since production release publicly available, I’ve been running iOS 13 and I’ve been running iOS 13.3 since released over 30 days ago. I wasn’t having any problems with BBMe until it received update last week.

Make someone send you BBMe message. It will arrive to you, but sender will not receive Delivery report...untill you enter BBMe app or click on notification...
Try it
For sure IM apps or iOS will have to fix this issue

[app_Developer]

Its because only BBMe so far implemented this rule required by iOS13. Rest app will have to do it by April.

First of all this new rule is only wrt to VoIP. All IM apps have always supposed to have worked this way for async messages (IM or text style messages) since like iPhone 4 or something.

It’s not that I’m failing to get VoIP call notifications, I’m failing to get any message notifications.

The way all other messaging apps have always worked (including WhatsApp) is that you send your app an empty hidden notification over the one persistent channel that the OS manages. And then in the handler for the empty message you schedule a block to get the actual content (securely). I really don’t think BBM has ever done this pattern correctly.

[PsihoKey2]

Make someone send you BBMe message. It will arrive to you, but sender will not receive Delivery report...untill you enter BBMe app or click on notification...
Try it
For sure IM apps or iOS will have to fix this issue

Here is good news guys!!!
Next update will solve this!

[Elephant_Canyon]

Its because only BBMe so far implemented this rule required by iOS13. Rest app will have to do it by April.

[citation needed]

[Chuck Finley69]

Maybe they tried to comply with the April 2020 requirements... and just muffed it?

I wonder if the iOS version is even viable at this point. Since the change early last year, there have only been 30 reviews and those are hit and miss.

That’s not so good

[app_Developer]

Maybe they tried to comply with the April 2020 requirements... and just muffed it?

I wonder if the iOS version is even viable at this point. Since the change early last year, there have only been 30 reviews and those are hit and miss.

I think I know what happened now. Short version: I think They depended on the previous 3rd party VoIP mechanism for *all* messages. That was never going to be reliable if used in that way and is a waste of battery. But it’s consistent with the behavior I’ve observed since the app first came out for iOS.

Now that VoIP rules have also changed they are forced to do it the right way for the basic text/pic messaging and they apparently didnt get it right this first time. Hopefully their next version will be correct.

The good news is that when they get it right this pattern is much more reliable and uses much less energy.

[PsihoKey2]

I think I know what happened now. Short version: I think They depended on the previous 3rd party VoIP mechanism for *all* messages. That was never going to be reliable if used in that way and is a waste of battery. But it’s consistent with the behavior I’ve observed since the app first came out for iOS.

Now that VoIP rules have also changed they are forced to do it the right way for the basic text/pic messaging and they apparently didnt get it right this first time. Hopefully their next version will be correct.

The good news is that when they get it right this pattern is much more reliable and uses much less energy.

Good view! Thanks!
Most important is that it will be fixed!

[Dunt Dunt Dunt]

I think I know what happened now. Short version: I think They depended on the previous 3rd party VoIP mechanism for *all* messages. That was never going to be reliable if used in that way and is a waste of battery. But it’s consistent with the behavior I’ve observed since the app first came out for iOS.

Now that VoIP rules have also changed they are forced to do it the right way for the basic text/pic messaging and they apparently didnt get it right this first time. Hopefully their next version will be correct.

The good news is that when they get it right this pattern is much more reliable and uses much less energy.

Yeah I know when I had gotten a few Apple friends to try BBM... it really killed their battery life.

Even now there is a warning and it's locations usage and battery life under the product description....

[app_Developer]

Yeah I know when I had gotten a few Apple friends to try BBM... it really killed their battery life.

Even now there is a warning and it's locations usage and battery life under the product description....

Yeah the good news is this all makes sense now and I could explain the fix to them in 30 min. Hopefully someone there will get it right.

I had a similar conversation with the BB10 team once at a BBJam. Because their solution for 3rd party IM products was also inefficient and not always reliable (like if your app was force closed because the user opened 8 other apps for example)

[Ben xfg]

I talked to BBMe chief developer

If you really do have the main developers contact info, I suggest you try to connect him with @app_Developer so they can learn from each other and code the app properly. This would be a great help to everyone.

I think I know what happened

[Ben xfg]

Its because only BBMe so far implemented this rule required by iOS13. Rest app will have to do it by April.

So pretty much like the SMS/call log restriction by Google that crippled the Hub?

[PsihoKey2]

If you really do have the main developers contact info, I suggest you try to connect him with @app_Developer so they can learn from each other and code the app properly. This would be a great help to everyone.

Thos was response for my problem report via blackberry site for bbme.
Looks like they for sure know problem and will fix it.

[PsihoKey2]

So pretty much like the SMS/call log restriction by Google that crippled the Hub?

No idea Ben

[PsihoKey2]

If you really do have the main developers contact info, I suggest you try to connect him with @app_Developer so they can learn from each other and code the app properly. This would be a great help to everyone.

App_developer can contact me and I will try to connect them, my pin is
EF01DE45

[app_Developer]

App_developer can contact me and I will try to connect them, my pin is
EF01DE45

Invite sent. I used to teach a class on this and I actually taught much of the Good team who are now at BB.

[PsihoKey2]

Invite sent. I used to teach a class on this and I actually taught much of the Good team who are now at BB.

Hmm can you send me again? Or write me your pin, I accepted but nothing happened?

[Dunt Dunt Dunt]

Invite sent. I used to teach a class on this and I actually taught much of the Good team who are now at BB.

Looking at the ratings of the Good/BlackBerry apps.... not sure I'd admit that.

I assume that iOS isn't a priority for BlackBerry or Good - at least in the area of offering additional apps.