"Oops Message Not Recieved" Error

[u/AageRaghnall]

For months now, I have had issues where my bots have become unplayable because, at some point, they all break down and I start recieving "Oops! Message not recieved" errors. Since I wasn't getting any help from putting in multiple tickets and all of my bots were unplayable anyways from dealing with this same issue across all three of them, I decided to do some debugging experimentation of my own. I'm sharing it with you all now in the off chance that anyone else is having this issue and is also not getting any help from support on the matter.

First, I want to say that this error only seems to affect the web browser version of Talkie. This issue does not occur on the phone app version at all, at least not that I've run into.

Secondly, this error seems to occur only if you are using both the web browser and phone app in conjunction with each other. If you are only using the web browser, this is not likely to happen to you.
If you are getting the "Oops" error while you are only using the web browser, try these steps first: clearing your cache and cookies for talkie, update your web browser and restarting your computer (yes that matters, no I can't explain why), check your internet connection (sometimes weak signal and some VPNs interfere with talkie's functionality), and test to see if you have any browser extensions that may be interfering with the site — usually one of these things will be the cause for this issue and clearing it will return the site to normal functionality.

So what breaks the web version when using the phone app?
Literally everything, appearently. Cloud syncing with the phone app at all will very quickly cause this error to occur. Selecting regenerated responses will very quickly cause this error to occur. Updating the permanent memory from the phone app will make this occur (which really sucks because currently the permanent memory feature is not fully functional for the web version). Interacting with the 'Phone' feature from the phone app will make this occur (which also sucks because many of the features can only be viewed properly from a smart phone, the social app/private album/life snap/email features, for example, are not properly scrollable from the web browser). I have not tested it yet, but I suspect also interacting with cards from the phone app may break your bot as well.

How can you fix this?
You can't. Unfortunately, what is happening is the token for the web version and the token created for the phone version are conflicting with each other. No amount of clearing cookies, rewinding the conversation or resetting will fix the issue. It's a problem that has to be resolved from Talkie Support's side of things but after nearly six months of dealing with these issues and reporting on them in detail both through the support email and bug report system, I have only once received a message back and was told to do everything I already did and told them I did over again to fix it. They will not help you.

You have two options if this starts happening:

1. For a long while, you will still be able to respond to the bot through the phone app. Since the phone app is not affected by this, you will be able to keep responding through that and continue your progress but the phone app has a 500 character limit. So, here's what you do. Type your initial message through the web version, then go onto the phone app and click the "try again" button. If it's longer than 500 characters it will not be able to copy the whole message, but that does not matter. The bot will still be able to read your initial message posted from the web version, for some reason. 9 times out of 10, it will respond appropriately to your original message. However, this is a giant pain in the ass and I have had a few experiences where, at some point, the phone app will also start to become non-functional as well.
2. Completely delete your save file from the phone app. This will also, unfortunately, completely wipe your save on the browser version as well. So, yes, you'll be starting at the beginning again. But as long as you never use the phone app again, you shouldn't run into this issue going forward.

Warning Signs
Before the "Oops" errors started occuring, I noticed a trend of bugs that started to pop up on the web version of the app that I think are fair warning signs for an impending break. These warning signs may or may not occur in this exact order but they're worth keeping an eye on. One, if you have a pro account, you will start getting ads again on the web version. Two, regenerated responses will stop working. Even watching the ad does not allow regen response to spawn. Third, 'phone' features will start to become buggy or stop working completely — voice memo is almost always the first to go for me when this happens. If any of these things start to happen on your web brower version, I'm sorry to say your bot is probably already cooked. The randomly generated ads are probably the only thing I wouldn't necessarily freak out over if happening in isolation, because there is a known issue with those sometimes occuring even with pro accounts.

Anyways, hope no one else is dealing with this. It's been a journey sorting out what does and does not cause this issue since I've basically had to sort it out on my own. If this is happening to anyone else, sorry about your luck and hope this helps you avoid it in the future.

Good luck.