Large portion of users not able to fetch data from remote config.

Hello,

We have recently released our game UnderKnight: One Thumb Warrior to the play store early access.

We have seen that a lot of our players seem to get stuck getting the data from remote config even though they have a good internet connection.
It seems configresponse is never returning success for them.

Any help would be appreciated.

 

Just want to chime in on this too, a title we've been testing has been experiencing the same issue for the past few days - we have some users that can receive data from Remote Config, but others haven't had it work once!

*Edit* Also wanted to note this is happening on the Android/Oculus Quest platform, if that helps!

 

Yep, the affected users end up with our default values. Its consistently reproducible on their devices - users with the issue always have the issue, and those without the issue don't get the issue later (as far as we've seen in our testing).

Could it be an issue with the user's network/firewall settings? We have other network queries in the game (mostly to Oculus servers) that work with no issue on all devices.

 

For us(mobile), the affected users keep having the same issues no restart phone or re-install fixes the problem. Players who do not have the issue never encounter it.

So the same behaviour austineast is experiencing.

Thanks for looking into it!

 

It occurred immediately, when we started testing beyond our dev team. But we have some interesting news for the potential source of the issue - a playtester who was experiencing the issue ended up having a DNS blocker setup at their house (a raspberry pi-based "pi-hole", specifically), and it's default blocklist (which you can see here: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts) blocks many of Unity's domains. After they whitelisted `unity3d.com`, the Remote Config service was working fine for them.

A little frustrating but at least we have something to try when other players report issues in the future

I know there's nothing you guys can really do about this specific issue, but it may be worth mentioning this somewhere in the docs as a potential troubleshooting step, seeing how popular DNS blockers (especially pi-holes) are these days.