[Solved] Is there any problem with x.thunkable server?

what is that exemple ?

So the developer are working we can be assured??

Hi. My app is crashing both on Thunkable Live and apk, it just happen yesterday. I’ve tested the app one day before the error it works fine. My app have about 10 pages in drawer navigator. About 5 of the pages are crashing (even the page that i didn’t do anything to it) when i click on a button to upload to Airtable, Local Storage.

One more problems is that on the screen that doesn’t crash I set the text box to blank after upload to airtable. sometimes the textbox text input still appear until i touch the screen and sometime the hint are gone after they clear the textbox.

I have Loading Icon on each screen and one label as a notifier. I use columns and rows on each screen to reduce Screen since the app already have 10 screen already. i use the visible: true/false to show and hide rows and column. I have about 5 airtable component. and 3 local storage component. barcode scanner and photo library component.

Note: work fine on ios app. haven’t test on ios live app.

share the app please , we have all the same problem :frowning: but they do there best !!

I hope so, but how long will it take I don’t know

yes it is

Sometime, after crash it shows a screen saying : Uncaught Error: Attempting to disconnect view that has not been connected with the given animated node. Fatal error

I have the same problem (sorry for annoying anyone):

  • my app starts normally
  • I open another screen, where I change some button texts (language dependend) triggered by “screen open”. The buttons get only displayed after I touch the display. It seems as if the “machine” behind ThunkableX freezes and events get stopped. When I touch the display, the changes become visible, but only one after one…

My app is different compared to older versions because I use the “Local DB” a lot: It saves me a lot of space and variables, because now I can store most of the values in the DB. Is this maybe causing trouble?

PS: why is the status set to [solved]? It is still an issue.

It sill a issue ! We have all the same issue … @domhnallohanlon @Mark

Update: This seems to be working again in the Live application on both iOS and Android. Can you please test your apps if you have been experiencing this issue and report back if it now works for you as well?

The screen update issue is still there btw.

The screen problems stay there I wrote them on github @Mark told me that they don’t have this problem using my app add it also on github please with your link to your app

I still have the problem on all my ios devices

Can anyone take the status solved out please !!??

Any component is just so powerful and important for building dynamic apps :sob:

That is my question too why this status marked as solved??

hello @danyklein @domhnallohanlon My app is working now!!! everyone check your apps . But i dont know would it be stable or not?

I am currently updating my app. I will keep you posted.

So I just updated to ios 13.3 beta 3 and it’s working now !

Thanks goes to @domhnallohanlon @actech @jane and all thunkable stuffs.

Regards
Farhad

3 Likes

We had very little to do with it @farhadkubd1, our incredible team of engineers we able to deploy a fix a few hours ago, and are keeping an eye on the situation.

Thank you to all the Thunkable users who helped out with feedback and shared their projects to help get a resolution to this.

3 Likes

THX to you all :smiley: @domhnallohanlon

1 Like

My android app is still crashing. IOS works fine