Thunkable Team! This is outrageous! Not only since your last update the performance of app has dropped dramatically (we have published a topic on this matter and you just do NOT seem to care), furthermore since your last update you no longer support rendering in CREATE of images format base64 (data:image/jpeg;base64,…… or pure base64 or format jpg) just like that!!! This is unbelievable and outrageous! Leaving us wit screen and program logics that simply do not work anymore. If you are playng busines WE ARE NOT!!! Much more outrageous is the fact that you just do not care to give a professional answer or any answer!!! We wish to remind you that we PAY for using your system and the least we can expect is that your team replies in a professional way to our urgen topics with a concrete plan regarding WHEN this bugs will be fixed on your side!!!
Hello @pmginvestda6z
I understand that it is frustrating, and I am sorry for the trouble caused by these issues.
Your previous post was on a topic that we have provided a solution for, and the best way to get a response fast is to create a new topic for your issue, as you did here.
At the moment, I am still trying to replicate your issues on a new Thunkable project.
For the Base64 issue, here is the image I used and it worked:
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAAXNSR0IArs4c6QAAAA1JREFUGFdjWH4p9z8ABvAC5ua4Z50AAAAASUVORK5CYII=
Also, could you please share the project that you have the performance issue?
This way we can investigate it further.
We can of course share the project with you, but let us take one issue at the time! Please read our post again, what we are clearly saying is that a few weeks ago our app worked just fine. Then without any change whatsoever from our side, CREATE items in users information container Iin the blocks) does not work any more. We know of course that assigning a base64 in the design panel to a picture component (as you show in your reply to us) works. This was NOT the issue we wrote about.
Hi @pmginvestda6z
Thanked for sharing more information.
It’s is still not clear to me what you mean by “Create Items”.
Could you please share a screenshot of your blocks?
Something that have changed in the last release and it might help you is this: https://community.thunkable.com/t/all-webviewers-broken-in-thunkable-live-ios-and-android-after-update/4108231/3?u=ioannis
Also, please share the link for your project on a personal message.
Thank you again for your time and patience.
When I read through the link you attached in your reply I get even more perplex! How do you handle and render images in format base64? Does your change in “stringifying” impact on that too? If so we actually need to rewrite the entire application.
Hi @pmginvestda6z
We can understand that it is frustrating and we appreciate you taking the time to investigate and provide more information.
I can replicate the issue with the create image block inside a container, so I have flagged it to our engineering team and will provide an update as soon as possible.
Please ignore the link I sent in the previous post, it is a different case.
Thank you. Please notify us immediately as soon as it is done on your side.
When can we expect the bug fixed???
Hi @pmginvestda6z
Thanks for your patience.
Unfortunately, we don’t have an exact timeline for when a solution will be released but we will provide an update as soon as possible.
If you need an immediate workaround, you could add an image component inside your screen and then use the clone block instead of the create image block.
Hello Ioannis. I am shocked! Unfortunately you do not have the exact timeline to fix a serious bug in your system???!!! Do I read you right??? At this point I am questioning the professionality of Thunkable. Cloning does NOT work stable and has issues in iOS. All we are trying to do is to populate a list on the screen containing an unknown number of items consisting of user picture and some inf text!!! Simple List in your system does not support picture and text, Data Sources is not supported in iOS, Cloning is unstable and not supported in iOS, CREATE after your latest update does not work anymore and you have tested and found and established it your self! I just wonder, is anyone else reading this?! Are you aware of the damage your are causing?
Hello @pmginvestda6z
I am sorry that my workaround didn’t work for you.
Another workaround is to use the Create button block like this:
Could you please explain what you mean here?
Data Sources are supported on iOS.
Hi Ioannis,
sorry, I mentioned problem with iOS regarding Data Sources. The problem was in Android, not in iOS as you can see from our post here: Dataviewer in Android vs iOS to which by the way no response from your side. However I wish to respectfully remind you that the issue in focus is the fact that there is a bug in your system which you have recognized but not fixed immediately as it is expected from a system on which many apps are developed. In our case we have used the CREATE mechanism throughout the entire App and it all was working fine until your team made the last upgrade. Can you please give us a precise deadline for fixing this bug.
Hi @pmginvestda6z
Thanks for sharing more information.
Sorry for the late reply to your previous post. I missed it.
The engineers have been informed about the issue with the Create Image block, and I will provide an update as soon as possible.