14.4 Bug Update

Problem with TEXTJOIN and “do not include empty cells”. FIXED!!!

TEXTJOIN would include cells that were null strings. You might end up with extraneous commas in the result. This made us jump through extra hoops to remove those extra commas. It now ignores null strings the same as actual empty cells.

The bug was present in 13.1 but is fixed now.

Wrapped text in a popup may cause tables to overlap. FIXED

If a table has another table below it and a cell increases in height in the upper table, the lower table is supposed to move down accordingly to accommodate the increased height.  This worked fine except if that wrapped cell was a pop up cell.  The cell height would increase but the table below would not move down and might end up getting overlapped.  

----

Sorry to say that that is the extent of the bug fixes for bugs I have reported. Now onto the ones that did not get fixed.

Bug related to cell borders not displaying or printing correctly.  Bug remains in version 14.4.

Cell borders that are the same color as the cell fill will be visible if they are less than 1pt width. They appear to be a lighter shade. If set to 1pt or greater the problem goes away.

Tables with no cell borders print with faint borders. It looks correct in Numbers but not when printed.

Bug was first reported in version 11.2 in October 2021. Still remains in version 14.4 in April 2025.  Three and a half years and counting….

Calculation Engine Bug. Bug remains in version 14.4

Changes Apple made to the calculation engine deviated from the IEEE 754 standard and have rendered Numbers useless for recursive formulas that require high precision. 

Numbers used to follow the IEEE 754 standard religiously. This caused some “user expectation” problems when numbers did not add and subtract exactly like they do on paper, sometimes resulting in a very small error instead of being exactly zero. Apple apparently decided to massage the results to “fix” this.  But in doing so they created other small errors, or at least inconsistencies with other math apps such as Excel and Matlab.

Bug was first reported in version 12.0 in March 2022. I believe it was around many versions earlier but I do not recall what version had the change to the engine and did not find it then. Still remains in version 14.4 in April 2025. Far more than 3 years and counting…

Reference Errors When Sorting. Bug remains in version 14.4

This is a very glaring bug and it really irks me that is is still not fixed. Formulas such as SUM and COUNTIF when used with a range of the form $A2::A2 will develop reference errors if the table is sorted.  Example is COUNTIF(A$2:A2,A2) filled down to the rest of the column for the purpose of finding duplicates in column A (rows where the formula result will be >1). This is an extremely common referencing method for formulas that look only at the top of the table (from the current row and up) and it used to work correctly, even after a sort.

Bug was first reported in version 10.0 in June 2020. It still remains in version 14.4 in April 2025.  Almost five years, yes FIVE YEARS, and still counting…

INDIRECT, OFFSET, INDEX, and FORMULATEXT do not work correctly when referencing cells in categorized tables.  Bug remains in version 14.4

When changes are made to a categorized table and rows move around (such as sorting), these formulas do not keep up with the changes. It is as if they are still referencing the prior version of the table. For example, say INDIRECT(“Table 1::B5”) is giving the result “4” (the value in cell B5). After a sort, that row moves somewhere else and now cell B5 has “10” in it.  The formula still has “Table 1::B5” but the result is still “4”, not “10”.