-
-
Notifications
You must be signed in to change notification settings - Fork 149
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
Unable to open a card from the device control quick settings tile #1881
Comments
I can reproduce this by rebooting the emulator as step 3 (for context, I don't know how you define "Quit Catima" here. IIRC a "force stop" is not a reliable test as that causes Android to block delivery of some intents). Interestingly, this works fine on Android 13, it broke in Android 14. And long-pressing the card in device controls shows it fine, just short pressing doesn't do anything. Looking at logcat, I do see a message stating "Background activity launch blocked":
|
It's quite hard to find documentation on this. My first idea was to just guard the code on Android 14 with a Toast to explain to users to long-press (not perfect, but an okay workaround for now):
But of course, Google has another fun surprise up their sleeve: Seems that even telling an user from the background that they need to long-press requires Catima to ask for notification permission even though I currently don't have any other need to ask for notification permissions and this will not make sense to users. 😞 |
However, long pressing still won't bring up catima from the lock screen 😔 |
It seems a bit buggy just after boot but aside from that I can't reproduce that: Screen_recording_20240511_112906.mp4 |
Seems to be relevant to https://developer.android.com/about/versions/14/behavior-changes-14#safer-intents But the activity is exported 🤔 |
Maybe this https://developer.android.com/guide/components/activities/background-starts#exceptions
If that's the case, there's a bug in Android... |
I found out today that apparently Samsung's Android skin ("One UI") doesn't have any effect on long-pressing an entry, just moving it around. Given this extra limitation on Samsung devices making the only workaround I could think of not universally possible I think the only logical option that remains is disabling this functionality on Android 14+. It sucks for those who do prefer to open cards this way but well, our hands seem tied here... |
On the other hand, I'm curious how it works for the google home app 🤔 |
I don't think Google will let us take a peek into the kitchen :P But it may be worth looking at the Home Assistant Android app, see if the same issues exist there and if not how they do it. |
I can confirm that single tap work for Google Home |
I have been having the same issue with Home Assistant actually so we can't look at Home Assistant how they did it. My guess is that the issue is that this feature doesn't start an app in the background so Android itself fails to communicate when the app got killed from OOM or hasn't started yet because the phone just restarted. This might be avoidable by starting on device start and on schedule, which may be necessary for notifications anyway. But it's just... guesswork, I couldn't find any documentation on this issue. |
Reproduce steps:
Expected behavior:
The card opens
Catima version: 2.29.0
Android version: 14
The text was updated successfully, but these errors were encountered: