Glide not working on cellular data or mobile data

[Hbrezy]

Hi everyone

I’m experiencing issues with glide working via cellular data. The app is simply not loading or starting at all. Over wifi it work perfectly 100% of the time however the minute switch to cellular/mobile data its almost like the app is non existent.

Any advice on how to fix this as this is a major step back for us. I really like what the team at glide are doing but this issue simply means I can not invest any more money or time with glideapps if they don’t fix this major road block any time soon. Its a shame as everything else is almost perfect.

Would love to hear from anyone else experiencing this issue also.

Thanks

HB

[SantiagoPerez]

Do you have a url to the app that we can test?

[Hbrezy]

Hey SantiagoPerez

here is the like - https://nearbysaver.glideapp.io/

please note its not just this app my other apps also dont load half the time via cellular data.

Thanks
HB

[david]

What cellular provider? What country/state?

[SantiagoPerez]

It does load on cellular data at least where I am.

As David said? What country? What cellular company?

Have you tried with different devices on different cellular companies?

[Hbrezy]

I’m using Three mobile in the UK in Oxford, Oxfordshire. I noticed the issue today when decided to try out the app via mobile data and the performance was not good. I’m now looking for alternative solutions as i need to get this project underway.

[Hbrezy]

have you tried saving it to the home screen and open it again? that where it doesn’t load sometimes.

[SantiagoPerez]

I just did and it loaded no problem.

Please take screenshots when trying to visit https://debug.fly.dev/ and https://debug.ipv4.fly.dev/.

These would let us know what is going on with the network.

I recommend opening a ticket, sending the support link and the screenshot of those two links to https://glide-help.zendesk.com/hc/en-us/requests/new

[Rosewebstudio]

Just tried in the UK on O2 network.

Loaded fine.

Probably best to follow the latest advise given by @SantiagoPerez in his post. Maybe a local network issue with 3.