It’s still saying the new link is unavailable. We’ll probably have to wait for it to populate the App Store.
Can’t find any message button.
Strange that it showed up within the topic window and not on a separate page. What happens if you go to Profile - domhnallohanlon - Community?
Do you have Do Not Disturb turned on in your profile?
Thanks a lot, The Blue message button finally appeared on his profile.
Everything back to normal for me… moments ago.
Any explanation?
Same for me. Happy to have the explanations as well
Hi @lamagalhaes @vincent.pappollakvt - appreciate your patience as we looked into this matter.
Our dev team just released some updates that caused this issue. They’ve reversed the release and we’re continuing to investigate what exactly caused this.
Let me know if you have any further questions!
Thanks for you reply @cassandra
What I don’t quite understand is how some Thunkable updates, wherever it is… servers, live companion, etc… affects already published apps on the stores.
Could you please enlight us?
We released a major security update on the platform. There was a minor bug and caching issue that affect the web apps. I expected this impacted web apps or apps with data viewers or data sources as they depend on our platform. Sorry for the inconvenience.
Best,
Wei
Thanks for the update.
has it affected thunkable live too?
I’m still unable to test my app (blank) live on the device (android).
I don’t think so. Can you try to sign out and sign in again?
just tried it several times.
still not working.
tried on different android devices.
i enter the code and get stuck on the blank screen with the thunkable logo.
it was not working 2 hours ago and the service got back working for less than a hour.
Dear wei,
i tried thunkable live with my google account. It’s working fine.
Usually I’m logged in via e-mail (Pro membership) and in combination with this account it’s not working.
@wei @domhnallohanlon Would someone mind clarifying what this means? Why would a published app depend on something from you after it’s published? How would it work if there was no internet available? I was told early on that apps were NOT dependent on your platform after it was published. Please clarify.
Who told you this?
It was over a year ago when I was first considering the platform. I was asking questions either here or via chat. I’ll see if I can find. I was wanting to know if I ever ended my subscription or if the company (Thunkable) went away, would my apps keep working. I was told yes.
For privacy reasons alone, the apps should not be dependent on the platform.
PS. And I’m not talking about using Airtable or those types of data sources. I understand there may be some interdependency there. I don’t use those sources. My data sources are in-house or stored on the device itself.
one of my apps uses Airtable and was affected by this outage. I spent some time trying to contact Airtable as I too had no idea that after an app is published it is still reliant on thunkable?
Does firebase also rely on Thunkable servers?
Most, possibly all, apps built using Thunkable and similar builders rely on the builder.
apk / aab files contain code from the builder which tells the builder about things like usage stats, crashes etc.
If you are connecting to your Firebase DB using Web API
calls and you manage your own user token and authorization tokens then Thunkable platform would not impact your published app.
In the other hand, if you are using Thunkable components then somewhere in the net someone is making it easy for you by providing the connection service and generating these tokens on your behalf.
In the end, Firebase needs these tokens to provide you with information and you either generate them yourself or have someone generate these tokens every time you access Firebase.
Hope this clarifies the situation.
Out of curiosity, if I may ask, how do you manage the Firebase tokens via Web API the way you described? I’ve been just using the standard Firebase components in Thunkable. Would be nice to have a short description or an example if you care to share @muneer
Thank you!
/ Heikki