Question

I am facing kind of weird requirements, which in real word I don't seem to exists. But, As a developer I don't ask for the reasons behind them :)

When working In a chat Application. I put BadgeNumber for each new message (expected behavior)

Now, while my tester tested it, they kept on pushing message to the other to the limit it (My App) gets failed. Now, When they failed to do so. They posted a weird bug.

They say for 9999 notification BadgeNumber shows as:

enter image description here

But, when next notification arrives It fails to shows that properly:

enter image description here

Now, What am I supposed to do.

I know that's not going to happen (Consider from Developer point of view). But, How in hell would I resolve this?

Any guidance !!

Was it helpful?

Solution

Since the Application badge you can only show numbers and you are passing a longer number than it can display it will truncate the number.

It will truncate the middle part of the number, this is why it is display .. in the middle since it can't fit the number.

Since this is all handled by iOS there is nothing you can to to change the way it is presented.

If you want you can check the badge number server side and make sure that it not exceed 9999.

OTHER TIPS

resolve the bug as Known Limitation or Third Party you can not do anything in it. put resolution as won't fix

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top