@domhnallohanlon
Now that I am testing my app on iOS testflight, I’m running into an orientation bug. Where when I tilt the phone it will move the screen in landscape orientation and I didn’t design it to support this orientation. How do I lock my app from not respond to landscape orientation? On Android publish my app does not respond to landscape so this problem is not present.
All my pages are set to Portrait
Here you can see visual issues because it’s responding to landscape.
When i flip my phone back and my app flips back to portrait the buttons don’t respond. App has to be closed and reopen for buttons to respond. This is a show stopper bug.
Any news on this? Today was the first live use of my app this season and all 30 users have spent the weekend reporting this issue to me.
Really urgent this one! @jared@domhnallohanlon@cassandra@wei
One of the championships using my app has now cancelled the contract and requires refunds for all 32 users £10 each subscriptions due to the instability of the app caused by this issue. I suspect more will follow.
Just to be clear, I am not overly worried about sorting the issues that result from the device rotating, I just need the Thunkable portrait lock to work.
This issue been since February i hope it would be fixed soon since i cant update my APP’s ios version till it is fixed. unless i put a message in the APP asking people to please make sure that their device is set-to lock on portrait screen while using the APP i don’t how users will take that message they might just uninstall
I am genuinley very pleased that you have reached 3m Thunkers and secured the series B funding, however by contrast my project could be over this weekend as another championship with 45 subscribed users will discover that the app is unuseable with this current orietation issue.
Please can you focus all your attention on sorting this issue today as any later will not give me time to get the update rolled out and approved by Apple.
You are seeing things wrong. We are all concerned but I’d rather seeing it fixed the right way than seeing it fixed the quickest way just to see it fall apart again after few more updates.
I just wanted to post an update on this. So, the TLDR; is that we were relying on an old package that used to work but for some reason has broken over time. Instead of trying to apply a bandaid that will probably not work in all cases, we are formulating a solution that will work for all users and operating systems. That said, it is taking longer than we had originally planned and we want to acknowledge this and thank everyone for you patience and diligence in holding us accountable for fixing this bug.
I only want to comment here and say that fixes are priority based but even though only a few have raised this issue, this is actually a high priority that is unfortunately requiring a very complex fix.
We hope to have this resolved soon and as soon as I can I will circle back around with updates on this matter.
Thank you all for your input here!
[Update]
We have a fix in review at this time. There’s no promises yet, BUT that’s a sign of good things in the works!
,