Steps to reproduce
Install Obsidian 1.11.4.apk from GitHub, install it on a Fairphone 5 (Android 15) with Google services disabled (not removed). Open the app for the first time (and multiple times later).
Did you follow the troubleshooting guide? [Y/N]
N (impossible to open the app)
Expected result
Open the app to create or select a vault (or open later the last vault).
Actual result
App crash an close every time I open it, before the app opens.
Environment
Impossible to get there.
Additional information
I tried to clean the cache, delete all data, uninstall, reboot the device and reinstall the app from the same APK, uninstall and install it from Google Play. It crash even before to be able to select or open a vault. Reinstalled the 1.10.6 version, it works perfectly.
1 Like
Same here. The latest update doesn’t work on a Google Pixel 3a (Android 12). I’ve tried reinstalling it from scratch with no success. The Obsidian logo just appears for 1-2 seconds and then the app suddenly closes.
I think we can get around this for now, but I am not sure we can avoid google services forever.
@Leslyecream it’s not clear to me if you have the same or a different problem.
I also have a phone from which I’ve removed all Google apps. However, I do have WebView updated and enabled.
Hi! Same issue here, exactly as Leslyecream described, on a Samsung phone with Google Services disabled.
In case it helps: I noticed that this only happens if Google Services are disabled when the app is opened. If you turn Google Services on, open the app, then disable Google Services, it seems that you can continue using Obsidian normally, as long as you don’t close it.
I hope they can fix it in a future update. For now, I’ve automated a task that enables Google services before opening Obsidian and disables them after a period of inactivity…
should be fixed 1.11.5. No ETAs.
2 Likes
A very respectful but important comment about it.
Obsidian Website mention:
Your thoughts are yours.
Obsidian stores notes privately on your device, so you can access them quickly, even offline. No one else can read them, not even us.
That was one of the main reason I chose to use Obsidian professionally and personally, including the fact that the app don’t need Google Services to work on Android.
If we are forced to use Google Services to use your app, our data are not ours (only) anymore. They are shared with Google and we all know what that mean.
I personally prefer to loose some options of functionalities than to loose privacy, so please, in the future, let us the choice and don’t force us in the future to use Google Services.
Thank you very much 
2 Likes
We are not currently using google services and I am not even sure if in the future we will implement some features that rely on google mobile services. However, I don’t think it is fair to say that using google mobile services necessarily implies that your data is shared with google.
For example, in this case the google mobile service dependency happened while implementing the app shortcuts feature, but there was no data sharing. So it depends!
The point is that the package com.google.gms (Google Mobile Service) is actually named Google Play Services.
This package require actually 369 permissions, including a complete access to the user address book, GPS, WiFi-Fi SSIDs (helps to know your position), sensors, phone calls, and complete access to all files of the device (at least the user/workspace). Permissions that you can’t accept or reject like other apps. This is the reason why my phone don’t use Google Play Services (Google Mobile Service).
So if I need in the future to enable this to open Obsidian, even if Obsidian don’t use it except for the shortcuts, etc. I have to accept that that package and all permissions it requieres, data that even if you don’t have a Google account, are sent to Google.
I just did these 2 comments for you said :
I think we can get around this for now, but I am not sure we can avoid google services forever.
I perfectly understand that we are really few people that don’t accept to renounce privacy for convenience and might be a lot of work to adapt an app for few people, but we still exist. 
Thanks Obsidian for your app, and thanks @WhiteNoise for your answers. 
Hello!
I only wanted to confirm that Obsidian 1.11.5 fixed the issue for me.
Love the new design of 1.11 version 
Thank you very much Obsidian and @WhiteNoise for this app !