Chat bubble Items overlaping

[keshavmix]

Hi mate

Text bubbles overlaps on each other all items showing on the same cell.
I just used UIbubbletableview in new project without any other framework. This project is also working fine with iPhone Retina (4-inch) simulator but not with iPhone Retina (4-inch 64bit) simulator..

I am using XCode 5.1 and iOS 7.1. This issue occurs only in 64bit simulator.

Your sample app is working fine in all simulators, but I am using storyboard and unable to figure out where is the problem.

Please help me.

[carlosaguirre]

Hi
I am having the same problem, bubble items overlaps.
Today we updated our ios to 7.1, only the iphone 5S is having this problem.
We tested also with iphone 5 and ipad and mini ipad. All those are showing right.

We had tried with
cell.clipToBounds = YES

we checked on methods that returns section count and height for 0 values but both return >0 results.

we are currently exploring different changes but none had worked.
If we find a solution, Ill post it.

We got a solution!

at UIBubbleTableView on the following method we changed the result type from float to CGFloat

• (CGFloat)tableView:(UITableView *)tableView heightForRowAtIndexPath:(NSIndexPath *)indexPath {
  ...
  }

in respect to clipToBounds, everytime we used it, the cells were not displayed at all, and we tried many combinations with it.
I hope this hard to find and histerically easy and out of mind solution works for you

[keshavmix]

HI mate

This issue is with the 64-bit architecture.
i just changed the Architecture to $(ARCHS_STANDARD_32_BIT) in Build settings.
and it works fine for now.

But for future this issue needs to be fixed with in the code. I Hope they will update the code accordingly.

Regards
Keshav

[eliburke]

The problem is indeed the call to - (float)tableView:(UITableView *)tableView heightForRowAtIndexPath:(NSIndexPath *)indexPath. When compiled for 64-bit, CGFloat is 64 bit, whereas float is only 32-bit. The method signature doesn't match, so heightForRow is never called. Changing it from float to CGFloat is exactly the right solution.

[carlosaguirre]

thanks for the logical explanation, now I know why.

[bouchtaoui-dev]

I ran into the same problem too and the solution carlosaguirre posted worked, at least for me. eliburke gave a clear explanation of the problem. Thank you for the solution :)

[RahulAppIdeas]

Mr. eliburke gave a clear explanation of the problem.Changing it from float to CGFloat is exactly the right solution.Working For me. Thank you for the solution :)