Hi all,
Thanks for any help in advanced.
As mentioned in the title, I am getting error whenever calling Video Recorder’s recording methods, both “Start Recording” and “Start Timed Recording”.
When I removed the Video Recorder block, the app works fine without any error.
I wonder how can I troubleshoot this error?
Does Thunkable have any log file for me to troubleshoot the error?
Thanks.
Regards,
Simon.
Can you share a link to your project? Something is causing the app to crash. Adding some debugging statements may help and I can do that easier if I have the blocks you’re using. This is the method I use in case you’re interested: Debugging in Thunkable X (Video).
Hi tatiang,
Here’s the link for your checking:
https://x.thunkable.com/copy/7c0d65dda84056c73d87c1a31bf91c74
Thanks.
Regards,
Simon.
Even this simple setup crashes in the Thunkable Live app on my iPhone 13 Pro:
I tried replacing the component and it still crashes immediately after clicking the button. I tried a different screen… same problem.
Is there a reason you’re using the older snap-to-place interface?
Here’s a similar example using the newer drag-and-drop (DnD) interface:
https://x.thunkable.com/copy/38ca4e5d97c6871ab8fd08e583bbb294
See the first screen. You’ll need to enter your own Cloudinary API details on the Design tab.
Edit: In fact, it’s possible now that I think about it that Thunkable’s change from providing a sample Cloudinary account to requiring users to provide their own account is the reason for your app crashing. I’m not 100% sure that’s it but it’s possible.
Hi tatiang,
I found that some block layouts are different in the new drag-and-drop (DnD) interface, and the current interface seems to have more flexibility for me to manage the blocks.
Why is Cloudinary API needed, when there isn’t any file upload activity required?
Is there a way for me to see the details of the error?
I tested normal camera capture and audio recording as well, they are working fine. Only video recording is having error, and there is no error details could be found.
Regards,
Simon.
Hello @simontneoh @tatiang
Happy New Year!
Thank you for testing it and sharing more information.
We were able to replicate the issue and have flagged it to our engineering team. We will keep you updated as soon as there is any progress.
1 Like
Hi ioannis,
Thanks for your help and looking forward to your update soon.
Happy New Year 2025!
Regards,
Simon.
1 Like