# All webviewers broken in thunkable live, ios and android after update **URL:** \ **Category:** Issues / Bugs\ **Created:** [January 13, 2026, 2:39pm UTC](https://community.thunkable.com/t/all-webviewers-broken-in-thunkable-live-ios-and-android-after-update/4108231 "2026-01-13T14:39:33Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [January 14, 2026, 5:30pm UTC](https://community.thunkable.com/t/all-webviewers-broken-in-thunkable-live-ios-and-android-after-update/4108231/3 "2026-01-14T17:30:02Z")
Hi @grant.mccallum We have changed only 1 thing, and it was a needed bugfix - when we post a message through the web viewer, previously, we were sending whatever type the user has chosen - e.g., if you send the number “1”, we’re sending 1 as a number. Now, we are stringifying everything, meaning that if you send “1”, it’ll be 1 as a string and not as a number. This means that, whoever is receiving or consuming the message, should handle it accordingly. In the case of “1”, it’s “simple”. But if you decide to send a whole object (e.g., `{ name: 'John Doe', age: 20 }`, then this will be sent/received as a string, and the receiver must cast/parse it to an object and then they can use it as such Could you please let me know if you have more questions? --- _[View the full topic](https://community.thunkable.com/t/all-webviewers-broken-in-thunkable-live-ios-and-android-after-update/4108231)._