Assistant Trigger Takes Over App Listing

[githubsterer]

Developer TODO (don't remove)

• write tests. put issue number in comment
• update documentation

Not sure my description is understandable but here's the issue: after purchasing the Assistant Trigger, all references to the App elsewhere in the system (widgets and home screen shortcuts) gets changed from Key Mapper to Assistant Trigger for newly created key maps.

So now I have two references to these launchers (one for widgets and key maps created before purchasing Assistance Trigger and another after) when everything should be under Key Mapper.

Otherwise it's very confusing.

See screenshot.

[sds100]

Yeah, this is something I became aware of when some apps list the installed apps. It kind of depends on how well they filter the packages. The reason why I list the assistant trigger as a launcher app is that some OneUI versions only let you pick an "app" as the action for the power/bixby button, not a shortcut or something else.

I'm not really sure how to fix this

[githubsterer]

It would make sense were the key map shortcut the result of the Assistant Trigger, what throws it all off is that after that point everything is binding to it, but interestingly not the ones created prior. They still remain under the Key Mapper app as I showed you.  So it does seem that some filtering is going on. Is it possible that you can change the creator app for all key maps not triggered by the Assistant Trigger to the regular Key Mapper app? Maybe that's the solution but evidently it can be done as I showed you.

[githubsterer]

Yeah, this is something I became aware of when some apps list the installed app

Just wanted to point out that this is happening with the native widget selector in Android, so it's not only random apps.

On my S22 at least, the Key Mapper shortcut maker isn't even listed at so, just the Assistant Trigger, which is strange to see.

[sds100]

Yeah, i consider the widget selector in the launcher an app as well, the system UI is an "app" as well 😅. In Lawnchair/Pixel launcher it shows Key Mapper instead of Assistant Trigger.

Wait, do you see both the "Assistant trigger" and "Key Mapper" in the shortcuts/widgets list?

[githubsterer]

Hmmm... I hope you can fix it for Samsung.

[githubsterer]

Curious is it's something I can easily fix on my end like changing the file type for the Assistant Trigger, or without that break the functionality? I would hate to have to delete it in order to get back where I was because I find the double listing super confusing.

[sds100]

I don't really know what the solution is, there isn't anything you can do to fix it i think. I don't have the same samsung device with that version of OneUI so there its hard for me to investigate.

Do you see both the "Assistant trigger" and "Key Mapper" in the shortcuts/widgets list?

[githubsterer]

It's really interesting. The widgets list only shows the Assistant, there's nothing at all for Key, which is obviously confusing if you didn't know where to look.

The shortcuts list both because one of my shortcuts was created before insisting Assistant, but every shortcut since then is showing only in Assistant. So for me there are two entries in shortcuts, one for Assistant and another for Key Mapper.

I would be happy to test anything you might want to send me and try to fix it.

[githubsterer]

Hopefully the other bugs are getting squared. From my usability productive, these are the three biggest issues, the shortcut name, icon, and this listing thing.

You had mentioned that the problem steps from the need to set the Assistant as an app because of some versions of OneUI. Do you want be to test it not being an app on my phone to see if that works?

[githubsterer]

One way to fix it completely would be to embed Assistant into a another version of the app that would go with the payment. Doing this now would open the pathway for you to charge for the "pro" version that bundles this action and perhaps other additions over time like the accessibility we spoke of, or the floating button.

[sds100]

Yeah, having it as a separate app could be a good idea, also gives more publicity in terms of people discovering it through search. Its a bit awkward to change it now though.

Can you try this APK

https://drive.google.com/file/d/1Da7nJEu-PpIGLrM9m41_--9HjW7GCVD6/view?usp=sharing

[githubsterer]

Trying it now.  On Thu, Feb 13, 2025 at 9:27 PM, Seth ***@***.***> wrote: Yeah, having it as a separate app could be a good idea, also gives more publicity in terms of people discovering it through search. Its a bit awkward to change it now though. Can you try this APK https://drive.google.com/file/d/1Da7nJEu-PpIGLrM9m41_--9HjW7GCVD6/view?usp=sharing — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> sds100 left a comment (keymapperorg/KeyMapper#1433) Yeah, having it as a separate app could be a good idea, also gives more publicity in terms of people discovering it through search. Its a bit awkward to change it now though. Can you try this APK https://drive.google.com/file/d/1Da7nJEu-PpIGLrM9m41_--9HjW7GCVD6/view?usp=sharing — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>