Similar to the user in this thread (Stalled loading on almost all non-host devices) I’m not able to use Live Links to view my site on either iPhone or iPad. It works perfectly when using Desktop (Mac and PC) as well as Android. When I type in the localsite.io page it asks for the username and password, it accepts that, but the page never populates. I can use the /wp-admin just fine, just not able to view the live page at all.
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc
Restarted, no fix. Updated to new OS, no fix. Cleared CSS, no fix. Disabled all plugins, no fix.
Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
Hey @scmaverick! Are these devices using WiFI or LTE Data? Or are there any other unique connection differences between them? That could be one possibility.
Hey Nick. I’ve actually tried both LTE and WiFi for iOS. Desktops have all been on WiFi. I can’t think of anything that could be blocking it. After I posted last night, I ran across a thread that someone else uninstalled and reinstalled LocalWP and that fixed a similar issue they were having. I haven’t tried that but think that may be the next steps for troubleshooting.
I’m using Divi as a theme and once I changed it to the default theme LiveLinks worked immediately. So there has to be something with Divi that is blocking it. The site is almost finished so I won’t have to worry about LiveLinks for too much longer.
Ahh okay good catch! I just did a quick test of a Live Link on my iPhone and it worked fine, but it’s just using a default WordPress theme as well.
A quick Google search for Divi Mobile issues, and I’m seeing some recommendations for checking versions, regenerating CSS, or fine-tuning other settings. It might just have a specific stuck setting or feature that’s conflicting.