-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Android App NullPointerException on first launch #12148
Comments
Can you please run |
Will do, I have this crash handy but it wasn't from
It also crashes if I try to connect the app while the other VPN is connected & enabled as always-on. edit: This is the same stack trace I'm seeing in logcat. Please let me know if you want that output instead. |
Thanks! This really helps. cc @kari-ts |
For those looking for a quick solution, clearing the app data and then re-logging in seemed to fix this for me. |
-show VPN connection permissions after intro screen -make toggle state and main view take VPN preparedness into consideration Fixes tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
-show VPN connection permissions after intro screen -make toggle state and main view take VPN preparedness into consideration Fixes tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
-show VPN connection permissions after intro screen -make toggle state and main view take VPN preparedness into consideration Fixes tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
-show VPN connection permissions after intro screen -make toggle state and main view take VPN preparedness into consideration Fixes tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
Updates tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
Updates tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
@sjug, thank you for the report and the logs - this goes such a long way towards helping us identify and fix issues, and we so appreciate it! |
Updates tailscale/tailscale#12148 There was a small bug where we weren't rechecking the vpn permissions to the FUS would never show. We'll now do that in the view model base case on initialization. Signed-off-by: Jonathan Nobels <[email protected]>
Updates tailscale/tailscale#12148 There was a small bug where we weren't rechecking the vpn permissions to the FUS would never show. We'll now do that in the view model base case on initialization. Signed-off-by: Jonathan Nobels <[email protected]>
Happy to help, thanks for the quick triage @agottardo and turnaround @kari-ts. |
#398 introduced a bug where we were not calling startVPN after getting (or confirming) VPN.prepare permissions This resulted in the VPN not being turned on after logging in for the first time Updates tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
#398 introduced a bug where we were not calling startVPN after getting (or confirming) VPN.prepare permissions This resulted in the VPN not being turned on after logging in for the first time Updates tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
#398 introduced a bug where we were not calling startVPN after getting (or confirming) VPN.prepare permissions This resulted in the VPN not being turned on after logging in for the first time Updates tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
#398 introduced a bug where we were not calling startVPN after getting (or confirming) VPN.prepare permissions This resulted in the VPN not being turned on after logging in for the first time Updates tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
#398 introduced a bug where we were not calling startVPN after getting (or confirming) VPN.prepare permissions This resulted in the VPN not being turned on after logging in for the first time Updates tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
#398 introduced a bug where we were not calling startVPN after getting (or confirming) VPN.prepare permissions This resulted in the VPN not being turned on after logging in for the first time Updates tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
#398 introduced a bug where we were not calling startVPN after getting (or confirming) VPN.prepare permissions This resulted in the VPN not being turned on after logging in for the first time Updates tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
-show VPN connection permissions after intro screen -make toggle state and main view take VPN preparedness into consideration Fixes tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
Updates tailscale/tailscale#12148 Signed-off-by: kari-ts <[email protected]>
Updates tailscale/tailscale#12148 There was a small bug where we weren't rechecking the vpn permissions to the FUS would never show. We'll now do that in the view model base case on initialization. Signed-off-by: Jonathan Nobels <[email protected]>
What is the issue?
I updated my Tailscale app on my Android device. I had my other VPN app running and set to the "Always-on VPN" in the settings.
I tried to launch the Tailscale app after updating. It would crash immediately.
Steps to reproduce
Are there any recent changes that introduced the issue?
The recent change was the app rewrite/uprade.
OS
Android
OS version
14
Tailscale version
1.66.3-teae73f821-g63a2bbc8e71
Other software
Other VPN app
Bug report
BUG-a820be88a1be0ad8b0f78a2ee14193dcd3fec85e0988dad38e3496f127afd610-20240515172921Z-fb47fd784292be6f
The text was updated successfully, but these errors were encountered: