[BUG] Launch failure for apps missing Leanback intent (no launchable activity)

[Trooped]

⚠️ Rules of Engagement

Please read before submitting:

• Language: All issues must be submitted in English.
• Completeness: You must fill out all sections of this template.
• Respect: This project is maintained by a student/developer in their spare time; help me help you by being clear.
• Automatic Closure: Issues that are not in English or are incomplete will be closed immediately.

---

Describe the bug

When attempting to launch certain third-party apps (frequently telecom, provider, or sideloaded mobile apps) via QuickBars, the app fails to open and displays a "Can't open [package_name] (no launchable activity)" toast.

This happens because these specific apps omit the standard Android TV CATEGORY_LEANBACK_LAUNCHER intent from their manifest. As a result, QuickBars' standard intent resolution cannot find the "front door" to launch them.

To Reproduce

Steps to reproduce the behavior:

1. Configure a trigger key in QuickBars to open an app known to lack a leanback intent (e.g., a provider app like OdidoTv).
2. Press the configured trigger key.
3. See error toast: "Can't open [package_name] (no launchable activity)."

Expected behavior

QuickBars should be able to launch the app regardless of whether it strictly follows Android TV intent conventions. It should ideally fall back to scanning the package's activities and forcing a launch of the main or splash activity.

Screenshots/Video

If applicable, add screenshots or a video to help explain your problem (very helpful for UI/Overlay issues!).

Environment (please complete the following information):

• Android TV Device: [e.g. Nvidia Shield, Chromecast with Google TV]
• Android Version: [e.g. Android 12]
• QuickBars Version: [e.g. 1.3.2]
• Home Assistant Version: [e.g. 2024.2.1]

Additional context
Add any other context about the problem here (relevant Home Assistant logs are great!).

---

🛠️ Want to fix this?
If you intend to submit a PR for this bug, please comment below first so we can coordinate and avoid duplicate work!

[Trooped]

Proposed Fix / Implementation Notes:

The best approach to resolve this is to introduce an "aggressive fallback" mechanism inside the getBestLaunchIntent() function.

Important Constraint: This new logic must strictly act as a last resort. It cannot interfere with the standard intent resolution that currently works flawlessly for the vast majority of apps.

The updated resolution flow here should be:

1. Try standard launch intent (pm.getLaunchIntentForPackage).
2. Try TV-specific Leanback intent (CATEGORY_LEANBACK_LAUNCHER).
3. Try generic ACTION_MAIN intent.
4. [NEW] Aggressive Fallback: If steps 1-3 fail, query PackageManager.GET_ACTIVITIES to pull the complete list of activities for the target package. Scan the array for likely entry points (e.g., activity names containing "main", "splash", "tv", or "leanback") and attempt to launch the best match.
5. Hardcoded edge cases (e.g., Amazon Prime Video).

By placing the fallback at step 4, we ensure QuickBars continues to respect the OS's preferred launch methods for compliant apps, while creating a safety net for non-standard provider apps.

Note:
This is a good first issue in my opinion, but if someone wants to try their hand and submit a PR, you must test it with an app that you know for a fact it didn't work with up until now.

[evanofficial]

I'll give this a shot — the fallback approach you outlined makes a lot of sense. Will get a PR up with the aggressive activity scanning as step 4.