Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iOS 8 whatsapp bug found

A

ANDYMILLMAN

macrumors member
Original poster
Jul 6, 2008
76
0
For those having endless issues with whatsapp crashing. If you send any word that has a double f in it I.e "off" This will cause the app to crash completely. This is likely the reason group chats are crashing too - logs show dispatch queue error being the main culprit
 
ANDYMILLMAN said:
For those having endless issues with whatsapp crashing. If you send any word that has a double f in it I.e "off" This will cause the app to crash completely. This is likely the reason group chats are crashing too - logs show dispatch queue error being the main culprit
Click to expand...

:rolleyes: stupid bug! and yes it does happen!! Now resolution please.
 
Tested it on mine and its the same, though I just sent a sentence to someone and it crashed as well...but they still received the message even though it doesn't show I sent it successfully on my end.
 
ANDYMILLMAN said:
For those having endless issues with whatsapp crashing. If you send any word that has a double f in it I.e "off" This will cause the app to crash completely. This is likely the reason group chats are crashing too - logs show dispatch queue error being the main culprit
Click to expand...

Oh wow, good find! I hope someone has told the Whatsapp team about that so they can fix it later?
 
ANDYMILLMAN said:
For those having endless issues with whatsapp crashing. If you send any word that has a double f in it I.e "off" This will cause the app to crash completely. This is likely the reason group chats are crashing too - logs show dispatch queue error being the main culprit
Click to expand...

My chats wouldn't load at all in whatsapp, it would just crash.
 
ANDYMILLMAN said:
For those having endless issues with whatsapp crashing. If you send any word that has a double f in it I.e "off" This will cause the app to crash completely. This is likely the reason group chats are crashing too - logs show dispatch queue error being the main culprit
Click to expand...

I think "tt" as well, because everytime I said "Battlefield", the app crashed lol
 
Hello there,
the cause of the random app-crashes is only related with the content of the message you've received or if you press the send-button. It's not only the "ff" pattern, the "fi" causes also a complete crash of the application. "fi" is used in some programming-languages to finish a "if-else"-statement. I hope on october, it's frustrating - BUT, Telegram works good on iOS8 b1 ;-)
 
Very frustrating, I had to fall back and use BBM until it gets fixed and/or B2 comes out and it doesn't have this issue anymore.
 
Why don't you tell the developers instead of posting on MacRumors? For those saying it's frustrating, why don't you just use iOS 7 until iOS 8 comes out? Surely you know you'll run into issues, so if it's so frustrating why do you bother?

Beggars belief.
 
You don't need to tell the developers about this, they will know about it already.

That's what this BETA is for.
 
ANDYMILLMAN said:
For those having endless issues with whatsapp crashing. If you send any word that has a double f in it I.e "off" This will cause the app to crash completely. This is likely the reason group chats are crashing too - logs show dispatch queue error being the main culprit
Click to expand...

File a Radar.
 
You load a beta knowing that some (many) apps will not work. The beta comes with lots of warnings. Developers find out about the new os the same day as everyone else around the world. Because an app doesn't work in beta 1, doesn't mean it won't work in beta 2. Last year I had issues that didn't crop up until beta 3, but magically went away in beta 4.

Either be patient, or don't use a beta as your daily driver.
 
For those who keep saying "It's beta, what did you expect?" this is a forum; what did you expect?

People keep posting threads here because people keep posting threads here. It's what Macrumors is for. The title of this thread is "iOS 8 whatsapp bug found." What did you expect?

For those who use the app, it's good to know why it's crashing and kind of have a workaround for the interim.
 
Workaround

It seems whenver a chat has one of the character combinations ff, fl or fi in it (case sensitive, so capitals are not an issue) the app will crash upon opening it.

As a workaround you can download your whatsapp sqlite database from your phone (for example using iexplorer) open it in a db management tool (for example sqlitebrowser) en remove the combinations using sql query, save the database and replace the current one on your phone. Re-open whatsapp and opening the chat should work now.

I ran below sql queries in order to place a space between the harmful combinations.

update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'ff', 'f f')
where ZWAMESSAGE.ZTEXT like '%ff%';

update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'fi', 'f i')
where ZWAMESSAGE.ZTEXT like '%fi%';

update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'fl', 'f l')
where ZWAMESSAGE.ZTEXT like '%fl%';

Unfortunately you have to repeat this everytime someone sends you one of these combinations again.

Regards,
Wouter
 
MalcolmJID said:
Why don't you tell the developers instead of posting on MacRumors? For those saying it's frustrating, why don't you just use iOS 7 until iOS 8 comes out? Surely you know you'll run into issues, so if it's so frustrating why do you bother?



Beggars belief.
Click to expand...


How do you know that people haven't reported it? I, for one, definitely have. Shouldn't assume should you. Why do you care if people are using it? You don't have to read the threads, let alone whinge about people using it. People like to try things. That's a good thing. It's just as frustrating as stupid posts like yours...
 
zigmob said:
It seems whenver a chat has one of the character combinations ff, fl or fi in it (case sensitive, so capitals are not an issue) the app will crash upon opening it.

As a workaround you can download your whatsapp sqlite database from your phone (for example using iexplorer) open it in a db management tool (for example sqlitebrowser) en remove the combinations using sql query, save the database and replace the current one on your phone. Re-open whatsapp and opening the chat should work now.

I ran below sql queries in order to place a space between the harmful combinations.

update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'ff', 'f f')
where ZWAMESSAGE.ZTEXT like '%ff%';

update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'fi', 'f i')
where ZWAMESSAGE.ZTEXT like '%fi%';

update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'fl', 'f l')
where ZWAMESSAGE.ZTEXT like '%fl%';

Unfortunately you have to repeat this everytime someone sends you one of these combinations again.

Regards,
Wouter
Click to expand...

Taken your work around a step further so you don't have to manually rerun your fix everytime someone sends you one of these combinations again.

Code: 
CREATE TRIGGER insert_Ff AFTER INSERT ON ZWAMESSAGE
BEGIN 
  UPDATE ZWAMESSAGE 
  SET ZTEXT = replace( ZTEXT, 'ff', 'f f')
  WHERE ZWAMESSAGE.ZTEXT like '%ff%';
END;
 
CREATE TRIGGER insert_Fi AFTER INSERT ON ZWAMESSAGE
BEGIN 
  UPDATE ZWAMESSAGE 
  SET ZTEXT = replace( ZTEXT, 'fi', 'f i')
  WHERE ZWAMESSAGE.ZTEXT like '%fi%';
END;
 
CREATE TRIGGER insert_Fl AFTER INSERT ON ZWAMESSAGE
BEGIN 
  UPDATE ZWAMESSAGE 
  SET ZTEXT = replace( ZTEXT, 'fl', 'f l')
  WHERE ZWAMESSAGE.ZTEXT like '%fl%';
END;

wanted a quick fix and it works well for me but if you can improve it fork away https://gist.github.com/jonathan-wheeler/0f8235f5904365e3c75a
 
  • Like
Reactions: pzumk
jonnywheel2 said:
Taken your work around a step further so you don't have to manually rerun your fix everytime someone sends you one of these combinations again.

Code: 
CREATE TRIGGER insert_Ff AFTER INSERT ON ZWAMESSAGE
BEGIN 
  UPDATE ZWAMESSAGE 
  SET ZTEXT = replace( ZTEXT, 'ff', 'f f')
  WHERE ZWAMESSAGE.ZTEXT like '%ff%';
END;
 
CREATE TRIGGER insert_Fi AFTER INSERT ON ZWAMESSAGE
BEGIN 
  UPDATE ZWAMESSAGE 
  SET ZTEXT = replace( ZTEXT, 'fi', 'f i')
  WHERE ZWAMESSAGE.ZTEXT like '%fi%';
END;
 
CREATE TRIGGER insert_Fl AFTER INSERT ON ZWAMESSAGE
BEGIN 
  UPDATE ZWAMESSAGE 
  SET ZTEXT = replace( ZTEXT, 'fl', 'f l')
  WHERE ZWAMESSAGE.ZTEXT like '%fl%';
END;

wanted a quick fix and it works well for me but if you can improve it fork away https://gist.github.com/jonathan-wheeler/0f8235f5904365e3c75a
Click to expand...

Do you have step by step instructions, on how to get it to work?
 
Considering Whatsapp updates their app about once per year, I wouldn't be holding my breath for a fix :(
 
Whatsapps latest beta works fine with iOS8 for me, now they need to release it...
 
jonnywheel2 said:
Taken your work around a step further so you don't have to manually rerun your fix everytime someone sends you one of these combinations again.

Code: 
...
wanted a quick fix and it works well for me but if you can improve it fork away https://gist.github.com/jonathan-wheeler/0f8235f5904365e3c75a
Click to expand...

Thank you so much! German is a Language where there are LOTS of ff and fi, so nearly all of my conversations were crashing whatsapp. Now its working perfectly fine again.
 
Daku93 said:
Thank you so much! German is a Language where there are LOTS of ff and fi, so nearly all of my conversations were crashing whatsapp. Now its working perfectly fine again.
Click to expand...

How did you get it to work? The code of the guy above, where you have to do it manually every time, works perfectly, but the "better" code doesn't seem to work for me... :confused:

I`m also from germany ;)
 
OneZweiThree said:
Do you have step by step instructions, on how to get it to work?
Click to expand...

Its actually very simple but if your not comfortable with the steps then I would strongly suggest you don't try it but considering people in this situation are on the beta I assume you at least have a vague understanding of all the processes involved.

1. Turn off icloud documents for whatsapp (Settings> icloud>Documents & Data) and also turn off any funky accessibility settings you might have like zoom or bold as they also cause issues with whatsapp. Turn off wifi and turn on airplane mode(prevents you get new messages during the process) Quit whatsapp and close it fully(double tap home button and swipe it away).

2. Download and install iExplorer (free trial)

3. If you don't have anything that can connect to sqllite databases I'd suggest you go with Navicat for SQLite (free trial). Download and install.

4. Plug in your iphone and open up iExplorer. Click "Apps> WhatsApp> Documents" right click "ChatStorage.sqlite" and export to folder.

5. Go to the location you exported the file to and make a copy of it for a backup. Open the sqlite file in navicat. Click on the connection in the left hand panel and rightclick on the database think its called "main" and select "New Query".

6. A new window should appear, click on the "Query Editor" tab and paste in.
Code: 
-- Cleans up existing messages --
update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'ff', 'f f')
where ZWAMESSAGE.ZTEXT like '%ff%';

update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'fi', 'f i')
where ZWAMESSAGE.ZTEXT like '%fi%';

update ZWAMESSAGE
set ZTEXT = replace( ZTEXT, 'fl', 'f l')
where ZWAMESSAGE.ZTEXT like '%fl%';

-- Sets up trigger's to re-clean message text when ever new messages are created --
CREATE TRIGGER insert_Ff AFTER INSERT ON ZWAMESSAGE
BEGIN 
  UPDATE ZWAMESSAGE 
  SET ZTEXT = replace( ZTEXT, 'ff', 'f f')
  WHERE ZWAMESSAGE.ZTEXT like '%ff%';
END;
 
CREATE TRIGGER insert_Fi AFTER INSERT ON ZWAMESSAGE
BEGIN 
  UPDATE ZWAMESSAGE 
  SET ZTEXT = replace( ZTEXT, 'fi', 'f i')
  WHERE ZWAMESSAGE.ZTEXT like '%fi%';
END;
 
CREATE TRIGGER insert_Fl AFTER INSERT ON ZWAMESSAGE
BEGIN 
  UPDATE ZWAMESSAGE 
  SET ZTEXT = replace( ZTEXT, 'fl', 'f l')
  WHERE ZWAMESSAGE.ZTEXT like '%fl%';
END;

7. Click the Run button and the query will execute. Exit Navicat and copy the sqllitefile back into the Whatsapp directory on your iphone. Whatsapp will still crash when ever you receive a message with these combination but when you reopen it, it should work fine.

Seeing as the issue will probably be fixed by the time iOS8 goes public it is probably best to remove these triggers once its stable. Just repeat the previous steps but run these queries instead.
Code: 
DROP TRIGGER insert_Ff;
DROP TRIGGER insert_Fi;
DROP TRIGGER insert_Fl;
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back