This link is my app according to your suggestions
1.Yes
2.Yes
3.No
You didn’t fix any of the problems I mentioned. Please try the project I posted a link to above (Unable to parse Web API response - #18 by tatiang) and let me know if that works when Live Tested on an Android device. It should.
sorry, I got the wrong link
here the right one
https://x.thunkable.com/copy/5115cb3a8b8397b3a78b0dc1323223db
1.Yes
2.Yes
3.NO
When I test it, it also does NOT work in Thunkable Live on an Android device. Even this doesn’t return any response (and the green error
block is empty when I check its value):
It works fine on an iPhone.
Maybe there is some problem with Google Scripts and Android devices? I don’t know.
I think you should file a bug report because on both iOS and Android devices, I can see the script response in a Chrome browser (I made a shortcut link: https://bit.ly/androidz123). So I think it’s something Thunkable is doing to run the script or get its response.
hi
I wouldn’t insist. I will proceed otherwise.
in any case, thank you for your help, for the time you devoted to me,
without forgetting muneer
What kind of device are you running on @bibbi and @tatiang ? I ran this on a Nexus 2 in both live preview and as a downloaded apk with this block combo and didnt get an error
I’m using a OnePlus Nord N100 5G running Android 11.
hi
my device is a realme 6 android 11
Can you guys try this project for me?
https://x.thunkable.com/projectPage/61e72aaaa686bf00118de789
Just to verify?
hi
I just tried it
that works !!!
two small questions
how? why?
Aha! Figured it out. Delete the loading icon and it all works perfectly, even the older project (Thunkable) from Unable to parse Web API response - #23 by bibbi.
Here’s that exact same project with the loading icon deleted and the loading icon blocks removed:
https://x.thunkable.com/copy/e523e49630f02d699a504dbfca4225af
The blocks don’t affect it, though, just the presence of the loading icon component.
This could be related to this bug report: Adding loading icon bugs project · Issue #864 · thunkable/thunkable-issues · GitHub
I was in a trip and could not be part of this adventure. I think I missed a lot.
However, let me add some comments on my side. I do not believe that there is something wrong with the Loading Icon
in this particular case despite of the BUG report.
There is a more subtle issue with how Thunkable process Starts/Opens
events in Android. You can safely leave the Loading Icon
in place but change the Opens
event of the screen to Starts
and the original project of @bibbi should work just fine.
Oh, interesting. Good catch!
Here’s a simplified project that demonstrates the issue (I left the loading icon in):
https://x.thunkable.com/copy/bc38cec6164a60886181360fdecc1162
The first screen uses When Screen Opens and the second screen uses When Screen Starts.
In Thunkable Live on iOS, both screens function properly, showing the list of email addresses in the label.
In Thunkable Live on Android, the first screen does not function properly, showing “label” in the label. The second screen does function properly, showing the list of email addresses in the label.
However, if I delete the loading icon, both screens work on both devices:
https://x.thunkable.com/copy/c7fb15dd86cac79bd8f970bbd4b9ddf7
Do you know is it only the loading icon or do other blocks make this same issue occur? Thank you for helping to sort this out @muneer and @tatiang
Thanks @tatiang for the example.
However, I always have unexpected inputs.
The Screen Opens/Starts BUG
is somehow strange and I have previously tested it and it goes this way.
The first screen in the project should have Starts
, any other screens can have Opens
.
So, based on this, Can you have the first screen using Starts
and the other screen using Opens
which is the reverse of your example and you will find that both screens will work in Android.
Here’s the project with Screen Starts first:
https://x.thunkable.com/copy/377766f9c7e167c06c6603a18078824b
Both screens work on iOS and Android.
@jared I don’t know. I’m still not quite sure how the loading icon relates to the screen starts/opens event.
Me too. I’m just sharing observations that I had days ago.
Thanks for everyones input. I have escalated this as an internal bug with a reliably reproducible and simplified example. I appreciate the help and will keep this channel updated when the bug is resolved.