XF 2.2 Bug when using mobile phone
- Thread starter Suzanne O
- Start date
Solution
There have been further reports of this now but still no way for us to debug this because it is working fine for us.
If anyone who is affected feels comfortable connecting their iPhone to their Mac via USB and doing remote debugging through the Safari browser that will be useful, but for now we’re going to have to wait and see if this rights itself or we get more information.
If anyone who is affected feels comfortable connecting their iPhone to their Mac via USB and doing remote debugging through the Safari browser that will be useful, but for now we’re going to have to wait and see if this rights itself or we get more information.
While I'm still unclear on the specific details, it seems this is a known issue with the latest version of Froala, v4.1.2.
We have rolled back to the last-known "good" version, v4.0.19.
Hopefully the issues are now resolved for you guys (although sometimes caching can be a bit tricky and may stick around for a bit).
We have rolled back to the last-known "good" version, v4.0.19.
Hopefully the issues are now resolved for you guys (although sometimes caching can be a bit tricky and may stick around for a bit).
FTL
Well-known member
All I ask is that whatever Froala is eventually replaced with won't feel like a downgrade.
Again, while I understand why you use a third party product since you explained it a while back, going by the smooth way XF works, I'd have more confidence in you guys developing your own editor that really makes the most of XF and doesn't have those stupid long term bugs in it either. Never say never.
It absolutely won’t be a downgrade. It’s an upgrade in every conceivable way. It just won’t be ready for a while.All I ask is that whatever Froala is eventually replaced with won't feel like a downgrade.
Again, while I understand why you use a third party product since you explained it a while back, going by the smooth way XF works, I'd have more confidence in you guys developing your own editor that really makes the most of XF and doesn't have those stupid long term bugs in it either. Never say never.
We’ve already found one and it is actively in development.
FTL
Well-known member
Latest is now iOS 17, just released yesterday. Try upgrading to that and see if the problem persists.
FTL
Well-known member
I'm suggesting it from the point of view of troubleshooting rather than a full solution. Of course, you want it to work properly on a multitude of older operating systems, browsers etc.
FTL
Well-known member
btw it works ok on my iPhone running 16.6.1 and Safari.
@aussiefooty you might want to try another browser first before upgrading the OS if clearing the cache doesn't work.
@aussiefooty you might want to try another browser first before upgrading the OS if clearing the cache doesn't work.
digitalpoint
Well-known member
Have seen that a couple times and end has ended up being an operating system issue for whatever reason (rebooting phone and/or browser fixed it for me).
FTL
Well-known member
@digitalpoint Reading your post reminds me that sometimes Safari goes a bit haywire, preventing me from posting - the post button reacts, but nothing else happens. Closing and restarting the browser fixes it. Another one is where pages suddenly stop loading, which happens on Wi-Fi or cellular and perhaps one or two others. Hence, @aussiefooty could just try restarting it and seeing if it fixes it. And yeah, rebooting the iPhone isn't a bad idea either.
digitalpoint
Well-known member
I think there’s something fundamentally wrong with the keyboard in iOS 16. Like my iPad wouldn’t show the keyboard when trying to enter the passcode when it first reboots. Have to hit the lock button and try again like 5 or 6 times until it would show. That’s just trying to unlock device (not in an app). Weirdly it was never my phone, only my iPad. And I think it finally resolved itself after upgrading to iOS 17 (at least hasn’t happened yet that I’ve seen).
Similar threads
- Question
