"Trusted" Networks and issues connecting in android app

Recently I’ve been having issues logging in through the android app. When I go to connect, I select the Google account, confirm it, twingate says connected for a second then kicks me back to the “sign in to connect screen”. Looking online and through the forums I found a post from a while ago saying to clear data and cache, after doing that it still kicks me back to the sign in screen, i jave also uninstalled and reinstalled but have the same issue. Some others recommend to click a different login type i.e using the MS one and exiting. Some times this works other times it doesn’t. Then after many attempts I am finally able to log in.

On that note, I would not mind being connected pretty much all the time, but while I’m on local it won’t let me connect to a couple other things, like my roku. Would it be possible to have an option to let my connection bypass the vpn while on “Trusted networks” and once I’m disconnected from that network the vpn kicks in? It is an option on my other vpn (keepsolid). But I have not had a need for that one since I set up twingate. Or would I need to add the roku’s ip to the resources list? Only issue is I cannot set a static ip on it through the roku, least I haven’t seen an option, so if it changes I would have to update it in the resources. Not something I’d want to do after hopping in bed and have to get up or vnc to my main comp.

Thanks!

Hi there,

strange login experience indeed, I don’t think we’ve seen a user on Android getting kicked out like that. Can you share the model / version of your Android device?

For your Roku question: there is currently no option to setup a “trusted network” that would automatically bypass Twingate, that being said, Twingate will only intercept traffic that matches resource definitions and nothing else. For your Roku, if its private IP changes on a regular basis, I’d check within the settings of your router, most these days will allow you to assign a static IP to any arbitrary device on your network. Since it’s controlled by DHCP (most likely), it won’t be within your Roku device itself but with the router.

You could for sure add a resource for your Roku’s IP and you could even give it an alias so as to not have to remember the IP of it. You could also create a resource that covers your entire subnet (like 192.168.0.0/16 depending on what your addressing looks like).

Hey Bren! Thanks for the reply! It’s a samsung Galaxy s24 ultra running android 14.

I didn’t think about adding the subnet as a resource. That would make it easier and only have that available to my profile. Will definitely test that.
I will look at my router settings as well beforehand. I believe it is indeed dhcp, but all the devices I can set a static ip on are set as such and added as static objects to not expire.

There was an update to the android app late last month-ish. I did have an issue with that as well because it did not show that an update was available through the Play Store, but there was a notice in the app saying an update was available. Somehow, it did get updated, and the notice in the app went away. It seems after that is when I started to have connection issues.

Otherwise, once I am connected, it works great. Even when scrubbing videos and such.